WordPress
How to Migrate a WordPress Website
Move files and database together, handle URL changes safely and preserve new content during cutover.
WordPress stores information in both files and a database. A reliable migration preserves these together and accounts for new posts, orders or comments created while the move is in progress.
Practical steps
- Inventory versions, plugins, themes, database size, media and scheduled tasks. Confirm the destination runtime supports the current site before copying it.
- Back up files and database, including configuration, and protect exports containing credentials. Prepare a private destination copy using an approved transfer method.
- Test URLs, HTTPS, media, forms and login flows. If addresses change, use a WordPress-aware search-and-replace tool that respects serialised data rather than a raw SQL string substitution.
- Agree a final sync and write-freeze window for active content. Change DNS, verify the new destination and preserve a rollback copy until traffic and data are stable.
Check the result
Compare content and order counts, test plugin integrations and inspect logs after cutover. Confirm that scheduled jobs and mail send from the production site only.
Before you proceed
A staging copy can send real notifications or charge real payments if production integrations remain enabled. Disable those actions and use sandbox credentials during testing.