Published 18 November 2026

A website migration is ready for a DNS change only when the copy on the new hosting account works for real visitors and essential business tasks. Before switching traffic, test the site using a temporary URL or a local hosts-file entry, check the database and forms, confirm HTTPS, and decide how you would return traffic to the old host if something fails.

This guide is for site owners and developers moving a website to cPanel hosting. It focuses on the checks that can catch problems before a domain’s DNS records send visitors to the new server.

Prepare both hosting accounts before testing

Keep the old hosting account active during testing and after the switch. It is your reference copy and a possible fallback; do not cancel it just because files have been copied. Record the old DNS settings and the current website’s important behaviour, including contact forms, checkout steps, scheduled tasks, redirects and email routing.

cPanel’s backup documentation describes account backup and restore considerations; it is useful for understanding why a copied site and a restorable account backup are different things. A backup is not a substitute for checking that the migrated application works.

Test the new copy without sending visitors to it

Use a temporary preview URL if the hosting provider offers one, or test with a local hosts-file entry that directs your computer to the new server while leaving public DNS unchanged. The hosts-file approach affects only the computer where you make the change. Record the original entry and remove the test entry afterwards; otherwise, you may keep viewing the new server when the rest of the world is still visiting the old one.

  1. Load key URLs: Test the home page, representative inner pages, images, downloads, and any important landing pages. Look for missing assets, incorrect links, unexpected redirects and error pages.
  2. Exercise the application: Sign in to the appropriate admin area and test a representative form, search, booking or checkout flow. For a store, verify product details and a safe test transaction process without placing an unintended live order.
  3. Check the database: Confirm that recent content and records are present. Review application configuration for the correct database name, username and credentials; a site may display a generic error when it cannot connect.
  4. Verify HTTPS behaviour: Test secure pages and redirects using the hostname visitors will use. Check for certificate errors and mixed content, where a secure page still requests resources over HTTP.
  5. Review background work: Check scheduled tasks, outbound email and integrations that depend on server paths, credentials, IP allow-lists or callback URLs. A page can appear healthy while a cron task or notification is failing.

Keep DNS and email changes separate

DNS is the system that directs domain names to services such as a website or mail server. Before changing records, identify which provider hosts the domain’s authoritative DNS zone. Moving web hosting does not automatically mean that nameservers should change, and changing nameservers can affect more than the website.

Compare the current DNS zone with the intended new setup. Pay particular attention to the website’s address records and to MX records and email-related TXT records. If email remains with its existing provider, preserve the records that service requires. Do not assume that copying website files transfers mailboxes or reproduces mail routing.

Important: Changing nameservers can replace the active DNS zone. If you have not accounted for email and other required records at the destination, the website may come up while business email or another service stops working.

For each DNS record you plan to change, write down its current value, intended value and purpose. Make only the changes needed for the migration, and use the DNS provider’s documentation for its specific controls.

Switch traffic, verify, and know when to roll back

Choose a cutover time that allows someone to monitor the site and act if a critical issue appears. If customers can create orders, accounts or content, agree on a brief change freeze or another method to keep the old and new copies from diverging. Lowering a record’s TTL beforehand may help some DNS resolvers pick up a change sooner, but it does not guarantee that every visitor will move at the same time.

  1. Make the planned DNS change at the authoritative provider and note the time and values changed.
  2. Check the domain from more than one network or resolver, and test the important pages and business functions again.
  3. Monitor form delivery, checkout or booking activity, site errors, HTTPS and email. Remember that visitors may reach different hosting accounts while DNS changes are being observed across networks.
  4. If a critical failure occurs, use your written plan to restore the previous DNS values. Do not delete or overwrite either site until you have confirmed which copy contains the latest data.

cPanel’s migration guidance is relevant to moving hosting accounts, while its backup documentation helps frame the recovery work. The practical lesson is to treat migration as a tested cutover, not as a one-time file transfer.

Where HostCupid fits

HostCupid Web Solutions Private Limited is a Chennai-based company operating since 2018 that provides hosting and website migration assistance. For a business owner moving a cPanel-oriented site, migration assistance can be relevant when coordinating the account move; the site owner should still agree on what is included, how email and DNS will be handled, and who will test the application before cutover. Keep a copy of the checklist and the rollback values with whoever is responsible for the domain.

A migration is complete when the destination serves the expected site, the important workflows work, and you know how to respond if they do not—not merely when the files have arrived.


Sources

Portrait of Kavya Anand, HostCupid editorial persona
Published by
Kavya Anand

HostCupid Editorial Team

Covers WordPress, cPanel, performance, DNS, website security and practical digital guidance for Indian businesses.

Editorial persona representing the HostCupid content team.

← More HostCupid Insights