An information communication technology company dedicated to developing innovative IT solutions.
In Part 1, we prepared for the migration and created backups.
In Part 2, we moved the website files and database to the new server and connected the website to its new database.
Now we are at the final stage:
Taking the website live on the new server.
This is the part where we change the DNS records so visitors are directed to the new server.
Before changing DNS, give the website one final test.
Open the website on the new server and check the important pages and features.
At a minimum, check:
If it is a WordPress website, log into the WordPress dashboard and make sure everything looks normal.
Also check your plugins and themes for errors.
The objective is simple:
Make sure the new server works before sending real visitors to it.
Your new server needs a valid SSL certificate before the domain starts receiving visitors.
Without SSL, visitors may receive security warnings when accessing:
If you are using cPanel, check:
cPanel → SSL/TLS
Depending on your hosting environment, you may also have an automatic SSL option such as AutoSSL.
Once SSL has been installed, test:
Make sure the certificate is valid and the website loads correctly.
Also check that important resources such as images, CSS, and JavaScript are loading over HTTPS.
Your domain currently points to the old server.
For example:
We want to change it to:
The most important record for many websites is the A record.
For example:
You may also have a record for:
Depending on your DNS setup, this could be a CNAME pointing to your main domain.
If your domain also handles email, be especially careful with your MX records. Changing the wrong email-related DNS records can interrupt mail delivery.
If you had planned the migration in advance, you could have reduced the DNS TTL (Time To Live) before making the switch.
TTL controls how long DNS information can be cached.
For example, you might temporarily use:
instead of a much longer value.
This can help make the transition easier to manage.
However, changing TTL does not mean that every visitor will immediately see the new server.
DNS caching still depends on different networks and DNS resolvers.
Once you are satisfied that the new server is ready, update the DNS record.
Change:
to:
After saving the DNS changes, the migration is effectively entering the go-live stage.
Some users may reach the new server before others while DNS caches update.
This is normal.
Now keep an eye on the website.
Do not immediately delete the old server or account.
Monitor:
You can also check your website's server logs for unexpected errors.
For example, if you are using Apache, error logs can help identify problems that visitors may not see directly.
After migration, it is worth checking whether any pages or files are returning errors.
Look for:
A website crawler or search engine monitoring tool can help identify broken URLs.
Pay particular attention to:
Fixing these issues quickly helps prevent a poor user experience after migration.
If your website and email use the same domain, remember that website migration and email migration are not necessarily the same thing.
Your website may work perfectly while email is still using the old server.
Check your DNS records and confirm where your MX records point.
Then test:
If you migrated email separately, make sure that process has also been completed successfully.
Give the migration time.
Keep the old website and server available until you are confident that:
The exact amount of time depends on your website and DNS setup.
Once everything is working correctly, create a fresh backup on the new server.
For the website files:
And for the database:
Store these backups somewhere safe.
You now have a recovery point for the newly migrated website.
The migration complete when:
Only after these checks would I consider retiring the old server.
This is usually related to DNS caching.
Give DNS changes time to propagate and check the domain from different networks or DNS lookup tools.
Check that the SSL certificate was installed for the correct domain and that the DNS now points to the new server.
Check your website's rewrite rules, .htaccess file, and application configuration.
For WordPress, you can also go to:
Settings → Permalinks
and save the permalink settings again to refresh the rewrite rules.
Compare the new server's PHP version, database performance, available resources, and server configuration with the old environment.
Now that we have completed all three parts, the process can be summarized in six simple stages:
The key is not to rush from one stage to another.
Each stage gives you an opportunity to catch problems before they affect visitors.
Migrating a website to a new server does not have to mean losing data or experiencing unnecessary downtime.
The most important lesson from this migration is simple:
Do not make the DNS switch until the new server is ready.
By creating reliable backups, transferring the website and database carefully, testing everything before going live, and keeping the old server available during the transition, you give yourself a much safer migration process.
The complete approach is:
Prepare → Back Up → Transfer → Restore → Test → Switch DNS → Monitor.
Once the new server has been running successfully and you are confident that everything is working, you can safely retire the old hosting environment.
That is how you can move a website to a new server while protecting the data and functionality you have already built.
Server migrations can involve more than simply copying website files. DNS, databases, SSL, email, PHP versions, permissions, and server configuration can all affect the final result.
If you are planning to move your website to a new server and want help with the migration, African Script can assist with server preparation, website transfers, database migration, DNS configuration, and post-migration testing.
Contact African Script and let us help you move your website safely.
Your email address will not be published. Required fields are marked *
Comments