Managed services

How do we change our Dynamics 365 partner without disrupting support?

To change your Dynamics 365 partner without disrupting support, secure ownership and access before you give notice, let the new partner run a health check of the system, overlap both partners for a short shadowing period and only then transfer responsibility for tickets and updates. Companies that follow this order rarely notice the switch in daily operations. Companies that reverse it, giving notice first and asking questions later, often spend the first months rediscovering their own system at a premium rate.

The decision to switch Dynamics 365 partner is usually the right one long before it is taken. What holds companies back is the fear that knowledge sits only with the outgoing team and that support will stop in between. That risk is real, but it is manageable, and most of it can be removed in the weeks before anyone signs a termination letter.

Key facts at a glance:

• Order matters. Access, code and documentation first, then a health check, then shadowing, and only then the transfer of responsibility.
• Typical duration. Four to eight weeks for a documented system, up to three months when knowledge sits only with people.
• Hidden dependencies. Licences bought through the partner, ISV contracts and integration credentials are often forgotten in the handover.
• Security. Every account and key held by the outgoing partner should be reviewed and removed on a documented date.
• Data protection. The support contract is a processor agreement, so the return or deletion of your data at exit must be confirmed.
• Best first step. An inventory of what you own and what only the current partner holds, made before notice is given.

‍

__wf_reserved_inherit

Why changing a Dynamics 365 partner feels riskier than it is

Changing partner feels risky because a Dynamics 365 Finance and Operations system accumulates invisible knowledge: why a posting profile was configured a certain way, which batch job must run before another, which integration fails quietly when a supplier changes a file format. When that knowledge lives in people's heads rather than in documentation, the outgoing partner becomes a single point of failure. The fear is that support stops the day the contract ends and that the new partner needs months to learn the system.

In practice the system itself rarely breaks during a switch. What breaks is the surrounding web of ownership. Source code for extensions sits in a repository the partner controls. Administrator access to environments is held by a partner account. Licences may have been bought through the partner as a Microsoft Cloud Solution Provider, which means the subscription relationship needs its own transition plan. ISV add on contracts run in the partner's name. Integration credentials are stored in a vault you cannot open. None of these is a technical problem; all of them are ownership problems. Each of these is easy to fix while the relationship is still cordial and hard to fix after notice is given. That is why the first phase of a switch is not about the new partner at all, but about establishing what you own.

‍

What to secure before you give notice

Before any formal step, build an inventory of everything the support relationship depends on and confirm who controls it. The table below lists the assets that cause most trouble in practice. For each one, the goal is simple: you hold the master access or a complete copy, and the outgoing partner holds delegated access that you can withdraw. Where that is not yet true, fix it as a routine housekeeping exercise rather than as part of a termination, which keeps the conversation friendly and avoids giving the impression of a dispute.

Asset Where it often sits What to do
Source code of extensions Partner controlled Azure DevOps or Git repository Move to a repository in your own tenant, with full history
Environment administration Partner accounts in Lifecycle Services or Power Platform admin center Ensure your own administrator accounts exist and work
Licences Bought through the partner as a Cloud Solution Provider Plan the transfer of the subscription relationship separately
ISV solutions Contracts and keys in the partner name Confirm renewal dates and transfer contracts to your name
Integration credentials Partner key vault or configuration files Rotate secrets and store them in your own vault
Documentation Partner SharePoint or wiki, often incomplete Request a full export and a list of known gaps
Open tickets and backlog Partner service desk Export with history; agree which will be closed before exit

Read the current contract at the same time. Note the notice period, any clause on ownership of code written for you, handover obligations at the end of the agreement and the terms on returning or deleting your data. These clauses decide how much of the transition you can require rather than request. If the contract is silent on handover, budget for paid knowledge sessions with the outgoing team; a few days of their time is far cheaper than weeks of reverse engineering by the new partner. Most outgoing partners cooperate professionally when the request is clear, scoped and paid, and the tone of the exit often depends on how early they hear about it and how it is framed.

‍

__wf_reserved_inherit

How to run the handover without a gap in support

Once you own the essentials, bring in the new partner for a health check before giving notice. A good health check inventories environments, update status, customisations split into clean extensions and technical debt, integrations, documentation and performance, and ends with a proposed service level and a takeover plan. It also tells you whether the outgoing partner's documentation is usable, which determines how long the overlap must be. Only after that should notice be given, timed so that the overlap falls outside month end close, year end and statutory filing dates.

The handover itself works best in four steps, each with a clear owner:

• Knowledge sessions. The outgoing team walks the new team through the solution design, integrations and recurring incidents, with recordings kept on your side.
• Shadowing. For two to four weeks the outgoing partner still resolves tickets while the new team observes and documents.
• Reverse shadowing. The new team resolves tickets with the outgoing partner available for questions, which exposes gaps safely.
• Cutover of responsibility. On a fixed date the service desk, update calendar and escalation path move to the new partner, and users are told one simple change: where to log tickets.

