Migrate a WordPress Website
A WordPress migration copies the website files and database to another hosting environment. DNS is changed after the destination has been tested so visitors reach the new copy.
Plan the migration
- Confirm the source domain and hosting, destination hosting and planned launch time.
- Check destination PHP, database, storage and server compatibility.
- Identify ecommerce orders, form entries, memberships or edits that could arrive during the copy.
- Record current DNS, scheduled tasks, email and external-service settings.
- Create a complete source backup stored outside the live hosting account.
Copy and preview WordPress
- Copy all WordPress files, including hidden files and uploads.
- Export and import the complete database.
- Update
wp-config.phpwith the destination database details. - Use a WordPress-aware URL replacement if the domain changes.
- Preview the destination and test admin, forms, media, search, scheduled tasks and important customer journeys.
Complete the move
Take a final copy or reconcile new data where needed, then update the website DNS. Confirm HTTPS and repeat the important checks on the public domain. Keep the source hosting available until the new environment and backups have been verified.
See Website Migrations for the wider planning checklist. BugShield can manage a migration through a Fix Request. Add requested hosting access to the Password Vault.
Common questions
Frequently Asked Questions
Can a migration plugin move the whole website?
It can automate files, database and URL updates for many sites, but hosting limits, large media libraries, custom server rules or complex live data may need additional work.
How can I avoid losing orders or form entries?
Plan a short content freeze, maintenance period or final database sync appropriate to the site. Record how data created during the migration window will be reconciled.
When should I update DNS?
Update DNS after the destination copy has been previewed and its important features work. Keep the source available while cached DNS answers expire.
What access does BugShield need for a migration?
The required access depends on both hosts. A developer may request hosting, SFTP, database or WordPress access through the Password Vault.