Moving a small business website? A migration can affect your website, customer email and HTTPS if you change the wrong records. This guide is a practical sequence for reducing avoidable downtime—not a claim that any provider has been benchmarked by Toolnitive.
What changes during a website migration?
Domain registration, DNS hosting, website hosting and email hosting can be provided by different companies. Moving your website does not necessarily mean transferring your domain or moving your email. Decide exactly which service is changing before touching DNS.
Identify the DNS records you must preserve
Export the existing DNS zone and record the name, type, value and TTL for each entry. A and AAAA records resolve addresses; CNAME records create aliases; MX records direct incoming email. TXT records may contain SPF, DKIM, DMARC, verification and other service settings. Some providers also use CAA, SRV or other records. Do not assume every record can be omitted if its purpose is unclear.
Step 1: Back up and prepare
Create a restorable copy of files, databases and relevant configuration; check that it can be restored. Save the current DNS records and capture important URLs and redirects. Confirm access to your domain registrar, DNS host, website host and email administrator before starting.
Step 2: Build the destination without changing public DNS
Set up the new hosting account, deploy the site and test it using a provider preview URL or a local hosts-file override where appropriate. Check application versions, database connectivity, file permissions, HTTPS support and contact forms. Do not process real payments or expose production customer information in a test environment.
Step 3: Plan the switch and rollback
Choose a low-traffic maintenance window if your site requires it. If you intend to reduce a record’s TTL, do it ahead of the cutover so caches have time to expire. Document the original DNS targets and how to restore them. A low TTL does not guarantee instant worldwide propagation; registrar or nameserver changes may be slower.
Step 4: Change only the necessary DNS
For a hosting move, updating the relevant website A, AAAA or CNAME records may be enough. If you change authoritative nameservers, recreate the complete required DNS zone before the switch: web, mail, verification and service records. Check that mail hostnames are not accidentally tied to a changed website record.
Step 5: Validate email and HTTPS
Verify incoming and outgoing email and inspect MX, SPF, DKIM and DMARC with your email provider’s tools. Confirm that the SSL/TLS certificate covers all published hostnames, renews correctly and that HTTP redirects to HTTPS. Test for mixed content and incorrect www/non-www redirection. Many plans include certificates, so verify before purchasing an add-on.
Step 6: Test the live website
Open the homepage and key pages on mobile and desktop. Test menus, forms, login, checkout if present, canonical URLs, redirects and your sitemap. Watch server errors, Search Console coverage and important rankings. Keep the old hosting available until traffic and any data synchronization concerns are settled.
Common migration mistakes to avoid
Do not remove MX or email authentication records because you are ‘only moving the website.’ Do not cancel your previous hosting before confirming traffic has switched. Avoid simultaneous changes to registrar, nameservers, web host and email unless there is a clear plan. Keep an audit trail of what changed and when.
Which service should you compare?
For registrar or DNS management, review domain transfer and DNS features. For managed WordPress, evaluate backup/restore, staging, support and renewal pricing. Consider the plan’s exact limitations rather than assuming a provider is best for everyone.
Quick checklist before declaring success
- Backup and rollback instructions saved
- Old DNS records documented
- Website and www hostnames resolve correctly
- HTTPS and redirects work
- Incoming and outgoing email tested
- Forms, logins and checkout tested where relevant
- Search Console and server errors monitored
Helpful comparisons
Compare providers before moving
If you need a new provider after preparing your migration plan, compare hosting requirements and renewal terms first. SiteGround is an option to investigate for managed WordPress hosting; Namecheap may fit domain-first workflows and offers several separate hosting products. Neither recommendation is based on an independent speed benchmark.
Affiliate disclosure: Toolnitive may earn a commission if you purchase through these links, at no extra cost to you. Check the current product details and final checkout price before buying.
- Namecheap vs Cloudflare Registrar — choosing a domain registrar
- Best Hosting for Small Business — selecting hosting
Editorial disclosure: Some Toolnitive pages may contain affiliate links. This guide is educational; plan-specific features, security requirements and DNS behavior should be verified with the relevant provider before changing production systems.
SSL errors after a migration? Follow our 7-step HTTPS troubleshooting checklist to diagnose certificate mismatches, stale DNS records, redirects and mixed content before spending money on another hosting plan.
Email stopped after transferring a domain or changing nameservers? Our DNS and MX troubleshooting guide explains how to inspect MX, SPF, DKIM and DMARC before changing live mail settings.
