Changing IT providers: a practical onboarding checklist
Changing IT providers should make the business safer and easier to support, not leave everyone locked out of systems or unsure who owns what. The key is a structured handover: identify the important systems, confirm business ownership of accounts and licences, capture documentation, protect backups and security controls, then agree on who is responsible at each stage.
Last updated
The short answer
Before a new IT provider starts work, make sure the business (not an individual technician) controls its key domains, Microsoft/Google tenancy, backups, internet services, admin accounts, licences and vendor relationships. Document the current environment, agree a transition plan, and avoid turning off the previous provider's access until the new arrangement has been tested.
What IT-provider onboarding should achieve
Onboarding is the controlled process of moving responsibility for technology support to a new provider. It should give the business an accurate system record, clear ownership of key accounts, safe administrator access, an agreed support process and a plan for any gaps discovered during the review.
The handover checklist
Business ownership of core accounts
Confirm that the business controls domains, DNS, email tenancy, cloud services, internet services, backup accounts and software subscriptions, with recoverable contact details and payment ownership.
Administrator access and recovery
Record legitimate administrator accounts, recovery methods and emergency contacts. Remove stale access only after replacements are confirmed and tested.
Systems and asset inventory
List users, devices, servers, network equipment, cloud systems, line-of-business software, vendors and locations. The list does not need to be perfect on day one, but unknowns must be visible.
Security and backup review
Identify security tools, MFA, email protection, monitoring, backup scope and recovery responsibilities. Confirm what is monitored and what is merely assumed.
Support process and escalation
Agree how staff request help, who can authorise changes, what is urgent, and how the business will be kept informed during a significant issue.
Transition and exit plan
Set dates, responsibilities and a clean handover point. Keep the previous provider's access long enough to prevent disruption, but not indefinitely.
Who this is for
- Business owners changing managed IT providers.
- Teams bringing support in-house or moving from an informal arrangement to a structured provider.
- Businesses that do not have a clear record of their domains, cloud accounts, backups and supplier contacts.
- Organisations planning a merger, move, major system change or security uplift alongside a provider transition.
A safe transition sequence
- Agree the scope and roles. Set out what the new provider will manage, what stays with the business or another supplier, and who can make decisions during the transition.
- Collect facts before changing access. Gather account ownership, systems, licences, vendors, contacts, current security settings and known issues before deleting or replacing anything.
- Establish safe new access. Create or verify the new provider's access using named, controlled accounts. Test it before removing the previous arrangement.
- Validate the important services. Check email, key applications, backups, security alerts, remote access and support contacts against the agreed inventory.
- Close the handover deliberately. Document open issues, remove obsolete access, store the records where the business can retrieve them and confirm the ongoing support process.
How WaTo can help
- We treat the transition as a business-risk exercise rather than a simple password handover.
- We help establish business ownership and documentation instead of making the provider a single point of failure.
- We can review the wider environment: devices, cloud, backup, security, domains, hosting and business systems.
- We identify unknowns and open risks clearly, rather than pretending every environment is tidy on day one.
- We support Adelaide businesses on site and clients across Australia remotely.
Changing IT provider questions
Should we give the new provider every existing password?
Not by default. Start with a controlled inventory and establish named access through the correct business-owned accounts. Password sharing without ownership, MFA and documentation usually creates a new risk instead of solving the old one.
When should the old provider lose access?
After the new provider's access has been verified, critical services have been tested, open work is documented and the business has approved the handover. The exact timing should be agreed in the transition plan.
What if we do not know who owns our domain or Microsoft 365 tenant?
Treat it as an early priority. Collect invoices, recovery contacts, registrar details and existing administrator information, then work through the provider's formal recovery and ownership processes if needed.
How long should onboarding take?
It depends on the number of users, locations, systems and documentation quality. A good provider should explain the stages, dependencies and any immediate risks rather than promise a one-size-fits-all timeframe.
How WaTo can help with this
Guides on this topic
WaTo Consulting. Last reviewed 2026-10-04. Review after onboarding-process changes.
Planning a change of IT provider?
WaTo can help you map the environment, protect account ownership and make the transition without unnecessary disruption.
Mon to Fri, 8:30am to 5pm
