Practical planning guide · Published 12 November 2026 · Automated Australia
Start with the services your website depends on: the domain registrar, DNS provider, host, email provider, forms, booking tool and any payment connection. A website can load correctly while its enquiries or business email are broken. Treat those journeys as part of the handover.
1. Confirm business-controlled access
Know who owns each account and how the business can regain access if a staff member or supplier becomes unavailable. Prefer named accounts and appropriate access levels. Agree how credentials will be transferred securely; do not put passwords, recovery codes or private customer data in a public brief.
2. Inventory what must be backed up
A copy of the visible web pages may not contain the database, uploaded files, form submissions or configuration needed to recover the service. List what is included, how often it is saved, where copies are stored and how long they are retained. Ask how much recent work could be lost and what must be rebuilt manually.
Test a restore to a separate environment and check a useful task, such as retrieving a record or completing a test enquiry. A “backup completed” message is not the same as a demonstrated recovery. The Australian Government's small business cyber security handbook recommends regular backups and testing that they can be restored.
3. Check the services around the website
Record DNS settings before changing them, especially email records. Keep the current site available until the new environment and rollback route have been checked. Verify the main and www addresses, redirects, certificate, forms, booking links and any necessary integrations after the move.