Choose templates, globals, content types, integrations, or bundles and keep unrelated site data out of the run.
Generate the manifest, inspect planned operations, and catch dependency or conflict issues before anything is imported.
Require human approval, maintenance mode, backups, or custom checks before a production import proceeds.
Run the workflow locally, through WP-CLI, from a remote connection, or by calling a secured webhook from CI.
Every workflow run can leave activity, export files, and audit details for rollback, review, and compliance.
Combine backups, dry-runs, selective exports, maintenance windows, remote pushes, notifications, shell commands, and webhook calls into named workflows. Teams can reuse those workflows across projects, environments, and multisite networks.
Preview imports before changing data and add explicit approval where production risk is high.
Trigger repeatable release paths from scripts without losing the WPChangeSync audit trail.
Throttle large imports, process multisite rollouts, and keep fleet operations observable.