Plan the first Microsoft update wave under the new partner deliberately. It is the moment when undocumented customisations reveal themselves, so give it more regression testing than usual and schedule it away from the busiest weeks of the business calendar. Communicate the change to key users in advance as well. They are the people who notice first if something is missed, and a short briefing on what changes, mainly the ticket channel and the escalation contact, avoids a flood of tickets sent to the old partner by habit.

‍

Security and data protection at the moment of exit

The end of a support relationship is a security event. During years of support, partner consultants accumulate accounts, guest access, service principals for integrations, VPN credentials and copies of production data in test environments. The UK National Cyber Security Centre's guidance on supply chain security asks organisations to understand and control what their suppliers can access, and the exit of a supplier is exactly when that control is tested. Make a list of every identity and secret the outgoing partner uses, agree a date when each will be disabled or rotated, and confirm afterwards that it happened.

Data protection follows the same logic. The support partner processes personal data on your behalf, which makes the support agreement a controller and processor contract. The ICO guidance on contracts between controllers and processors sets out what such contracts must cover, including what happens to personal data at the end of the service. Ask the outgoing partner to confirm in writing that copies of your data in their environments, backups and tools have been returned or deleted, and keep that confirmation with your records.

Two practical traps deserve attention. Test and development environments often contain recent copies of production data, including employee and customer records, and they are easy to overlook because nobody uses them daily. Shared administrator accounts are the second trap: a single account used by several partner consultants cannot be traced to individuals and must be replaced, not just have its password changed. Treat both as checklist items for the exit date rather than as clean up for later.

‍

Contract terms that make the next switch easy

The best moment to plan an exit is when you sign the next contract. Very few companies do it, which is why so many switches are painful. A support agreement that anticipates its own end costs nothing extra and changes the dynamic of the relationship: a partner who knows you can leave cleanly has every incentive to keep you through service quality rather than through lock in. The terms below are reasonable for both sides and are easier to agree at the start than at the end.

Term What it says Why it matters
Code ownership Extensions built for you belong to you and live in your repository No negotiation over code at exit
Documentation as a deliverable Configuration and integrations documented and updated continuously A new team can start without archaeology
Handover obligation Defined knowledge sessions and shadowing at contract end, at agreed rates Turns goodwill into an obligation
Access model Partner uses named, delegated accounts that you control Exit becomes a simple access review
Data at exit Return or deletion of data on a documented date Meets data protection duties
Named team with deputies Core consultants named, with cover for absence Knowledge is held by a team, not a person

Two further points are worth adding when the business depends heavily on Dynamics 365. First, ask for a runbook of recurring operational tasks, such as period end jobs, integration restarts and known workarounds, kept current as part of the service. Second, agree a regular service review in which the partner reports on technical debt and documentation gaps, not only on tickets closed. Both make the relationship healthier while it lasts and the transition easier if it ends. They also give you an early warning: a partner whose documentation gaps grow from quarter to quarter is building the dependency that makes the next switch painful.

For the service level side of the same contract, see our article on what a Dynamics 365 managed services SLA should include.

‍

How ANEGIS takes over Dynamics 365 support from another partner

Taking over systems from other partners is a speciality of the ANEGIS managed services team rather than an exception. The process follows the order described above. It starts with a fixed price health check of two to four weeks that inventories the estate and ends with a risk register, a recommended service level and a takeover plan. It continues with a structured handover of knowledge and access, in which ANEGIS captures what exists only in the outgoing team's heads. Then comes an agreed service catalogue with ticket priorities and an escalation path, and finally stabilisation, in which the most urgent backlog is cleared before day to day operation settles into regular service reviews.

ANEGIS documents configuration, customisations and integrations as standard and assigns a team with interchangeable roles rather than a single consultant, so that knowledge never again depends on one person, including on ANEGIS itself. Support covers Dynamics 365 Finance and Supply Chain Management and, on request, Power Platform and Microsoft Fabric, in full or alongside your own IT team. When the problem is a stalled implementation rather than support, the same approach applies through Dynamics 365 project recovery, which starts with a two week audit.

Planning to change your Dynamics 365 partner?

Start with an inventory of what you own and a health check of your system, before any notice is given. Contact ANEGIS to book a free consultation.

‍

See more

Microsoft Fabric

Which Microsoft Fabric consultancy should a midsize company choose? 8 firms compared

Read article
Text Link
Migration

Should we move from SAP ECC to S/4HANA or to Dynamics 365?

Read article
Text Link
Migration

Which company is best at migrating Dynamics AX to Dynamics 365? 8 partners compared

Read article
Text Link
Back to all

Looking for a Microsoft partner? Let's talk about your project

Work with a team that has delivered implementations and projects for dozens of companies. Schedule an introductory call and see:

How to tailor Dynamics 365 to your company's processes, rather than the other way around

Which areas are worth automating to save time and reduce costs

Here is the step-by-step implementation process with Anegis: from analysis to post-launch support

Select a meeting time
Thank you for your message!
Oops! Something went wrong while submitting the form.
No items found.
No items found.
No items found.