Change partner without losing what they know.

Small changes take weeks. Every question goes back to the same supplier, and only they really know why the system works the way it does. Moving starts to feel riskier than staying.

The usual worry is a new partner who criticises the old one and quotes to rebuild everything. We won't. Most of what you have is usually worth keeping, and the handover audit tells you which parts are.

The audit is fixed-price, typically £7,500 to £12,500 plus VAT (£9,000 to £15,000 including VAT). It ends with a handover plan and a fixed price for the move.

Why changing partner feels risky

The knowledge is in their heads

Why a plugin exists, which flow feeds the finance system, what that nightly job is for. If none of it is written down, it leaves with the partner.

Some keys are in their name

Admin accounts, source code, release pipelines, app registrations and Azure resources are often set up under the partner rather than under you. Nobody notices until they're needed.

A gap in support

Between the old partner stepping back and the new one getting up to speed, something breaks and nobody owns it.

A rebuild nobody needed

A new supplier who doesn't understand what's there will want to replace it. That costs a lot and throws away work you've already paid for.

How the move works

  1. 01

    Handover audit

    Our health check, aimed at the handover. We read what's actually in your environments, list what's undocumented, and record who owns each account, repository and resource.

  2. 02

    Handover plan

    The questions to ask your current partner while they're still working with you, the access and code to bring into your own name, and a fixed price for the move.

  3. 03

    Overlap

    We work alongside your current partner for an agreed period, writing down what they know as we go, so nothing depends on one last call before they leave.

  4. 04

    Take over

    Releases go through a pipeline you own, and the platform is documented. From there it's a support plan, a monthly contract or project work, whichever suits you.

What stays the same

Your tenant and your data

Changing partner doesn't mean moving your environments or your data. Everything stays where it is, and your users carry on working.

What already works

We fix what's broken and leave alone what isn't. If something does need rebuilding, the audit says why and what it would cost, so you decide.

Your Microsoft licences

If your current partner also sells you your licences, those can move to another licensing partner too. Microsoft runs a partner-to-partner transfer that keeps your user counts and renewal dates. Your current partner has to approve it, so we plan it into the handover.

Your relationship with your current partner

Handovers go better when nobody is backed into a corner. We keep it factual and professional, and you decide when and how they're told.

Platforms we've inherited

One environment we took over had a single core table with more than 300 fields, built by a Microsoft Solutions Partner, and splitting it took months. The handover audit finds decisions like that before you build on top of them. The schema decisions we look for.

Leaving Dynamics 365 or an older platform altogether? See CRM migration.

Common questions

Do we need to tell our current partner before we start?

Not for the audit, as long as your own team has admin access to your environments. You'll need their cooperation for the handover itself, and the plan tells you exactly what to ask them for.

What if our current partner won't hand things over?

Most of what matters is already in your tenant: the solutions, the configuration and the data. The audit lists anything that isn't, such as source code or accounts in their name, so you can ask for it while they're still working with you.

Will you want to rebuild everything?

No. We fix what's broken and leave what works. If something does need rebuilding, the audit explains why and what it would cost, and the decision is yours.

How long does a handover take?

The audit takes about two weeks. The overlap with your current partner depends on how much is undocumented, and the handover plan gives you a date for it.

What happens to our Microsoft licences?

If you buy them through your current partner, Microsoft's partner-to-partner transfer moves them to another licensing partner with your user counts and renewal dates intact. Your current partner has to approve it, and we plan it into the handover so access isn't interrupted.