YOUR SITUATION · SWITCH PARTNER

Your partner is not the problem you signed up for. Changing them does not have to be a project.

Slow response times, turnover on your account, a relationship that has quietly gone stale: switching Dynamics 365 partners is more routine, and less disruptive, than most people expect.

Why teams switch

It is rarely one dramatic failure. It is a slow accumulation of small ones.

Common reasons teams look elsewhere

  • 1
    Support tickets sit open for daysResponse time keeps slipping and nobody explains why.
  • 2
    Constant consultant turnoverYou are re-explaining your setup to a new person every few months.
  • 3
    You are the one explaining your own system to your own partnerInstitutional knowledge should live with the people supporting you, not just with you.

What a transition actually involves

  • ✓
    A licence and CSP transfer, not a re-implementationYour system keeps running. What changes is who supports it.
  • ✓
    A documented handover periodOverlap with your outgoing partner where practical, so nothing gets dropped.
  • ✓
    No re-training your team from scratchYour configuration, customisations, and data stay exactly as they are.
How the transfer works

Licence and support move over. Your data and configuration never do.

01

Assess

A read of your current configuration, customisations, and any open issues with your existing partner.

AI: config scan
02

Plan the transfer

CSP and licence transfer mapped out, with minimal disruption to daily operations.

AI: gap mapping
03

Notify & schedule

Your current partner is notified per your licence terms, on a timeline you control.

04

Take over support

Support moves to us on an agreed date, with your data and configuration untouched.

AI: in-app help agent
0
Re-implementation required, your configuration, customisations, and data are untouched by a transfer
Days, not months
Typical time from signed transfer to us holding first-line support
Same licence
CSP and licence simply move to a new partner of record, nothing is repurchased
Common questions

What teams usually ask before switching partners.

Q.Will switching partners disrupt our day-to-day operations?

Not if done properly. The transfer is a licence and support handover, your system keeps running exactly as it is throughout.

Q.Does our current partner have to agree to the switch?

No. A CSP or licence transfer does not require your outgoing partner's cooperation, though a clean handover is easier when they do.

Q.What if our documentation from the old partner is thin or missing?

Common, and part of why Assess exists. We rebuild a working picture of your configuration directly from the live system if needed.

Q.Can we switch mid-contract with our current partner?

Usually yes, though licence and support agreements vary. We will help you understand your specific contract before you commit to anything.

Q.How quickly can support actually move to you?

Typically within a couple of weeks of a signed transfer, faster if access and documentation are readily available.

Thinking about switching

Get an honest second opinion first.

Tell us what is not working with your current partner. We will tell you plainly whether a switch will actually fix it.

Book a 30-minute call

With someone who has taken over support from another partner before.

→

Run the situation diagnostic

Four minutes, no email required to see the result.

→