Home›Guides›Hosting and handover checklist
Practical guide Australian small business

Know who holds
the keys.

Hosting is more than a monthly server charge. Before a move or handover, check who controls the accounts, how recovery works and what your support agreement actually covers.

Before a hosting change

Make an account and responsibility map.

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.

Agree the operating scope

Turn broad promises into specific responsibilities.

4. Separate monitoring from response

Ask what is monitored, who receives an alert, the hours in which support is available and what a response includes. Detection, acknowledgement and repair are different events. Document routine updates, incident escalation and work that requires a separate quote.

5. Ask where data actually goes

A hosting region does not by itself describe every backup, analytics service, email provider or AI processor connected to a site. Request a list of relevant providers and data flows. For private AI, agree where inference runs, what leaves the environment and who can access logs. Avoid treating a label such as “private” as a complete technical specification.

6. Plan for a future supplier change

List the source files, data exports, licences, deployment instructions and account access included in the handover. Separate custom work from third-party services that remain subject to their own subscriptions and terms. Agree what assistance is included if you move later.

A useful acceptance record names the accounts, includes a restore result, records the live journey checks and identifies the support owner. Keep sensitive access details in an appropriate secure location rather than in the public report.

Bring your current host, the services that depend on it and the problem you want to solve to a managed hosting or private AI assessment. For a broader review, see our website and technical assessments and the audit of our own site.

  1. 1Send an enquiryAbout three minutes
  2. 2Choose a timeFree assessment
  3. 3Complete your briefAfter booking

Work out the next step.

Tell us what your business needs to do better. We can help define a practical assessment and a clear scope.

About three minutes. No account needed.
No obligation to book or buy.

Prefer email? Talk to Jesse ↗

Want to talk it through? Send this enquiry first, then choose a time for your free assessment.