Switching IT partner: how it works (without the hassle)

Switching IT partner takes four to eight weeks in practice and almost always turns out fine — provided you arrange four things in advance: the ownership of your tenant, domain and DNS, your notice period (usually one to three months), a complete handover of access and documentation, and a new partner who takes the lead. With a proper approach your team barely notices anything: mail, files and applications simply stay put; only the management and the point of contact change. In this article we walk through the whole switch, from the first check to the final week.

When is switching sensible?

Switching is sensible once your IT partner has become structurally reactive: you report faults more often than they prevent anything, and no one can explain to you exactly what the monthly fee goes towards. One bad week is no reason to change; a pattern is. The signals we see most often in practice:

• Reactive instead of proactive. Something only happens once you call — you notice nothing of monitoring, updates or prevention.
• No documentation. Knowledge of your environment sits in one person's head at the provider, not on paper.
• Everything is extra work. Every question outside the contract results in a quote, so small improvements keep getting left.
• Security is neglected. No MFA on all accounts, former employees who still have access, a backup that has never been tested.
• You've outgrown them. The party that was fine at eight workstations is structurally short-handed at forty.

If you recognise three or more of these points, the question is not whether you should switch, but in what order you tackle it. And that order does not start with the notice of termination, but with an ownership check.

First check: who actually owns your environment?

Your Microsoft 365 or Google Workspace tenant, your domain name and your DNS management should be in your company's name — not in your IT provider's name. This is the most important check of the whole switch: if ownership is in order, no one can hold you back; if it is in the provider's name, you arrange the transfer of that before you cancel. Run through these five points:

• 1. Tenant. Is your Microsoft 365 or Google Workspace environment in your company's name, and does someone within your organisation have an administrator account themselves? Licences that run via the provider (a CSP arrangement) are normal; a tenant in the provider's name is not.
• 2. Domain name. Check who is registered as the holder of your domain — for .nl domains you can do that via the SIDN whois. The holder should be your company.
• 3. DNS management. Know where your DNS runs and whether you can access it yourself. Whoever manages the DNS effectively manages your mail and your website.
• 4. Passwords and documentation. Request an up-to-date overview: admin accounts, wifi, application management, licences. Whatever is not documented has to be figured out during the handover anyway.
• 5. Hardware and ongoing contracts. Which equipment is rented or leased via the provider, and which licences or subscriptions run through them? You convert those or buy them off.

If everything is yours, the rest of the switch is mainly a matter of planning. If the tenant or domain is in the provider's name, first request the transfer in writing — virtually every party cooperates with that, but it takes lead time you don't want falling within your notice period.

Your contract: notice period, renewal and data processing agreement

For IT management contracts a notice period of one to three months is common, often combined with automatic annual renewal. So first check your end date and your renewal moment: whoever cancels a week too late is sometimes stuck with the old contract for another year. Plan the switch around that, not the other way around.

Also look at the data processing agreement. Your IT partner processes personal data on your behalf, and a proper data processing agreement sets out what happens to data and access at the end of the collaboration — return or deletion should be included as standard. If such an agreement is missing, that is a signal in itself, and something to record straight away with the new partner.

The notice of termination itself does not have to be a legal masterpiece. Make sure it states:

• your company details and the contract or customer number;
• an explicit cancellation against the end date, with reference to the notice period in the contract;
• a request for written confirmation of the cancellation and the end date;
• a request for cooperation with the handover: access, documentation, admin accounts and open tickets;
• the contact person at the new party who coordinates the handover.

One timing tip that prevents a lot of hassle: only cancel once the ownership check is complete and the new partner is ready. That way there is never a gap in which no one is responsible for your environment.

The handover itself: four to eight weeks, without interruption

A complete handover takes four to eight weeks in practice, and the core is overlap: the new party gets admin access alongside the old one, takes over management step by step, and only then is the old access closed. There is no "big bang" moment and nothing needs to migrate — you're changing administrator, not system. Here is how it looks per phase:

• Week 1–2: inventory. The new party gets admin access and maps the environment: users, licences, permissions, devices, DNS, open items. This is usually where the first quick wins also surface.
• Week 3–4: handover of management. Documentation is taken over or rebuilt, monitoring and alerts are switched over, and your team gets the new support channel. Acute security gaps — MFA that's off, accounts of former employees — are closed straight away.
• Week 5–6: contracts and ownership. Licences and ongoing subscriptions are converted where necessary, and domain and DNS management come (back) under your control.
• Week 7–8: completion. The old party's access is revoked, admin accounts are cleaned up and a verification round follows: is the documentation correct, is monitoring running, is the backup tested.

And the old party? Most providers cooperate professionally — a proper handover is the fastest route for them too. More importantly: if you own the tenant, domain and DNS, an unwilling party can at most delay you, never hold you back.

How RiverFlows handles the takeover

We take over management in four steps: inventory, getting things in order, managing, optimising. In the inventory we map your systems, licences, access and bottlenecks — often we find quick wins there straight away. Then we close security gaps, clean up old accounts and set management and monitoring up tightly. Next we become your fixed point of contact: support for your team, proactive monitoring in the background, and we resolve open items from the previous party along the way — without interruption for your team.

The arrangements around it are deliberately simple. We work with a fixed monthly fee per user (as an indicative price for 2026: €40 to €90 per user per month, licences separate — the breakdown of that is in What does IT management cost?). A data processing agreement is a standard part of the collaboration, we use MFA on all admin accounts and we only get the access needed for the work. And perhaps most important for anyone who has just had a mediocre experience: everything stays in your tenant, documentation and access remain your property. No lock-in — not with us either. We manage both Microsoft 365 and Google Workspace; what exactly falls under the management, you can read on outsourced IT management.

The first step is small: first a message, then a short video call, then a fixed-price proposal — you decide.

Read more

• Outsourced IT management: what it involves
• Microsoft 365 management by RiverFlows
• What does IT management cost?
• NIS2 for SMBs: what to arrange before 1 July 2026?
• Free Operations Scan

Frequently asked questions

Written by Hugo Eleveld · Updated June 2026. This article is informational; for tailored advice book an intro call.