How to transfer a WordPress site to HostGator

Moving a WordPress website to HostGator involves copying its files, exporting its database, updating configuration details and directing the domain to the new server. A careful transfer can usually be completed with little disruption, provided the existing site remains available while the new installation is prepared and tested.

The process is relevant for Australian businesses, bloggers, online shops and community websites moving from another host or a local development environment. A Melbourne retailer, a Brisbane tradesperson or a Sydney agency may have different domain, email and time-zone requirements, yet the core migration steps remain similar.

Before starting, make a complete backup and record the current hosting details. Keep your old hosting account active until the replacement site works correctly, email has been checked and DNS changes have had time to spread across Australian networks and international resolvers.

Prepare the existing WordPress installation

Begin by listing everything that must move: the WordPress files, database, uploads, themes, plugins, media libraries, custom fonts, redirects and any scheduled tasks. Record the current PHP version, WordPress version and active plugins as well. This inventory makes it easier to identify a compatibility issue when the site is running on HostGator.

Create two separate backups rather than relying on a single copy. Download the complete public_html or document-root folder using SFTP or the current host’s file manager, then export the database from phpMyAdmin in SQL format. Store the files and database somewhere outside the old server, such as an encrypted local drive or a trusted cloud location. A backup is useful only if it can be opened and restored.

Take screenshots or notes of DNS records, email accounts, forwarding addresses and existing redirects. For an Australian business using a .com.au domain, check the registrar account and confirm that the registrant information remains accurate under auDA requirements. If the website accepts Australian dollars or uses services such as Australia Post, Stripe or Afterpay, record the relevant settings before any plugin is deactivated.

Review the content before copying it. Remove abandoned plugins, clear temporary cache folders and check that internal links use the correct domain. If the site contains specialist editorial pages, preserve their slugs and metadata; an article with a specific address, such as free spin information, should continue to resolve to the same path after the move.

Set up the HostGator account

Log in to the HostGator customer area and confirm that the hosting package is active. The account dashboard should provide access to cPanel, billing and invoices, domain management, support tickets and other account tools. Keep the invoice and package details available, especially if the website is operated by a business that needs Australian GST records for bookkeeping.

Add the domain in cPanel if it was registered elsewhere. Depending on the hosting arrangement, it may be the primary domain, an addon domain or a temporary address used while the site is being assembled. Do not change nameservers immediately if the old website is still serving visitors. Building the replacement first gives you a safe testing period.

Create the database and database user in cPanel, then assign the user to the database with full privileges. Write down the database name, username and password exactly as displayed. Host-generated database names often contain an account prefix, so a name copied from a local development environment may not work on the new server.

Check the hosting environment before uploading anything. Confirm the available PHP version, storage limits, SSL options and maximum upload size. A large Australian WooCommerce catalogue or a photography portfolio can exceed default upload limits, while a small brochure site may transfer easily through the cPanel file manager. HostGator’s knowledge base and video tutorials can help with cPanel tasks, while ticket support is useful if an account-level setting prevents installation.

Move the files and database

Upload the WordPress files to the correct document root, commonly public_html for the primary domain. SFTP is generally preferable for large transfers because it is more reliable than uploading hundreds of individual files through a browser. If a compressed archive is used, upload it first, extract it on the server and check that WordPress files are not buried inside an extra folder such as public_html/wordpress/.

Import the SQL backup through phpMyAdmin. Select the newly created database before using the Import function, and check that the upload size and execution limits can handle the file. Very large databases may need to be imported in sections or through a command-line method supported by the host. Never overwrite a live database without first confirming its name and taking a fresh backup.

Open wp-config.php and replace the old database name, username, password and database host with the HostGator values. In many cases the database host remains localhost, though the account documentation should take priority. Keep the authentication keys and salts unless there is a specific security reason to regenerate them.

If the transfer includes a large media library, compare the number of files and the total size on both servers. Missing images are often caused by an incomplete wp-content/uploads transfer rather than a WordPress configuration problem. Make sure file permissions are sensible, with directories commonly set to 755 and files to 644 unless a plugin or host requirement calls for something different.

Update URLs and WordPress settings

If the domain name is unchanged, WordPress may load immediately once the files and database are in place. If the site was developed on a temporary URL, localhost or a staging subdomain, update the siteurl and home values in the wp_options table. Use a WordPress-safe search-and-replace tool for the rest of the database, because serialized settings can break when edited with a basic text replacement.

