Skip to content

Provider transition

Change providers without losing control of your environment.

The riskiest weeks in any provider change are the handover: credentials nobody transferred, undocumented systems, backups nobody checked. In two to three weeks we take control of access, find the gaps, baseline the risks and stabilise the environment, whether we are replacing a provider or working alongside one.

Row of server racks with blue status lights reflected in a polished floor.

Who it is for

Organisations leaving an MSP, losing a key contractor or engineer, or adding North Ark alongside an existing provider for the engineering work. It also suits acquirers taking on an environment run by someone else.

Sample layout of an Infrastructure Review report: a ranked findings table with priority markers, and behind it a page with an architecture diagram and a numbered sequence of actions.
Sample layout.

What we cover

  • Access and credential handover: admin accounts, break-glass accounts, service accounts, vendor portals and licensing accounts
  • Discovery: servers, cloud subscriptions, Microsoft 365, network devices, backups, certificates, DNS and third-party services
  • Documentation gaps: what was handed over compared with what exists
  • Risk baseline: the issues found, ranked by impact and likelihood
  • Stabilisation plan: what to fix in the first 30 days, and in what order
  • A responsibility matrix if the outgoing or remaining provider keeps any services
  • The first monthly report, so you can see the starting point

Replacing a provider, or working alongside one

If the provider is leaving, we plan the handover against their exit date and make sure every credential and dependency moves. If the provider is staying for the service desk or devices, we agree the split of responsibilities and the handoffs before we take on the engineering.

How it runs

  1. Plan: the exit date, what the outgoing provider must hand over and the access we need.
  2. Take control: credentials rotated, accounts removed and access set up to least privilege.
  3. Discover and baseline: inventory, documentation gaps and risks recorded.
  4. Stabilise: backups, patching, monitoring and certificate expiries dealt with first.
  5. Report: the first monthly report and the plan for the next quarter.

Questions buyers ask

Our current provider isn't cooperating. Can you still take over?

Usually. With your admin access we can take control of most systems directly. We plan for the gaps and tell you early what needs the outgoing provider or a vendor to resolve.

How much notice do we need?

The earlier the better. A few weeks before the exit date gives time to plan the handover rather than recover from it.

Do you take over the service desk as well?

We can. A service desk is part of Managed Microsoft 365 and security, or your current provider can keep it while we take the engineering.

What happens after the assessment?

If you move into Managed infrastructure, Managed Microsoft 365 and security or full Managed Engineering, the assessment becomes the onboarding.

Can we use the findings with another provider?

Yes. The inventory, risks and plan are yours.

Start a conversation

Take control before the handover date.

Tell us who runs your environment today and when that changes.

Talk to an Engineer