🔍

How to migrate a website to HostGator manually

A manual migration gives you direct control over your website’s files, database and DNS settings. It works when moving from most existing hosts, regardless of whether your current provider uses cPanel, Plesk or a proprietary interface. The basic sequence is to export the site, recreate its database on HostGator, upload the files and then redirect the domain. Planning a short period of downtime is often simpler than synchronising two copies of a site that several people are editing.

Use the HostGator customer area to access cPanel, webmail, billing and invoices, domain purchase or transfer options, video tutorials, the knowledge base, ticket support and the online forums. Hosting, domain registration, email and website content are separate services, even when they share a login. Record each renewal date and account owner before beginning, because a successful migration should not create gaps in any of those services.

Prepare the move

Create an inventory before changing anything on the live site. Record the domain and its registrar, nameservers, DNS records, hosting plan, website files, database, email accounts, contact forms, payment connections, analytics, scheduled jobs and redirect rules. For WordPress or Joomla, note the content management system version, installed extensions and required PHP version. A saved export of the current hosting dashboard can be more valuable than a hastily assembled checklist.

Choose a low-traffic window during Australian business hours, accounting for the differences between AEDT, ACST and AWST. Sydney and Melbourne teams may work alongside colleagues in other states, while January holidays can affect staffing and support availability. Take complete backups and keep them outside the old hosting account. Download both the files and database, and confirm that you can restore a sample rather than assuming a backup is valid because it appears in cPanel.

If the website handles personal information, check whether the Australian Privacy Act 1988 and Australian Privacy Principles apply. Do not copy unnecessary customer information into the new environment. For a larger handover, a concise carry course can complement the inventory by assigning owners, deadlines and rollback decisions to named tasks.

Choose a transfer method

HostGator offers a cPanel transfer facility for supported source hosts, often found under the Files area as Transfer Website. It can copy files and databases through a guided process. Manual migration is useful when the source provider lacks that facility, uses an unusual control panel, contains very large files or requires closer control over database and user credentials.

For the manual route, use SFTP or FTP with an account created in HostGator cPanel, or use cPanel File Manager for smaller transfers. You will also need the old database export and the new account’s database details. Install the content management system on the destination first if necessary, ensuring its PHP version and extensions match the HostGator plan. Create email accounts separately because moving website files does not move existing inboxes.

Decide whether the domain will live inside your HostGator account. The domain purchase and transfer area can begin a registration or transfer an eligible domain, but a registrar change is not the same operation as a hosting change. If the domain remains with another registrar, HostGator must still receive the correct DNS settings. Do not change nameservers yet; the domain should continue resolving to the working site until the new copy passes testing.

Move the website files

Export the site from its current provider. In cPanel File Manager, select the public_html contents and create a compressed archive; in phpMyAdmin, export the matching database as SQL. An SFTP download is usually quicker for a large website. Include configuration files, hidden files such as .htaccess and CMS-specific files that an extension filter might omit. Store the archive in more than one secure location before editing anything.

Upload the archive to the appropriate HostGator directory, normally public_html for the main website or a subdirectory for an additional site. Extract it there and check that the folder structure matches what the application expects. Transfer the extracted files instead when a large archive causes timeouts, since repeated extraction can also be demanding. Apply sensible permissions and avoid making every folder or file writable to everyone as a troubleshooting shortcut.

Check the File Manager and local upload limits before starting. A fixed NBN connection, business fibre or stable wired network is preferable to a congested mobile hotspot, particularly for regional users. Visitors in Sydney, Melbourne and Brisbane can have quite different connection paths, so test the finished site rather than assuming equal performance. For a large archive, use an SFTP client with resume support or ask HostGator support about a temporary upload method. Never leave database exports or backups in a publicly accessible web folder.

Rebuild the database