Avoid changing every occurrence of the domain manually in a text editor. Search for old HTTP addresses, temporary hostnames and development paths in menus, widgets, page builders and plugin settings. A proper migration utility can adjust serialized data while preserving image galleries, builder layouts and widget configuration.

Keep the existing permalink structure. Visit Settings, then Permalinks in the WordPress dashboard and save the current structure once, which refreshes rewrite rules and may regenerate the .htaccess file. Check custom post types, category pages and pagination as well as ordinary pages.

Preserve search visibility during the move. Review canonical URLs, XML sitemaps, robots.txt, redirects and analytics tracking. If a page must change address, create a permanent 301 redirect rather than allowing an old URL to return a 404 error. This matters for local search results, whether customers are looking for a Perth electrician, a Canberra consultancy or a café in Adelaide.

Inspect external links and embedded content as part of the content check. A migrated specialist page about Martingale strategy should retain its intended slug, title and outbound references if those elements form part of the original editorial structure. Link preservation helps prevent broken-content reports after launch.

Move email, DNS and security settings

Website files and domain DNS are separate systems. Changing the nameservers tells the domain where to find its DNS zone, while changing an A record points the website to a particular server. Before making either change, copy the existing MX, TXT, CNAME and verification records. Missing MX records can stop mail delivery even when the website appears perfect.

Decide whether email will remain with the current provider or move to HostGator. If it is moving, create the same mailboxes and forwarding addresses in cPanel before changing DNS. Test webmail and an email client using both sending and receiving addresses. An Australian organisation working across Sydney and Perth should also check that staff devices use the correct account settings rather than relying on an old saved password.

When ready, update the domain’s nameservers or A record according to the HostGator setup instructions. DNS propagation is not instantaneous; some visitors may see the old server while others reach the new one. Keep both environments available during this period and avoid making content changes on the old site unless you plan to repeat them on the new installation.

Install and verify the SSL certificate after the domain points to HostGator. Visit the site with https://, check that the certificate covers the root domain and www version where required, and resolve mixed-content warnings. Update WordPress and site URLs to HTTPS only after the certificate is active, then test forms, payment pages and login screens.

Use the transfer as a security checkpoint. Delete temporary archives, old migration scripts and unused administrator accounts from the server. Review file permissions, enable sensible login protection and keep a copy of credentials in a trusted secure storage guide rather than in an unprotected text file. Security settings should be checked again after all plugins are reactivated.

Test the new site before launch

Test the temporary HostGator version before announcing the move. If the domain still points to the old host, use a hosts-file preview, a temporary URL where appropriate or a staging domain. Check the homepage, navigation, search, contact forms, image galleries, downloads, user registration and any membership or ecommerce functions.

For WooCommerce, place a test order and inspect payment callbacks, tax calculations, shipping zones and confirmation emails. Confirm that prices display in Australian dollars, GST behaviour matches the business’s requirements and delivery settings cover the intended states and territories. Do not use a live card for testing unless the payment provider offers a clearly marked test mode.

Test from several devices and connections, including a mobile network and a fixed NBN connection. Check the site at common Australian screen sizes and verify that page speed has not deteriorated because of missing caching, oversized images or a different PHP configuration. A visitor in Hobart should receive the same core content as one in Darwin, even if DNS resolution takes different amounts of time.

Use WordPress Site Health, browser developer tools and server error logs to find warnings. Pay particular attention to 404 responses, redirect loops, database connection errors, missing stylesheets and blocked JavaScript. Re-save permalinks, clear plugin and server caches, and regenerate page-builder assets when a layout looks incomplete.

Once testing is complete, change DNS and monitor both versions. Watch uptime, analytics, form submissions, transaction notifications and email delivery for at least several days. Keep the former host active until traffic consistently reaches HostGator and no important service depends on the old environment.

After the domain has settled, remove the old installation or cancel the previous plan only after downloading final records and confirming that backups are current. Update billing contacts, domain renewal details and internal documentation. HostGator’s forums, knowledge base, tutorials and support tickets can provide a useful record of any remaining configuration issue.

A successful WordPress transfer is a controlled handover rather than a single upload. Back up the old site, build the new account privately, copy files and database data, preserve URLs, protect email and test every important customer path. The practical rule is simple: keep the old site available until the new HostGator version has been checked from the front end, the dashboard, email and any revenue-generating workflow.