A website migration is only truly complete once everything has been checked. After transferring files, database, and DNS, small mistakes can have big consequences: a broken checkout, missing emails, or an expired SSL certificate. This checklist walks through the ten most important checks you should perform right after every migration, so you can be sure the site runs technically, functionally, and securely on the new environment.
Before going live: checking your preparation
Before you finalize the DNS switch, it’s wise to test the new environment first via a temporary test domain or your computer’s hosts file. This lets you see whether the site, database, and any settings were correctly transferred before visitors notice anything. Also check that all files, uploads, and database tables have been fully copied and that file permissions are correct.
Technical checks right after migration
Once the site is running on the new server, start by checking the basics. These points ensure the site is technically stable and secure.
SSL certificate active
Check whether the padlock appears in the browser and whether the site works over https without warnings. A free SSL certificate is usually installed automatically once the domain points to the new server.
Test loading speed
Compare the load time with the old environment. A slow site after migration often points to incorrect caching settings or a non-optimized database.
Redirects and permalinks
Check whether old URLs still work and whether 301 redirects are correctly set up, so you don’t lose traffic or ranking.
Track down error messages
Review the server logs for 404 and 500 errors. These immediately indicate where files are missing or configurations are incorrect.
Functional and content checks
In addition to the technical side, the content and functionality of the site must also be correct. Go through the following points manually.
- Forms submit and arrive correctly, including contact and order forms.
- Images, videos, and downloads load without broken links.
- Login functionality, shopping cart, and payment modules work as expected.
- Search function and navigation menus work on all devices and browsers.
- Cron jobs and automated tasks, such as backups or newsletters, run at the correct time.
Email, DNS, and aftercare
Email and DNS are the most underestimated parts of a migration. An incorrectly configured MX record can cause mail to go undelivered for days without you noticing right away.
- Check that MX, SPF, DKIM, and DMARC records are correctly set for your business email, so messages don’t end up in spam.
- Send and receive test emails from various providers.
- Check that the DNS settings of your domain name have fully propagated and that the old host isn’t still holding onto outdated records.
- Set up an initial backup on the new environment, so you have a restore point from day one.
- Monitor the site extra closely for uptime and error messages during the first few days.
In Plesk, the control panel used with many hosting packages, you can find the SSL status, DNS settings, email accounts, and backups in a single overview, which makes these checks much more manageable. If you’re unsure about performing a migration yourself, you can also have the switch guided for you; check out the options to switch to Tandata.
Frequently asked questions
How long does it take for DNS changes to fully propagate?
This depends on the TTL setting of the DNS records and can take anywhere from a few minutes to several hours. During this period, visitors may temporarily still see the old site.
Why doesn’t my SSL certificate work right after migration?
Often the domain must fully point to the new server before a certificate can be requested or activated. Wait until the DNS has propagated and then check again.
How do I check whether my email was transferred correctly?
Send test emails to and from various email addresses and providers, and check whether old emails are still accessible in the new environment.
What should I do if the site loads slower after migration?
Check caching settings, database optimization, and whether the new server has sufficient resources. Also check whether plugins or modules are compatible with the new server configuration.
Can I cancel the old hosting right after migration?
Wait until you’re certain everything works correctly on the new environment, including email and DNS. Keep the old hosting active for a few more weeks as a safety net.
Conclusion
A migration is only complete once the technical setup, content, email, and DNS have all been checked. By systematically going through this checklist, you prevent downtime, lost traffic, and missed emails. If you’re unsure about your current hosting or want the switch guided without any hassle, check out the options for web hosting or consult the knowledge base for more information.