Using the HostGator Migration Tool for WordPress

Moving a WordPress site involves more than copying files and a database. URLs, media, plugin settings, database values, and hosting rules all need to arrive intact at the destination. The HostGator Migration Tool is designed to automate the bulk transfer into a HostGator account, reducing manual work while giving you a controlled path from an existing host.

The tool does not remove the need for preparation. A safe move depends on a recent backup, accurate source details, testing on the destination, and a careful DNS change. Email and domain registration may also require separate work. Keep the original hosting active until the new installation has been checked thoroughly.

Plan the move before changing the site

Start by deciding whether the site is suitable for an automated transfer. A conventional, single-site WordPress installation on cPanel or similar shared hosting is usually the simplest case. Multisite networks, unusually large databases, advanced cron jobs, custom PHP applications, and heavily customised stores may need additional planning or manual intervention. Make an inventory of themes, plugins, custom code, and required PHP versions before anything changes.

Create two independent backups: a complete file archive and a database export downloaded somewhere outside the source account. Record the current WordPress version, database prefix, active theme, and all custom settings. If the site contains customer orders, bookings, memberships, or submissions, make the backup at a point when those records are consistent. The old installation should remain readable during the move.

Choose a maintenance window that suits Australian visitors. Sydney, Melbourne, and Canberra follow Australian Eastern Time, which shifts by an hour during daylight saving, while Brisbane stays on Australian Eastern Standard Time and Perth uses Western Standard Time. For a busy Australian business, an early-morning weekend slot may still overlap with customers in other states or overseas. Also check that the existing .com.au or .au domain and its DNS provider are known before touching nameservers.

Prepare WordPress and the destination

Prepare the HostGator destination before starting the transfer. Confirm that the account and hosting plan provide access to the migration feature, then sign in to cPanel. Create the destination directory, note its exact path, and decide which hostname the copied site will use while the main domain still points elsewhere. Match the destination PHP version to the source where possible, especially when the site uses an older theme or plugin.

The migration interface may ask for the source installation path, admin URL, and database credentials. In WordPress, the database name, user, password, and prefix are recorded in wp-config.php, while the site files sit under the folder containing wp-content and wp-admin. Keep the source online and reachable during setup. Temporarily allow the HostGator server through source security rules if a firewall blocks the connection, then restore any stricter access controls after the copy.

Check the source for hard-coded server addresses, outdated API endpoints, scheduled tasks, and references to the former host. Update WordPress core and plugins beforehand only if the site is already stable, since a last-minute compatibility change can introduce a separate problem. Keeping a few migration accessories nearby—such as a printed DNS record sheet and a spare USB drive—can be useful during the move. Save migration notes outside the browser and never include database passwords in screenshots.

Run the migration from cPanel

In cPanel, locate the HostGator migration feature. Depending on the account and current cPanel release, it may appear as Migrate WordPress, Migrate Site, or within a WordPress management area. Select the source installation and the empty destination, then enter the paths and connection details requested. If the destination contains an existing WordPress copy, back it up and move it out of the way rather than allowing two installations to be overwritten.

Start the transfer and let it finish without uploading another archive or changing the source database at the same time. A typical run copies themes, plugins, uploads, and WordPress content, then creates or updates the destination database. Some jobs also install WordPress automatically; others expect a prepared application directory. Record the completion time and any warnings. Cached files, generated media, or a timeout can affect large jobs, so repeated restarts should be avoided until the error has been reviewed.

If the job stalls, verify the source URL, folder permissions, database access, and available disk space before retrying. Large media libraries may need a manual archive or a longer transfer window. If the feature is missing, ask HostGator ticket support to confirm plan availability and provide the appropriate migration route. The knowledge base, video tutorials, and customer forums can help locate current menu guidance, but a ticket is preferable for account-specific database or permission failures.

Check data, links, and email

Test the copied site using its temporary HostGator address before updating DNS. Open the home page, sample posts, product or booking pages, media, search, login, and checkout flows. Submit a test form and check that administrator notifications arrive. Confirm that administrator and customer accounts work, and that the URL paths for WordPress administration and AJAX requests have not changed. A visually complete home page is not enough if forms, menus, or protected areas fail.

Inspect the database for the new site address, then check HTTPS, redirects, canonical URLs, and mixed-content warnings. Visit the WordPress Settings and Permalinks pages so WordPress can confirm its saved URL structure. Look for references to the old IP address in configuration files or plugin options. Database-driven content should also be checked for missing characters, broken relationships, and incorrect prices or dates, while payment and booking integrations should be tested without creating duplicate real transactions.

Treat email as a separate cutover. Copying web files does not move active mailboxes; the destination webmail account may be empty, and mail flow still depends on MX, SPF, DKIM, and DMARC records held by the DNS provider. Update those records in the planned sequence and test both incoming and outgoing messages. Australian organisations should also review Australian Privacy Principles, Spam Act obligations, and the consent wording on customer forms so migrated personal information and marketing messages remain lawfully handled.

Cut over and keep a rollback path

Two cutover methods produce different levels of risk. Migrating to a temporary address and changing DNS only after testing preserves the strongest rollback position. Changing DNS at the start may shorten the final interval, but it exposes visitors and automated processes to an incomplete site. For a WordPress installation handling sales or bookings, preserving control usually matters more than saving a few minutes.

Cutover approach	How it works	Main advantage	Main risk
Migrate before changing DNS	The site is copied to a temporary address, tested, and then the domain records are updated	Best rollback protection and a controlled final change	A final data sync may be needed if the site continues changing
Change DNS before transfer	The domain starts pointing to HostGator while files and the database are still moving	The formal switch occurs early	Downtime, stale SSL, and broken automation are more likely

Use a short DNS propagation period as the cutover approaches. Lower the relevant TTL records at least a day in advance, then keep the source online until the destination copy is final. For sites receiving new orders or comments, pause changes briefly so the last data can be transferred or reconciled. At cutover, point the domain’s A, AAAA, or CNAME records to HostGator, install or activate the correct SSL certificate, and confirm that both www and the preferred redirect behave as intended.

A domain transfer is separate from hosting migration. Whether the name is .com.au, .au, or another extension, keep the registrar and nameservers stable until the new host is stable. Australian customers often budget in Australian dollars, so the HostGator billing area should be used to check invoice currency, whether GST applies, renewal dates, and payment methods before renewing the new plan. After DNS has settled, watch server logs, forms, orders, and scheduled tasks while retaining the old host temporarily as a rollback source.

The essential lesson is to treat a WordPress move as a controlled handover: preserve a tested backup, migrate while the original stays available, verify content and connections on the destination, and switch nameservers only after the new site has passed its checks. Keeping records of every path, DNS change, and support response makes the move repeatable and gives the business a clear recovery route if something behaves differently after launch.