Migration readiness checklist

Use this checklist before scheduling final cutover.

Code and runtime

• The migration deploy source is chosen: Git or Workspace.
• For Git, production code is committed and the branch, tag, or commit is recorded.
• For Workspace, the production file tree and transfer procedure are recorded.
• Required runtime and service versions are supported.
• The selected source can build and start without missing production files or private dependency credentials.
• Framework, extension, and dependency compatibility has been tested.

Data

• Database size, version, character set, and required extensions are known.
• The import path is chosen and rehearsed: managed-shell MySQL client with the platform DATABASE_* credentials, or a desktop client over the SSH database forward.
• Media and persistent-file paths are inventoried, including the target uploads path (wp-content/uploads for WordPress, pub/media for Magento).
• Export and import procedures have been rehearsed, with durations recorded.
• Business-critical record comparisons are defined, with the exact count queries and expected values recorded for both source and target.
• Source and target write behavior during final copy is explicit.

Configuration and integrations

• Environment variables and secret names are inventoried.
• Secrets will be entered through the Vars workflow, not copied into code.
• Email, payment, storage, search, identity, and webhook integrations have test plans.
• Scheduled jobs and background workers are recorded.
• Environment-specific hostnames and callback URLs are identified.

Traffic

• Required domains and DNS records are recorded.
• DNS time-to-live values have been lowered and the previous value expired.
• Domain ownership and certificate requirements are understood.
• A maintenance or read-only method exists for the source.

Recovery and approval

• A current source backup has been created and verified.
• The target reports current backup protection.
• Rollback criteria and decision owners are named.
• The source retention window after cutover is agreed.
• Critical customer journeys and cutover acceptance criteria are documented.

Start with Prepare an App for migration.