Website Migrations
A website migration moves some or all of a site to a new environment. This may include the files, database, domain, DNS, email or SSL certificate. Define what is moving before starting so an unrelated service is not left behind.
Plan the move
- Confirm the source site, destination hosting and planned launch time.
- List any email, subdomains, scheduled tasks, external storage or third-party connections.
- Check that the destination supports the site’s PHP version, database and required server features.
- Decide how orders, form entries or content added during the move will be handled.
- Save the current DNS records and reduce the relevant TTL in advance when appropriate.
Copy and test the website
- Create a complete source backup containing files and database.
- Copy the files and import the database at the destination.
- Update environment-specific configuration and use a WordPress-aware URL replacement if the address changes.
- Preview the destination before changing public DNS.
- Test WordPress admin, forms, search, scheduled tasks and any login or checkout journey.
Move visitors to the destination
Update only the DNS records required for the website, then confirm HTTPS and repeat the important tests on the public domain. Keep the source available until the new site has been verified and any late data has been reconciled. For WordPress-specific instructions, see Migrate a WordPress Website.
BugShield can manage a migration through a Fix Request when you would prefer developer help.
Common questions
Frequently Asked Questions
Does moving the website also move email?
Not automatically. Email may stay with its existing provider, but its DNS records must be preserved. Include email in the migration plan if it is also moving.
Can I test a migrated site before changing DNS?
Yes. The destination host may provide a preview address, staging URL or a hosts-file method. Make sure the test method supports HTTPS and does not expose the copy to search engines.
Why are some images or links still using the old domain?
The database, page-builder data, theme settings or cached files may still contain old URLs. Use a WordPress-aware replacement and clear the relevant caches.
When can I close the old hosting account?
Wait until the public site, admin area, forms, email-dependent features and other important journeys work from the new host, and keep a final independent backup before closing it.