Move files, databases, DNS — and the n8n webhooks or AI callbacks that break if you only migrate the website.
Migrating to Melbourne hosting: the full checklist
A migration fails quietly when the homepage works and the automations do not. Move the files, the database and DNS — then move the webhooks, cron URLs and OAuth callbacks that are still pointing at the old server. The second list is what turns a clean cutover into a week of mystery bugs.
Key takeaways
- Build an inventory before you touch anything: apps, runtime versions, mail, integrations.
- Get the site working on the new server before any public DNS points at it.
- Lower DNS TTL a day ahead so the cutover propagates in minutes.
- Change web records and mail records as separate, deliberate steps.
- Webhooks, cron jobs and OAuth redirect URIs are the most-missed items on every migration.
Steps
- Inventory what you are moving: application type, PHP or Node version, database, mailboxes, cron jobs, integrations.
- Provision the matching plan — React, Laravel, Business or n8n — from the hosting range.
- Copy files and export/import the databases.
- Test on a staging URL or a local hosts-file entry until the site is genuinely working.
- Lower the TTL on the records you will change, at least a day ahead.
- Cut over the
AandAAAArecords; changeMXonly if mail is moving too. - Confirm SSL is issued for every hostname, including
wwwand any subdomains. - Watch the error logs for 24 hours, then raise the TTL again.
Before you start: the inventory
Half the pain in migrations comes from discovering a dependency after the cutover. Write all of this down first:
- Runtime. PHP version, Node version, extensions the application needs, Composer or npm build steps.
- Database. Engine and version, size, and whether anything connects to it from outside the server.
- Mail. Which mailboxes exist, where they are hosted now, and whether they are moving.
- Scheduled work. Cron entries, queue workers, anything that must be running for the app to be correct.
- Integrations. Every external service that calls your domain or that you call with a stored credential.
- DNS. The full current zone, exported, not remembered.
The automation inventory most checklists skip
This is the list that matters and the one nobody has:
- Webhook destinations in payment providers, form handlers and automation platforms. Each one holds a URL you must verify still resolves correctly.
- n8n workflows. Export them before DNS moves, and re-point webhook URLs in the same window. n8n Hosting is the plan for running them in Australia.
- OAuth redirect URIs in Google, Microsoft and any other identity provider. These are exact-match and fail closed.
- Cron URLs hit by an external scheduler rather than by the server's own crontab.
- API keys stored only on the old server. If a key exists only in an old
.envyou are about to delete, you will not get it back. Rotate it deliberately. - Allowlisted IP addresses. Anything that permitted the old server's IP needs the new one added before cutover, not after.
Switch webhook destinations in the same window as DNS, so retries do not split across two hosts and get processed twice.
Why Melbourne
Serving Australian visitors from Melbourne removes an international round trip on every request. That is most noticeable on anything interactive — dashboards, carts, logged-in pages — where multiple sequential requests each pay the latency. Web hosting in Melbourne covers the infrastructure, and migration covers what help is available.
After the cutover
- Confirm mail flows in both directions with a test to and from an external address.
- Re-check SPF and DKIM if the sending host changed. This is where deliverability quietly breaks a week later.
- Watch the application error log, not just the homepage.
- Confirm cron entries and queue workers actually started on the new account.
- Leave the old account in place for a short overlap rather than cancelling it the same day.
Frequently Asked Questions
Do you help with migrations?
The migration page covers what is included. For anything unusual — a large database, an uncommon runtime, a tight window — raise it through contact before you book a date.
Should I move automations before or after DNS?
Prepare them beforehand and switch the destinations in the same window as the DNS change. Splitting the two means retries land on two different servers and may be processed twice.
Will my email go down during a hosting migration?
Not if mail is not moving. Change only the A and AAAA records and leave MX, SPF and DKIM untouched. If mail is moving, treat it as a separate scheduled change.
How long should I keep the old hosting account?
Long enough to confirm nothing was missed — typically a billing cycle. Cancelling the same day removes your fallback and any configuration you did not copy.
What breaks most often after a migration?
Scheduled jobs that were never recreated, and webhooks still pointing at the old hostname. Both fail silently, which is why they belong on the inventory before you start.

