iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Move the website first, change DNS last, and keep HostGator active until the new copy has passed your checks. A safe migration treats website files, databases, domain registration, DNS, and email as separate workstreams. Back up every site and database, recreate the destination environment, test it privately, then route traffic to the new host and monitor both servers during DNS propagation.
There is no guaranteed zero-downtime switch: DNS caches, application differences, and database writes can create a transition window. You can reduce that window substantially by preparing everything before the cutover and taking a final database export immediately before changing DNS.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
Understand what actually moves
A hosting change is not one transfer button. The parts of your online presence have different owners, settings, and failure modes.
| Workstream | What you move or change | Important boundary |
|---|---|---|
| Website files | Application code, themes, plugins, images, uploads, and server rules such as .htaccess |
Copying files does not copy the database or mailboxes. |
| Databases | Exported database dumps, destination databases, users, passwords, and host settings | The application configuration must be updated with the new credentials. |
| Domain registration | The registrar record for the domain name | Moving website content does not transfer registration. |
| DNS | Nameservers or individual records that direct visitors and services | A domain transfer does not automatically reproduce DNS records. |
| Mailboxes, aliases, messages, MX records, and other mail-related records | Website files normally do not include old email messages. |
For several sites, make a separate inventory and migration checklist for each domain, subdomain, database, mailbox, and scheduled task. One missed subdomain or cron job can make a move appear successful while a critical function still runs on the old account.
#1 Best Overall
Choose a migration method
DIY manual migration
Manual migration is the most portable option when the new host uses a different control panel. You download files through FTP or a file manager, export databases with phpMyAdmin or another supported tool, recreate the destination resources, and test the copy yourself. HostGator describes this work as technically challenging because it requires FTP, database, and domain-name knowledge. Choose it when you can identify every component and have time to troubleshoot.
Professional migration
Managed help is appropriate when you have many sites, frequently changing databases, a low tolerance for interruption, or no experience with FTP, database imports, and DNS. Clarify whether the service includes files, databases, email, DNS, SSL, redirects, and post-cutover testing; “website migration” can mean only part of that list.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Full cPanel account transfer
If both hosts support compatible cPanel restoration, a full account transfer can preserve more account-level configuration than a file-and-database export. It is less portable across unrelated control panels, so confirm compatibility before choosing it.
| Approach | Best fit | Trade-off |
|---|---|---|
| Manual files and database export | Different control panels or a single application you understand | More hands-on work and more opportunities to miss settings. |
| Compatible cPanel account transfer | Accounts that can be restored on a compatible cPanel host | Can retain more configuration but depends on platform compatibility. |
| Professional service | High-risk, high-traffic, or technically complex migrations | Requires confirming scope, support responsibility, and current pricing. |
1. Inventory every dependency before changing anything
Start while the HostGator account is fully operational. Record the following for every website:
- Primary domain, parked domains, subdomains, and the document root for each one.
- Database names, database users, application type, and the configuration file that contains the connection details.
- FTP accounts, file-manager locations, and any hidden files such as
.htaccess. - SSL certificates, forced-HTTPS rules, redirects, rewrite rules, and CDN or verification records.
- Cron jobs, scheduled backups, webhooks, external integrations, forms, payment callbacks, and search features.
- Email addresses, aliases, forwarders, spam settings, and which records currently provide mail delivery.
- HostGator login credentials, registrar access, DNS-provider access, and the new host’s account details.
Ask the new host which PHP or other runtime versions, database engines, extensions, upload limits, and security settings it supports. Match the old environment where practical, then plan any version change as a separate test rather than introducing it during the DNS switch.
2. Create independent backups
Do not begin a migration without a fresh backup. Download a complete copy of every site’s files and export every database. Keep at least one copy outside both hosting accounts; a portable external drive is a practical physical backup destination.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #2
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
- Use HostGator’s file manager or FTP to download each site, including hidden files when the application uses them.
- Open the downloaded archive and verify that expected directories, media, configuration files, and rewrite files are present.
- Export each database with phpMyAdmin or another supported method. Retain the original dump rather than overwriting it during testing.
- Record the backup date, site name, database name, and where the independent copies are stored.
A backup is useful only if it can be read. Check that the archive opens and that the database export is a complete dump before proceeding.
3. Build the new hosting account without changing DNS
Add each domain and subdomain at the destination, create the required databases and database users, and select runtime settings that match the application. Leave public DNS pointed at HostGator while you build and test.
Set up SSL at the new host if it requires domain validation, but do not assume the old certificate can simply be copied. Recreate redirects, rewrite rules, scheduled jobs, environment variables, and integration credentials that the application needs. If the new host provides a temporary URL or staging area, note it for testing; otherwise prepare a local hosts-file override so your computer resolves the domain to the new server without changing public DNS.
4. Transfer the website files
Download from HostGator through FTP or its file manager, then upload to the destination’s corresponding document root while preserving the directory structure.
- Identify the exact document root for the domain at the new host.
- Upload application files, themes, plugins, media, and configuration files.
- Include hidden files such as
.htaccesswhen the site uses Apache rules. - Check file and directory permissions using the destination host’s recommended settings.
- Compare file counts or directory listings between the backup and destination so a partial upload is obvious.
Do not delete the HostGator copy after uploading. Keeping the original online gives you a recovery path while DNS caches still send some visitors to the old server.
5. Recreate and import each database
Files alone cannot reproduce a database-driven site. At the new host, create a database and user, grant the required permissions, and import the export you made from HostGator.
- Open the destination control panel and create the database with a unique name.
- Create a database user with a strong password and grant it access to that database.
- Use phpMyAdmin or the host’s supported importer to load the SQL dump.
- Update the application configuration with the destination database name, username, password, and database host.
- For WordPress, these values are commonly stored in
wp-config.php; other applications use their own configuration file or environment settings. - Load the site through the private preview and confirm that pages, media, logins, search, and admin functions can read and write data.
If the application uses a database that changes continuously—such as orders, bookings, comments, or memberships—plan a final export immediately before DNS cutover. Otherwise, records written to the old database after your first export may not exist on the new server.
6. Stage and test the new copy privately
Testing before DNS changes is the main protection against an avoidable outage. Use the new host’s temporary URL, a staging feature, or a local hosts-file override to reach the destination server while the public domain still resolves to HostGator.
Functional checks
- Open the home page, representative internal pages, category or archive pages, and a page with a deep URL.
- Load images, downloadable files, scripts, stylesheets, and embedded media.
- Submit every important form and verify that the expected recipient receives it.
- Sign in, sign out, reset a password, and test any role-specific dashboard.
- Search the site and test filtering, shopping-cart or booking flows, and other transactions where applicable.
- Follow redirects from old URL patterns and confirm that HTTPS works without certificate warnings.
- Run scheduled jobs manually or inspect their logs to confirm that cron tasks are configured at the destination.
Record failures with the URL, time, browser, and error message. Fix the destination copy rather than applying a temporary workaround only on the old host.
7. Move email as a separate project
Mailboxes and old messages are not normally included in a website-file move. Decide whether the new host will provide email or whether mail will remain with a separate provider.
- List every mailbox, alias, forwarder, and shared address currently in use.
- Archive old messages through a mail client or POP3 before changing mail records.
- Recreate the required mailboxes and aliases at the new provider.
- Confirm mailbox passwords, storage limits, spam settings, and client configuration.
- Prepare the new MX records and any required TXT records before the cutover.
- After DNS changes, send test messages from and to external accounts and verify that replies, forwarding, and authentication work.
Keep the old mail service available during the transition when possible. If messages continue arriving at the old provider while DNS caches update, retrieve or forward them rather than assuming every sender switched immediately.
8. Decide how to change DNS
DNS tells the internet which server should answer for your domain. You can replace the domain’s nameservers with those supplied by the new host, or edit individual records while leaving DNS managed at the registrar or a third-party DNS provider.
Rank #4
- Provides a Vital On-The-Road Reference for Drivers On CSA Issues
- Covers All Information Drivers Need to Operate Successfully Under CSA
- Provides Fingertip Access of the Seven Basics
- How to Prepare for Roadside Inspections
| DNS method | Use it when | Checks before saving |
|---|---|---|
| Change nameservers | The new host will manage the complete DNS zone | Copy custom A, CNAME, MX, TXT, verification, CDN, and subdomain records first. |
| Edit individual records | You need to retain an existing DNS provider or custom mail/CDN setup | Change only the web records and preserve unrelated service records. |
Before either change, compare the old DNS zone with the records required by the new host. A nameserver switch can remove custom MX, TXT, verification, or CDN records if they were not recreated in the destination zone.
9. Perform the cutover and monitor propagation
Change DNS only after the destination passes your private tests. Use the nameservers or record values supplied by the new host, then monitor both endpoints because different resolvers update at different times.
- Take the final database export immediately before the DNS change if the site receives ongoing writes.
- Put the application into any available maintenance or read-only mode for the shortest practical period while you capture that final data.
- Import the final dump into the destination and confirm that the latest records are present.
- Apply the nameserver or individual-record change.
- Check the domain from multiple networks and devices, and test both the old and new server while propagation is in progress.
- Watch access logs, error logs, forms, transactions, and email delivery for the transition window.
Do not cancel HostGator immediately. Keep it online until traffic, HTTPS, scheduled jobs, forms, and mail consistently work on the new host and you are satisfied that cached DNS responses have aged out.
10. Keep or transfer the domain registration separately
You can leave registration with the current registrar and change only DNS, or transfer the registration as a separate project. HostGator states that content migration does not transfer the domain and that a domain transfer does not automatically transfer DNS records.
Recommended Free Tools
If you transfer registration, confirm the domain is eligible, unlock it if required, obtain the transfer authorization code, and verify the administrative email address before starting. Avoid combining a registration transfer with the hosting cutover unless you have a specific reason; separating them makes troubleshooting clearer.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.11. Verify the new host before closing the old account
Use a written sign-off list for every site:
- Public pages and deep links load over HTTPS.
- Media, downloads, forms, logins, search, redirects, and transactions work.
- Database writes appear in the destination database.
- Cron jobs, backups, webhooks, and external integrations run successfully.
- All required mailboxes send and receive messages, and old messages are archived.
- DNS contains the intended web, mail, verification, and service records.
- Monitoring and error logs show no unresolved migration errors.
Only after these checks pass should you cancel HostGator. Save the final backup, DNS record list, credentials, and migration notes before closing the account.
Best Value
- Used Book in Good Condition
Common failure modes and fixes
The site shows a database connection error
Recheck the database name, username, password, and database host in the application configuration. Confirm that the user has permission on the destination database and that the import completed rather than stopping on an error.
Pages work, but images or styles are missing
Compare the destination directory with the backup, including hidden files and upload folders. Check that URL settings, rewrite rules, and file permissions match the application’s requirements.
Forms submit but messages never arrive
Test the application’s mail configuration separately from DNS. Confirm that the destination mailbox exists, MX records point to the intended provider, and any required TXT authentication records were recreated.
Some visitors still see the old site
This is expected while DNS caches update. Keep both hosts online, compare the old and new copies, and avoid making divergent content changes. If the site accepts writes, reconcile any records created on the old server after the final export.
HTTPS produces a certificate warning
Verify that the new host issued or installed a certificate for every required domain and subdomain. Check that redirects point to the correct hostname and that the certificate covers the exact name visitors use.
A scheduled task stopped running
Recreate the cron job at the destination, confirm its path and runtime, and inspect logs for permission or environment-variable errors. A file transfer does not automatically recreate account-level scheduled tasks.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Professional migration cost and scope
HostGator’s current help information lists a $149.99 one-time fee for migration of one website and a $99.00 one-time fee for migration of one email account. These are vendor prices that can change, so verify the amount and included work before purchase. Ask whether the quoted service covers databases, DNS, SSL, mail archives, testing, and post-cutover fixes; the listed fee alone does not establish that every component is included.
For a high-risk move, the value of professional help is not just copying files. It is having someone accountable for database consistency, DNS sequencing, email continuity, and recovery if the destination behaves differently.
Quick Recap
Final migration checklist
- Inventory domains, subdomains, files, databases, cron jobs, SSL, redirects, integrations, and mailboxes.
- Obtain credentials for HostGator, the registrar, DNS provider, and new host.
- Download fresh files and export every database to an independent backup.
- Build domains, databases, users, runtime settings, SSL, redirects, and scheduled tasks at the destination.
- Upload files, including hidden files, and import databases.
- Update application configuration with destination database credentials.
- Preview and test the new copies privately.
- Archive email, recreate mailboxes, and prepare MX and other mail records.
- Take a final database export for sites with ongoing writes.
- Change nameservers or individual DNS records, then monitor both hosts.
- Verify traffic, HTTPS, forms, jobs, backups, transactions, and email.
- Keep the old account until the transition is stable, then cancel it and retain your migration records.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