Create a database and user in HostGator cPanel, then import the exported SQL through phpMyAdmin. Store the database password securely and give the user only the access required by the application. Large imports may exceed the default PHP execution limit. Splitting the SQL file or increasing the limit with HostGator support may be necessary. Avoid repeatedly importing a partially completed dump, as duplicate tables and records can complicate recovery.

Update the application configuration with the new database name, username, password and host, which is usually localhost. WordPress uses wp-config.php, while Joomla uses configuration.php. Make these changes only after the import succeeds. If the CMS stores the old domain in its database, update those entries carefully. The WordPress Search and Replace tool can update URLs across posts and options, but it should run on the restored copy, with a backup available beforehand.

Keep the existing table prefix unless there is a deliberate reason to change it. Run any required installation or update wizard, confirm that media uploads use the correct directory and check scheduled tasks. Time-based scripts deserve particular attention in Australia because daylight-saving changes can shift an hourly job unexpectedly. Test a cron task before relying on it for invoices, email campaigns or membership renewals.

Point the domain to HostGator

Once the new site works through a temporary address, prepare its DNS settings. If the domain is registered with HostGator, set its nameservers to the values supplied for that account. If it is elsewhere, change the nameservers or relevant records at the current registrar. A .com.au or .au domain has specific eligibility, registrant and Australian Domain Name rules, so check the requirements before initiating a transfer or replacing responsible contacts.

Lower the TTL for the affected records at least 24 to 48 hours beforehand and save the existing DNS configuration. After the switch, allow for propagation rather than expecting every visitor to see the change immediately. Keep email records and external integrations in mind: moving a web address can leave an old payment platform, analytics property or mailing service pointing at the wrong domain. Update those services separately.

Secure the destination with an SSL certificate and verify that the preferred hostname and its www version work without browser warnings. HostGator’s supported automatic certificate service is generally the simplest option for shared hosting, although an old purchased certificate may need to be reissued. Redirect the alternative hostname to the preferred one after testing. Clear any content delivery network cache during the change so visitors do not receive a mixture of old and new pages.

Run a staged cut-over checklist

Test the destination before it becomes public. Use HostGator’s temporary preview address, where available, or a hosts-file entry on a test computer. Open important pages, test forms, log into the CMS and create a test order without completing a live payment. Check mail sent through webmail and confirm that password-reset messages arrive. For an Australian shop, verify prices, GST treatment and shipping information for customers in different states. Compare the new website with the old one instead of trusting a successful homepage load.

Plan the final cut-over as a short, deliberate freeze. Publish outstanding content changes, take a fresh database export, upload the last file changes and run the final import. Place a maintenance notice on the old site during the highest-risk period. Follow safe work practices by naming a rollback point, limiting who can make changes and recording each completed upload. Keep the old hosting and domain services active until the destination has passed its checks.

After changing DNS, monitor HostGator’s error logs and contact forms, then check them again after a scheduled scan or backup. Verify HTTPS, webmail, reset emails, analytics and automated jobs. Do not cancel the old account immediately, because hosting, domain and SSL renewals can have separate due dates, and duplicate invoices are easier to reconcile than a missing website.

Before the DNS switch

After the DNS switch

Remember the essentials after launch

Treat the migration as the beginning of ongoing administration. Keep cPanel and webmail access available to the right people, review billing and invoices before renewals and use the domain purchase or transfer area for registration changes. HostGator’s video tutorials, knowledge base, ticket support and online forums can answer routine questions, while a support ticket is better for account-specific faults.

Maintain the website after launch by updating the CMS, plugins and extensions, removing unused accounts and enabling two-factor authentication for cPanel and email. Test a restore from a recent backup, renew the domain and hosting before their due dates and document who receives expiry notices. If the site collects personal information or sends marketing email, review its obligations under the Australian Privacy Principles and Spam Act 2003 rather than treating launch day as the end of compliance.

The durable rule is simple: back up first, move files and data in a tested order, switch DNS only when the destination works and retain a rollback path until confidence is earned. The finished site should remain easy to find, secure and maintain on HostGator long after the migration day has passed.