Checklist after moving a website to a new server

Print
  • 0

In short: test the copy before you change DNS, test email, HTTPS and forms right after, and leave scheduled tasks and backups for the following days. Do not cancel the old hosting until every item below has passed.

Before you change the nameservers

  1. Preview the copy on the new server by adding a temporary line to your hosts file, as explained in How to access the site while it is being delegated.
  2. Click through the pages that matter: the home page, a few inner pages, search, login, cart and checkout.
  3. Match the PHP version to the old server, or pick a compatible one, in PHP version selection, and make sure the extensions your application needs are on (managing PHP extensions).
  4. Recreate special DNS records (verification TXT records, SPF, DKIM, external MX, subdomains) in the new zone so they are not lost when the nameservers change. See TXT records and MX records.

Right after the switch

CheckPasses when
HTTPSThe site loads with a padlock and no warning. The free certificate is issued automatically once the domain points at the new server (Automatic issuance of SSL)
EmailA test message goes out and one comes in, and your mail apps and phone use the new settings (setting up mail clients)
FormsA test submission of the contact form arrives
ShopA test order goes through, including payment

Over the next few days

  • Recreate scheduled tasks in cPanel under Cron Jobs, and make sure they are no longer running on the old server as well.
  • TopHost hosting is backed up daily with JetBackup, but download a copy of your own after the move too (downloading a full account backup).
  • Stop the old hosting once DNS has updated everywhere and the website and email have run cleanly for a few days, typically 3 to 7.

Typical problems

The SSL certificate is not issued

When the domain goes through Cloudflare with the proxy switched on, cPanel's automatic validation can fail. Turn the proxy off until the certificate is issued, or use Cloudflare's own certificate.

Forms or an email plugin stopped sending

TopHost shared hosting blocks outgoing connections to third-party SMTP servers on ports 25, 465 and 587, so a plugin set up for another provider's SMTP will fail. Send through a mailbox created in cPanel on your own domain instead. Details in Restrictions on the use of the mail service.

Which mail server do I enter in my email app?

cPanel shows the exact settings: open Email Accounts, then Connect Devices. If the domain uses Cloudflare, an address like mail.yourdomain.md may not work; use the server name listed there.

Plugins will not update

Check file permissions and the site address in the application's settings. If it still fails, open a ticket and include the exact address of the site.

Related articles

Was this answer helpful?