Taking over a website from another agency: a checklist
How to switch agencies safely — access, code, hosting, domains and documentation — with an interactive checklist to make sure nothing is missed.
How to switch agencies safely — access, code, hosting, domains and documentation — with an interactive checklist to make sure nothing is missed.
Protect ownership first
Make sure the domain, DNS, hosting and code repository are in your company’s name — not the outgoing agency’s.
RELATED GUIDEFlutter vs React Native in 2026: which should you choose? → Taking over an existing system?We adopt, document and maintain code other teams wrote.Get a free health check →Collect access
- Domain registrar and DNS
- Hosting / cloud accounts
- Code repository
- CMS / ecommerce admin
- Payment gateway and apps
- Analytics, tag manager, ad accounts
- Email and SMTP services
Audit before changing
Run a code, performance and security audit, document the setup and agree a stabilisation plan before new features.
Common mistakes to avoid
How we help with development
Frequently asked questions
What if the old agency won’t hand over code?
Check your contract for IP ownership; we can help recover access.
Will my site go down during the switch?
Not if planned properly — we move hosting and DNS carefully.
Do you document everything?
Yes — runbooks and access registers are part of onboarding.