Plan before copying anything
Start by listing everything connected to the domain. That may include the WordPress site, subdomains, email mailboxes, DNS records, scheduled jobs, external storage, payment services, analytics, and third-party APIs. A website migration and an email migration are separate tasks even when both use the same domain.
Choose a low-traffic period and avoid major content changes during the final move. Stores, forums, and membership sites need special care because new orders, posts, or registrations can appear while data is being copied.
1. Create complete backups
Back up all WordPress files and the complete database. The files include WordPress core, themes, plugins, uploads, and configuration. The database contains posts, pages, users, settings, orders, and many plugin records.
Download a copy outside both hosting accounts. If the site is large, confirm that the archive completed successfully and can be opened. Do not rely on a single untested backup.
2. Prepare the destination
Add the domain to the new hosting account without changing public DNS yet. Create a database and database user, select a supported PHP version, and confirm required extensions. Install an SSL certificate if the host can issue one before DNS changes, or plan to issue it immediately afterward.
Record the new database name, username, password, server address, document root, and temporary testing method.
3. Copy files and import the database
Upload or transfer the files into the destination website directory. Import the database using a hosting tool, command line, or migration plugin. Update wp-config.php with the new database credentials.
A migration plugin can automate much of this process. Manual migration provides more control and may work better for large or unusual sites. Either method still requires testing.
4. Handle URLs carefully
If the domain remains the same, the public site URL may not need to change. If the domain or path changes, update WordPress URLs with a serialization-aware search and replace tool. A plain text replacement can damage serialized plugin and theme data.
Create permanent redirects from old URLs to matching new URLs when changing domains or paths. Preserve page structure where possible so visitors and search engines reach the intended content.
5. Test before changing DNS
Use a host-provided preview, temporary URL, local hosts-file entry, or staging domain. Browse important pages and test both desktop and mobile layouts. Log in to WordPress and inspect the dashboard.
- Test contact, quote, registration, login, password reset, and checkout forms.
- Open images, documents, CSS, and JavaScript files.
- Check menus, internal links, search, redirects, and 404 behavior.
- Verify plugins, scheduled jobs, caching, and security tools.
- Review PHP and WordPress error logs.
6. Reduce DNS transition risk
DNS changes take time to reach resolvers and visitors. Lowering the DNS record's TTL before migration can shorten cached results, but it must be done before the existing TTL expires. Copy every required DNS record, not only the website address.
When ready, update the A, AAAA, CNAME, or nameserver records according to the new provider's instructions. Avoid changing nameservers unless the full DNS zone has been recreated, including email and verification records.
7. Perform a final data sync
For an active store or membership site, place the old site in maintenance mode briefly and copy the latest database after testing. This prevents orders or user changes from being split between servers. Static business sites may not require a second sync.
8. Verify the live site
Confirm that DNS resolves to the new server, HTTPS works without warnings, and the certificate covers the required hostnames. Test forms and outgoing email from the live domain. Check payment callbacks, webhooks, cron jobs, backups, security, and caching.
Monitor logs and customer reports for several days. Keep the old account available until DNS caches have cleared and you are confident no data is missing.
Common migration mistakes
- Canceling the old host too early
- Forgetting email and DNS records
- Using an incomplete or untested backup
- Changing URLs with a non-serialization-aware tool
- Failing to test forms, checkout, scheduled jobs, and SSL
- Leaving both copies open for new transactions
If you prefer assistance, contact Web Host Pro support before changing DNS. Migration scope depends on the site, access available, platform, email setup, and account size.
Frequently Asked Questions
Will a WordPress migration cause downtime?
A planned migration can have little or no visible downtime. Dynamic sites may need a short maintenance window for the final database sync.
Can I migrate WordPress with a plugin?
Yes. Migration plugins work well for many sites, but upload limits, storage, timeouts, custom configurations, or very large databases may require a manual method.
Do I need to move my domain registration?
No. Hosting, DNS, and domain registration can remain with different providers. You only need to point DNS to the new hosting service.
When can I cancel the old hosting account?
Wait until DNS has propagated, the new site and email are verified, backups are running, and no current data remains only on the old server.
