Migrating a website to a new host without downtime requires more than copying files. This guide gives you a repeatable process for preparing DNS, transferring databases and email, testing the new environment, switching traffic safely, and monitoring the result with a reusable checklist and verification tracker.
Overview
A hosting migration is the process of moving a website’s files, databases, configuration, email, and related services from one hosting provider to another. The safest approach is to build and test the replacement environment before changing the domain’s DNS records. Your current host continues serving visitors while the new host is prepared, which reduces the risk of a visible interruption.
No migration can guarantee that every visitor will see the same server at the same moment. DNS resolvers and browsers may retain records for different periods, and application behavior can vary between servers. However, careful sequencing can keep the website available throughout the transition and provide a clear rollback path if a problem appears.
Before starting, document the current setup. Record the domain name, DNS provider, hosting control panel, PHP or runtime version, database type, scheduled tasks, SSL configuration, email accounts, subdomains, redirects, and third-party integrations. If the site is business-critical, schedule the final cutover during a period of lower activity and identify who can approve a rollback.
For broader planning, compare the destination plan against your actual workload rather than choosing on storage alone. The guidance in How to Compare Web Hosting Plans Without Getting Misled by Marketing can help you review resources, support, renewal terms, and technical limits before the move.
What to track
1. Inventory and access
- Domain registrar and DNS provider login details.
- Current and destination hosting account details.
- Website files, database names, usernames, and passwords.
- Email accounts, aliases, forwarding rules, and mailbox storage.
- Subdomains, parked domains, staging sites, and API endpoints.
- Scheduled jobs, cron commands, server-side scripts, and environment variables.
- Analytics, payment, CDN, security, and transactional email integrations.
Store credentials in a secure password manager and never place passwords in a public checklist. If you cannot identify who controls DNS, resolve that issue before the migration begins.
2. Backups and rollback points
Create a complete backup of the website files and database. If email is hosted on the current server, export or otherwise preserve the mail data according to the provider’s available tools. Keep at least one copy outside the current hosting account and confirm that the archive can be opened or restored.
Record the backup date and the last successful restore test. A backup that exists but cannot be restored is not a dependable rollback plan. Keep the current hosting account active until the new site has passed testing and the DNS transition is stable.
3. DNS and TTL preparation
List every DNS record that may be affected: A and AAAA records, CNAME records, MX records, TXT verification records, and records for subdomains. Lowering the TTL before the move may help some resolvers request updated records sooner, but it does not force an immediate refresh everywhere.
Do not replace the entire DNS zone with a basic template unless you have compared the records line by line. Missing an MX, TXT, or subdomain record can interrupt email, verification, or an application endpoint even when the main website loads correctly.
4. Destination environment
Set up the domain or temporary site on the new host. Match the required runtime version and install the necessary extensions, database engine, SSL support, rewrite rules, and scheduled tasks. If you are moving WordPress, confirm the site URL, permalink behavior, uploads directory, caching configuration, and administrator access.
Transfer files and import the database before changing DNS. For a large or frequently updated site, use a method that allows a final incremental file or database sync shortly before cutover. Limit changes during that final window so the source and destination do not diverge.
5. Testing and monitoring data
Use a hosts-file override, temporary URL, preview address, or other provider-supported method to test the destination without directing public traffic to it. Check the homepage, representative content, forms, logins, search, checkout or payment flows, media, downloads, redirects, and administrative functions.
Track baseline measurements before the move: representative page load behavior, response status, uptime alerts, error logs, and current traffic patterns. The workflow in How to Test Web Hosting Speed and Uptime can be used to make the before-and-after comparison consistent.
Printable migration checklist
- [ ] Confirm the destination plan supports the site’s software and resource needs.
- [ ] Record DNS records, email settings, subdomains, redirects, and scheduled tasks.
- [ ] Create and verify independent backups of files, databases, and required mail data.
- [ ] Lower DNS TTL if appropriate and record the date and previous value.
- [ ] Create the site on the new host and configure the runtime and database.
- [ ] Transfer files and import the database.
- [ ] Install or validate the SSL certificate and force HTTPS only after testing.
- [ ] Test the site privately, including forms, logins, payments, email, and redirects.
- [ ] Complete the final synchronization and record the exact cutover time.
- [ ] Update DNS records and preserve the old host for rollback.
- [ ] Monitor traffic, errors, uptime, forms, email, and transactions after the change.
Cadence and checkpoints
Use checkpoints instead of treating migration as one large task. The following schedule works for many small and medium websites, but adjust it for traffic volume, email dependencies, and application complexity.
Several days before cutover
Complete the inventory, verify access, create backups, review DNS, and prepare the destination. Test a private copy of the site. Confirm that the new server can send or receive email as required, but avoid changing production mail records until the cutover plan is ready.
One day before cutover
Review the test results and record any known differences. Confirm the DNS values that will change, the final backup location, the rollback decision-maker, and the support contacts for both hosts. If the website accepts orders, registrations, comments, or other writes, decide how those changes will be preserved during the final sync.
At cutover
Take the final backup or synchronization, verify the destination data, and update only the required DNS records. Record the time, previous values, and new values. Keep the old host online. Avoid making unrelated configuration changes while DNS is transitioning.
After cutover
Test from more than one network or monitoring location. Check the main domain and important subdomains, HTTPS, redirects, forms, logins, database writes, media, email delivery, and scheduled jobs. Review application and web-server logs for unexpected errors. Continue monitoring before cancelling the old hosting account.
Post-launch verification tracker
| Check | Status | Evidence or notes | Next review |
|---|---|---|---|
| DNS points to the destination | Pending / Pass / Fail | Record queried name and time | After cutover |
| HTTPS certificate and redirects | Pending / Pass / Fail | Test canonical URLs | After cutover |
| Forms, logins, and database writes | Pending / Pass / Fail | Record test transaction | Within 24 hours |
| Email sending and receiving | Pending / Pass / Fail | Test each critical mailbox | Within 24 hours |
| Scheduled jobs and integrations | Pending / Pass / Fail | Review logs and delivery | Within 48 hours |
| Uptime, errors, and performance | Pending / Pass / Fail | Compare with baseline | Weekly for the first month |
How to interpret changes
A successful DNS change does not prove that the migration is complete. A page may load while a form fails, a scheduled job stops, or email continues using an old record. Evaluate the site by user journeys and operational functions, not only by the homepage.
If some users reach the old server and others reach the new one, DNS caching may still be involved. Keep both environments consistent during this period, or temporarily disable features that write different data to each server. Do not assume that increasing or decreasing TTL will instantly resolve every discrepancy.
Separate migration issues from normal traffic variation. Compare error logs, response behavior, and key transactions with your pre-migration baseline. A slower result on one test network may not indicate a server problem, while repeated application errors across locations deserve immediate investigation.
Use a rollback when the destination cannot reliably serve critical pages, process essential transactions, preserve data, or handle required email. Restore the previous DNS values, document the reason, and correct the destination before attempting another cutover. A rollback is a controlled safeguard, not evidence that the entire migration plan was invalid.
When to revisit
Revisit this migration record at least weekly during the first month, then monthly or quarterly as part of routine hosting maintenance. Review it sooner when the site changes substantially, such as after a platform upgrade, domain transfer, DNS provider change, major plugin or application update, email-provider move, or redesign.
At each review, confirm that backups still run and can be restored, DNS records remain documented, SSL renewals are functioning, scheduled tasks are active, and monitoring alerts reach the right person. Compare hosting renewal costs and resource usage before the next billing term; the web hosting renewal pricing comparison explains why the initial sign-up price is not the only figure to track.
For the next migration, improve the checklist using what the tracker revealed. Add any missed DNS records, failed test cases, or unclear ownership details. If you are ready to act now, print the checklist, assign an owner to every unchecked item, schedule a low-risk cutover window, and do not close the old hosting account until the post-launch tracker shows stable results.