A final preflight checklist before running a production sync, import, or remote push.
Updated 5 June 2026·Task guide
Outcome
You have a repeatable production release checklist that covers scope, dry runs, backups, conflict strategy, approvals, maintenance mode, verification, and rollback before a workflow writes to production.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.
Risk level
High. Production release guide. Treat every unchecked item as a reason to pause.
Before you start
Production remote is configured and tested.
The release scope is known: integrations, selected items, related data, and exclusions.
You have access to Activity, backups, and the affected production pages/templates.
The release owner knows who can approve, execute, and roll back.
Checklist
Confirm the release scope List the exact integrations and selected items that should move. Include dependencies such as media, fields, global classes, variables, custom fonts, and framework settings.
Create or verify a backup Export production or confirm WPChangeSync backup-before-overwrite will cover the affected data.
Run a dry run Use the workflow in dry-run mode and review created, updated, skipped, conflicted, and missing items.
Choose conflict strategy per integration Use prompt/skip for uncertain production data, merge for compatible config, and overwrite only when the source is authoritative.
Enable approval gates Require manual approval before any production write step.
Plan maintenance mode Use maintenance mode for broad imports or risky overwrites, and confirm timeout behavior.
Execute in a release window Run the workflow, keep Activity open, and avoid parallel editor changes.
Verify production Check affected URLs, Bricks templates, media, forms/fields, global styles, and Activity results.
Keep rollback materials Keep the pre-release export, backup records, and version snapshots until the release is accepted.
wp wpchangesync workflow listnwp wpchangesync workflow show nwp wpchangesync workflow run --mode=dry_runnwp wpchangesync workflow run --mode=execute
Production rule
Never run a broad production import as the first test. If the dry run is confusing, reduce scope before execution.
How to find the workflow ID
Open Workflows in the admin UI and inspect the workflow details, or run wp wpchangesync workflow list. Use the ID from that list in workflow show and workflow run commands.
Verify and recover
After the release, compare the production result against the approved scope, review Activity for failed or skipped steps, and keep rollback materials until sign-off. If verification fails, stop further syncs, restore the affected item or integration from backup/version history, then re-run with a narrower scope.