A WordPress migration must preserve both the site files and its database. Copying only uploads misses settings and posts; copying only the database misses themes, plugins and media. Test a complete destination before sending visitors there.
Define the cutover and rollback
Record the source versions, domain, database details, scheduled tasks and mail configuration. Decide when to pause writes, especially for stores, membership sites and busy comment sections. A backup taken hours before cutover may omit new orders or uploads.
- Take a complete source backup and keep an independent copy.
- Create the destination site and database with compatible software.
- Restore the files and import the matching database through a supported migration method.
- Update the destination database credentials and any required paths.
- Preview using a supported method that preserves the intended hostname where possible.
- Freeze writes, take the final data copy, then change DNS when acceptance checks pass.
Handle a domain change separately
Keeping the same domain often avoids broad URL replacement. If the domain changes, use a WordPress-aware migration tool that handles serialized data. A blind text replacement inside a SQL dump can damage stored settings. Keep the original export untouched.
Verify application behavior
Check admin login, media, permalinks, forms and any checkout flow in an appropriate test mode. Review scheduled jobs and external integrations so the source and destination do not both send messages or process jobs during the overlap.
Maintain a clear source of truth after launch. If rollback is required after new orders arrive, simply pointing DNS backward may lose those writes. Reconcile the new data or plan an application-level rollback rather than restoring an old database without review.
Close the transition
Keep the old service until cached DNS answers and validation checks have settled. Then disable its background jobs, retain the agreed backup, and remove temporary access credentials.
Use the DNS cutover guide and verify a restore procedure before retiring the source.
Sources and references
Hosting documentation. Publication and update dates reflect this edition.
Related articles
- Backing Up and Restoring a Website’s Files and DatabaseBuild a usable recovery set, protect it outside the public directory and test restoration before an outage.2 min read
- Pointing a Domain to Your Web Hosting Without Breaking EmailChoose between a nameserver change and DNS record changes, preserve mail records and verify the destination.2 min read
- Creating a Private Staging Copy of Your WebsiteTest updates with separate files and data while preventing indexing, real emails and accidental production writes.2 min read
