Home › Knowledgebase › KB-1396

How To Minimise Website Migration Downtime

Summary

This guide helps you troubleshoot and resolve: How To Minimise Website Migration Downtime. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Moving a live website between hosting providers or servers carries inherent risks to business continuity. Poorly planned migrations can result in extended outages, lost data, and broken marketing links, which directly impact customer trust and revenue. This guide outlines how to minimise downtime during a website migration by addressing DNS propagation, data synchronisation, and pre-launch verification.

Understanding Migration Downtime

Downtime during a migration typically occurs for two primary reasons:

Pre-Migration Planning

1. Audit Your Current Environment

Before touching any settings, document your current setup to ensure nothing is missed during the move.

  1. Identify all domains and subdomains associated with the website.
  2. Locate your current DNS records, including A records, CNAME records, and MX records for email.
  3. Note the file paths used on the current server, such as /var/www/html or public_html.
  4. Record database credentials, including the database name, username, and host address.

2. Prepare the Destination Server

Set up the new hosting environment before initiating the transfer.

  1. Install the required web server software (e.g., Apache or Nginx) and database server.
  2. Upload your website files to the new server using SFTP or the hosting control panel's file manager. For cPanel users, navigate to Files > File Manager. For Plesk users, go to Websites & Domains > File Manager.
  3. Import your database export into the new database instance. In cPanel, use Databases > phpMyAdmin. In Plesk, use Websites & Domains > Databases > phpMyAdmin.
  4. Update configuration files (such as wp-config.php for WordPress) with the new database credentials.
  5. Migrate SSL/TLS certificates: Export your existing SSL certificate and private key from the old server. Install them on the new server via the control panel's SSL/TLS management section (cPanel: Security > SSL/TLS Status; Plesk: Websites & Domains > SSL/TLS Certificates). Ensure the certificate is active before updating DNS to avoid browser security warnings.

3. Lower DNS TTL Values

Time to Live (TTL) determines how long ISPs cache your DNS records. A high TTL means longer propagation delays.

Important: Lower your TTL values at least 24 hours before the migration. For example, if you change your TTL to 300 seconds (5 minutes), it will take up to 5 minutes for ISPs to check for updates after you change the A record. If you leave the TTL at the default 86400 seconds (24 hours), some visitors may be directed to the old server for an entire day after you switch. Do not lower TTL values on the day of migration, as changes to the TTL itself take time to propagate based on the existing TTL.
  1. Log in to your domain registrar or DNS management console.
  2. Locate the DNS record for your primary domain (usually the A record).
  3. Change the TTL value to a low number, such as 300 seconds (5 minutes).
  4. Save the changes using the Save or Update button.

Pre-Migration Testing

Before updating your public DNS, verify the new server works correctly using a temporary URL or a local hosts file override. This allows you to test the site without affecting live visitors.

Option A: Using a Temporary URL

  1. Check if your hosting provider provides a temporary URL (e.g., http://server-ip/~username).
  2. Visit the temporary URL in a browser.
  3. Test all key pages, forms, and database connections.

Option B: Using the Local Hosts File

You can force your computer to resolve your domain to the new server's IP address.

  1. Windows: Open Notepad as Administrator. Open C:\Windows\System32\drivers\etc\hosts. Add a new line at the bottom: [New Server IP] yourdomain.com. Save the file.
  2. macOS/Linux: Open Terminal. Run sudo nano /etc/hosts. Add [New Server IP] yourdomain.com. Save and exit.
  3. Clear your browser cache or open an incognito window and visit yourdomain.com. You are now viewing the new server.
  4. Test contact forms, checkout processes, and user logins.
  5. Crucial: Remove the entry from your hosts file after testing to resume normal browsing.

Executing the Migration

1. Synchronise Dynamic Data

For sites with frequent updates, perform a final data sync immediately before switching DNS.

  1. Place the old site in maintenance mode to prevent new database entries.
  2. Export the most recent database dump from the old server.
  3. Import this final dump into the new server's database.
  4. Verify that the record counts match between the old and new databases.

2. Update DNS Records

Once the new environment is verified, point your domain to the new server.

  1. Access your DNS management panel at your domain registrar.
  2. Edit the A record for your domain to point to the new server's IP address.
  3. Update any CNAME records for subdomains (e.g., www) if necessary.
  4. Email Consideration: Ensure your MX records are correctly configured. If you are moving email hosting along with the website, update the MX records at the same time as the A record to minimise email downtime. If email remains with the current provider, do not change the MX records.
  5. Click Save Changes to apply the new DNS configuration.

3. Verify the New Environment

Before announcing the migration is complete, confirm everything works as expected.

  1. Visit your website using a browser in incognito mode to avoid local caching.
  2. Test key functionality, such as contact forms, checkout processes, and user logins.
  3. Check that images, stylesheets, and scripts are loading from the new server.
  4. Use an online DNS propagation checker to confirm the new IP address is visible globally.

Troubleshooting Common Migration Failures

DNS Does Not Propagate

Database Connection Errors After Switch

500 Internal Server Error After Migration

Post-Migration Checks

Monitor for Issues

Keep a close eye on the site for the first 24 to 48 hours.

Rollback Procedure

If critical issues are discovered on the new platform, follow these steps to revert to the old server:

  1. Ensure the old server remains running and has not been cancelled.
  2. Log in to your domain registrar or DNS management console.
  3. Edit the A record for your domain and change the IP address back to the original server's IP.
  4. Update any CNAME records back to their previous values.
  5. Click Save Changes.
  6. Wait for DNS propagation (based on your TTL setting) for traffic to return to the old server.

Decommission the Old Server

Do not cancel your old hosting account immediately.

  1. Keep the old server running for at least one week after the migration.
  2. Use this period as a rollback option if critical issues are discovered on the new platform.
  3. Once you are confident the migration is stable, back up the old server one final time and then cancel the service.
Preserving marketing visibility is critical. Ensure that your robots.txt file and sitemap are accessible on the new server so search engines can continue to index your content without interruption.
If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket