Support planning guide

How to change your Dynamics 365 support partner

Short answer

A Dynamics 365 support transfer starts with access, source code, open incidents and clear ownership. MS Dynamics Guys recommends reviewing these before the outgoing provider leaves. Agree the technical support scope, the Microsoft escalation route and the handover acceptance checks separately from any licensing changes.

A support transfer is a responsibility change

Changing who fixes custom code does not automatically move licenses, subscriptions or Microsoft support entitlements. Business Central online customers should confirm the role of their reselling partner. Teams supporting Sales or Customer Service should confirm their authorized support route and tenant access. Record the responsibilities before changing production access.

The support handover checklist

MS Dynamics Guys planning checklist for a support transfer
ItemEvidence to collectAcceptance check
Environment inventoryApp, deployment type, version and environment purposeProduction and test environments are identified
Custom componentsSolutions, extensions, plug-ins and flowsEach component has a purpose and responsible owner
Source and buildsRepository, build instructions and release packagesAuthorized maintainers can reproduce a build
IntegrationsEndpoints, authentication owners, mappings and schedulesFailed transfers can be detected and reconciled
Operational accountsService accounts, app registrations and permissionsAccess is approved and controlled by the customer
Open incidentsBusiness impact, history, workaround and statusIncoming and outgoing teams agree unresolved work
MonitoringAlerts, job history and escalation contactsA test alert reaches the responsible team
RecoveryRecovery procedures and dependency listA safe rehearsal confirms the agreed procedure
Licensing and escalationReseller and Microsoft support responsibilitiesThe authorized case-submission route is confirmed
Knowledge transferRunbook and recorded or written handoverThe incoming team can explain a representative incident
Commercial boundariesCoverage, fees, notice and extra-work processThe agreement names the support start date and scope

Download the support-transfer checklist (CSV). The working file includes blank Owner and Status columns for your team. This is a planning template, not a Microsoft certification or client case.

A practical transfer sequence

  1. Review the current agreement and the notice period with the responsible owner.
  2. Inventory the environment and collect the missing technical evidence.
  3. Separate urgent stabilization from the ongoing support scope.
  4. Agree a period when the outgoing provider can answer questions.
  5. Test access, incident routing, monitoring and a representative release process.
  6. Accept the handover, start the new support process and remove unneeded access through the customer's administrator.

Timing depends on system complexity, access, documentation and the outgoing provider's availability. Do not treat a generic number of weeks as a safe commitment for every system.

If source code or documentation is missing

Record the gap before accepting responsibility for a customization. An installed package may not provide maintainable source. Confirm ownership and the permitted route to obtain it. If recovery or replacement is needed, estimate that work separately and explain its effect on the support start date.

Keep the business running during the change

Keep an agreed incident owner throughout the transfer. Avoid changing access, integrations and release processes at the same time without a tested plan. The business owner should approve the cutover and know which team to contact for every severity level.

A documented support takeover at Bluefin

At Bluefin Insurance, a Customer Service consultant and a CRM/Dataverse developer joined the client’s live support team. Its Jira service board records critical incidents falling from 14 to 2 per month in May–June 2024; the client retained release authority.

Your next step

Review a support transfer with MS Dynamics Guys

MS Dynamics Guys can review an inherited Dynamics 365 CRM or Business Central environment, identify handover gaps and define the technical support scope. Use the checklist to show what you already have and what needs to be recovered.

Product documentation referenced on this page