Changing Website Agencies in Australia: A Practical Handover Checklist
Check domain access, hosting, content, source files, analytics and recovery procedures before a website supplier handover.
Before changing website agencies, verify that your business can access the domain, hosting, content, analytics and recovery process. Ask the outgoing and incoming suppliers to work from one written handover register, with an owner and an acceptance check for every item.
Receiving a ZIP file does not necessarily give you a deployable website. Receiving a login does not establish that your business holds the account or the rights to every asset. Check both access and the relevant agreements before closing the engagement.
Keep the domain separate from the website project
Record the registrar, registered holder, renewal date and account recovery method. For .au domain names, auDA explains that the registrant details determine who holds the licence. Its guidance on third-party management says a developer registering or renewing a name on your behalf should not be listed as the registrant instead of the eligible business or individual.
Changing a website supplier does not inherently require changing the domain name. Distinguish access to manage the account, transfer between registrars and a change of registrant. Use the registrar’s process for the action actually needed. auDA provides a guide to .au transfers.
Never put passwords or transfer codes in a shared project checklist. Record where authorised access is managed and who can grant it.
Build an asset and access register
| Item | Acceptance check |
|---|---|
| Domain and DNS | A business-controlled account can review records and renewal settings |
| Hosting and deployment | The incoming maintainer can publish a harmless change and roll it back |
| Website content | Pages, media and any required exports are available in a usable format |
| Source and build instructions | A fresh checkout or platform copy can be built without the outgoing supplier’s laptop |
| Fonts, photos and extensions | Licence terms and transfer restrictions have been reviewed |
| Analytics and Search Console | Appropriate business users retain access to the existing properties |
| Forms and integrations | A synthetic enquiry reaches the intended destination after the handover |
| Backups | A restoration has been demonstrated, with a named recovery owner |
Some hosted builders do not provide portable source code. In that case, document exactly what can be transferred or exported, and what must stay on the platform. Make that limitation visible before promising a migration.
Test the dependencies that are easy to miss
An illustrative Perth consultancy is moving maintenance to a new supplier while retaining its existing website. The obvious assets are the pages and logo. The less obvious dependencies are the booking calendar, enquiry destination, DNS email records and analytics access.
The business creates a short register with one row for each service, its account owner and the verification needed. The incoming supplier first tests the site on a private preview. They do not change the live domain simply because the preview looks correct.
Check embedded calendars, maps, paid extensions and scheduled tasks. Record which subscriptions are paid by the business and which were bundled into the old service. Obtain replacement arrangements before the old supplier cancels anything on which the website depends.
Preserve working URLs where practical
An agency change is not a reason to rename every page. If URLs must change, map each old URL to its relevant replacement and test the redirects. Google’s site-move guidance covers redirects, updated internal links and monitoring during URL changes.
Keep the original Analytics and Search Console properties unless there is a specific reason for a new setup. Historical data is useful for comparing performance after the move. A screenshot of the dashboard is not equivalent to ongoing access.
Do not combine a supplier change, domain change, complete content rewrite and form replacement without a deliberate migration plan. A smaller sequence makes failures easier to isolate.
Accept the handover through a demonstration
Ask the new maintainer to demonstrate:
- Editing a page and publishing it safely.
- Restoring the previous version.
- Receiving a valid test enquiry and handling a failed one.
- Updating an integration without exposing credentials.
- Finding renewal dates and recovery contacts.
- Explaining what ongoing maintenance includes and excludes.
Backups need a restoration check, not just a “backup enabled” setting. The Australian Cyber Security Centre’s cloud responsibility guidance includes checking responsibilities for backups and testing recovery.
Once the handover is accepted, remove unnecessary supplier access through each service’s normal controls. Preserve the records and licences your business needs; do not delete accounts indiscriminately.
For a new build or redesign, include these requirements in the project brief from the start. Vendrato’s website service can help scope a handover alongside the design and development work.