superpowers-sage:migrating

To safely migrate WordPress data to Sage, create a snapshot-before backup, compute a dry-run diff, and apply changes only after explicit human approval to prevent data loss. The process enforces preflight validation and logs row-level changes for verification.

Migrating legacy plugin structures to Acorn requires a 7-phase safety contract: snapshot-before, dry-run compute, human approval gate, preflight checks, apply with logging, snapshot-after verification, and idempotency proof to guarantee reversible moves.

Yes, WordPress database migrations are guaranteed to be idempotent, meaning re-running them produces the same result without duplicating changes. The migration provides row-change proofs to verify each re-run against the expected state.

Yes, the Sage migration process supports bulk option updates including serialized data, term taxonomy fixes, attachment regeneration, and postmeta cleanup within defined scopes while enforcing snapshot-before and snapshot-after verification.

You must approve a dry-run diff because the migration process forbids destructive-first actions and blocks autonomous apply until you explicitly confirm the changes. This human approval gate prevents irreversible data loss during content and postmeta rewrites.

Preflight checks required before migrating classic WordPress theme data to Bedrock include orphan checks and validation within defined scopes. These checks run after human approval of the dry-run diff but before applying any row-level changes to the database.