Switch Your Dynamics 365 Partner: 7 Signs and a Safe Plan (2026)

Last updated: October 15, 2026

By ZapAI Team

TL;DR: If slow tickets, surprise invoices, and untested release waves keep coming back after you’ve raised them, it’s time to look for a new Dynamics 365 partner. Licenses bought through CSP can move to a new partner mid-term without re-buying, but the old partner has to approve the transfer. Plan for 6 to 12 weeks, collect your code and documentation first, remove the old firm’s admin access last, and don’t cut over during a release wave.

Nobody wakes up excited to switch Dynamics 365 partners. It’s a hassle. You already paid one firm to learn your business, and starting over sounds like paying twice.

But sometimes the relationship quietly stops working. Tickets sit. Invoices show hours nobody approved. Or the one consultant who understood your plug-ins moves on, and every fix now starts with a stranger reading your code cold. So how do you know it’s time, and how do you leave without breaking anything?

Bias disclosed. We’re a Dynamics 365 partner, so we benefit when people switch. We’ll still tell you when fixing the current relationship is the smarter call, because sometimes it is.

What Are the Signs It’s Time to Switch Your Dynamics 365 Partner?

Patterns, not bad weeks. Seven signals matter most, and two or more that persist after you’ve raised them in writing usually mean the relationship is the problem, not the software.

• Tickets that sit. A production issue waiting days for a first reply isn’t a support model. It’s a queue.
• Nobody tested the last release wave before it reached production. If your partner met Microsoft’s changes the same morning your users did, that’s a gap.
• Knowledge locked in one head. Ask who else at the firm could fix your custom pricing plug-in tomorrow. Silence is an answer.
• Surprise invoices. Change orders after the work is done. A retainer that overflows every month.
• No roadmap. Has anyone walked you through which Copilot use cases in Dynamics 365 fit your process, or what’s landing next wave? Pure break-fix means you’re paying for a plumber, not an advisor.
• Documentation that doesn’t exist. No customization inventory, no integration map, no record of who built which flow. Sound customization practices assume somebody wrote things down.
• Scope drift. Custom code when a standard feature would do, or a new module when the real pain is a process nobody mapped.

Should You Fix the Relationship Before You Switch?

Usually it’s worth one honest attempt. Put the problems in writing, ask for a named backup consultant and a response-time commitment, and give it 60 to 90 days.

Some problems belong to you, not the partner. No internal owner, approvals that stall for weeks, requirements that change every sprint. A new firm inherits that same mess on day one, and it’ll bill you to rediscover it. Hold our list of Dynamics 365 implementation mistakes up as a mirror first.

Switch when the firm agreed to the fixes in writing and still didn’t deliver, when the people who actually built your system have left and nobody remaining understands it, or when you no longer trust the invoices. That last one rarely recovers.

What Changes Technically When You Change Dynamics 365 Partners?

Three separate things move. They aren’t wired together. Your CSP billing owner, the partner’s admin access to your tenant through GDAP, and Microsoft’s partner attribution records such as Partner of Record and Partner Admin Link.

Licenses. If you buy through the Cloud Solution Provider program, your partner is the billing owner. Microsoft’s partner-to-partner transfer process moves subscriptions to a new CSP partner without re-buying them. The new partner starts the request, and the current partner has to approve it. You can’t start it yourself. Microsoft won’t override a refusal or mediate disputes, and a request nobody acts on expires after 30 days. Before any of that, you sign a Microsoft Customer Agreement with the new partner and accept its relationship request.

The fine print is friendlier than people expect. According to Microsoft’s new commerce transfer guide, a transfer creates a new subscription with a new ID at the original price, keeps user counts and renewal settings, and doesn’t open a fresh cancellation window. Most finish in under an hour. Some take up to 72 hours.Each transfer caps at 25 license-based line items per billing plan. One catch. Microsoft’s transfer page says Business Central items can’t move through this tool, so Business Central customers should get both partners to explain, in writing, how licenses will be handled and when.

Admin access. Partners administer your tenant through granular delegated admin privileges, or GDAP. You can remove a partner’s GDAP roles yourself on the Partner relationships page in the Microsoft 365 admin center, which cuts off admin access for its mapped security group. That covers GDAP and nothing else. Microsoft’s Business Central partner-switch steps also have you disable the partner’s user accounts, remove its multitenant apps, and clear the notification recipients, authorized Microsoft Entra apps, and Application Insights settings it configured. Apply that thinking to every Dynamics 365 app, including guest accounts, app registrations, Dataverse application users, and integration service accounts. The reseller relationship is the odd one out. You can’t delete it yourself, and the partner can only remove it once no subscriptions are active.

Partner of record. This is Microsoft’s credit ledger, and it grants no access to anything. For Dynamics 365, partners file Claiming Partner of Record associations in Partner Center, Microsoft emails your contact, and you can decline at any time. Partner Admin Link works differently. A PAL ties a partner ID to the partner’s own user accounts or service principals in your tenant, and Microsoft documents it for Azure plan subscriptions. Only that partner can edit it. What you control is the access underneath, so disable those accounts and the link has nothing left to ride on.

Three systems. Three different owners. It rarely comes up in the sales call.

What Should Be on Your Partner Transition Checklist?

Everything the new partner needs to support you without phoning the old one. Collect it while things are still cordial. Confirm in writing that you own the code.

• Credentials and ownership. Admin and service accounts, API keys, and the Azure DevOps or GitHub organization with your code. If any of it lives in the partner’s tenant, move it first.
• Solutions, source code, and ALM pipelines. Unmanaged exports from dev, source for every plug-in and PCF control, and the pipelines that deploy them. A managed solution with no source is a sealed box.
• Design documents, the security role matrix, and a data model diagram, even rough ones.
• Integrations. Every connection in and out, whether it runs on Azure Logic Apps, Power Automate, or a third-party connector, plus the account it runs as.
• Environments. Which ones exist, and who can copy or reset them?
• Support history. Export 12 months of tickets. Recurring issues show the new team where the bodies are buried.
• Open tickets and in-flight work, with status and what’s already been billed.
• Knowledge transfer, two to four recorded walkthroughs with the outgoing consultants, written into the exit terms.
• ISV add-ons, their renewal dates, and which partner each vendor thinks you’re with.

What Do Dynamics 365 Managed Services Usually Include?

A support partner typically handles tickets against response targets, user and security administration, small enhancements, and regression testing before each Microsoft update. Pricing ranges from prepaid blocks of hours to fixed monthly retainers.

That testing piece? It’s where weak contracts fall apart. Microsoft delivers two major releases a year, in April and October, for Power Platform and customer engagement apps like Sales and Customer Service. Microsoft recommends validating in a sandbox copied from production, and says plainly it doesn’t provide that sandbox free. Finance and operations apps keep their own clock. Microsoft ships four service updates a year, in February, April, July, and October, customers must take at least two of them per year, and only one consecutive update can be paused. Business Central gets major updates every April and October, with minor ones monthly in between.

Translation? Somebody has to run your critical processes against every update, in a sandbox, before users see it. Ask a prospective partner how they handled this October’s wave. Watch their face.

Each pricing model fails its own way. Prepaid hours expire unused. Retainers can hide thin coverage. Time-and-materials quietly rewards slow work. A small retainer for admin and release testing plus hourly enhancements suits plenty of mid-sized teams. For where support sits in the overall budget, see our Dynamics 365 cost breakdown.

How Do You Evaluate a New Dynamics 365 Support Partner?

Ask how they’d take over, not how they’d implement. Verify their Microsoft listing yourself, talk to a client they inherited from another firm, and get the first 90 days in writing.

• Who exactly will work on our account, and who covers when that person is out?
• Walk us through how you tested client environments for the most recent release wave.
• What’s your response target for a production-down issue, and what happens after hours?
• Can we see a sample handover plan and a sample monthly support report?
• Who owns the code and documentation you produce? The only good answer is you.
• Will you take over our existing CSP subscriptions, and what changes on our invoice?
• Can we talk to a client you took over mid-contract?

Partner claims are easy to check. Microsoft’s Find a partner directory lets you search firms and filter by Solutions Partner designation. Solutions Partner for Business Applications is Microsoft’s designation for Dynamics 365 and Power Platform, scored on certified staff, customer growth, usage growth, and deployments. If a firm says it holds one, it should show up there. Useful signal. It still says nothing about the specific people who’ll answer your tickets.

How Long Does a Dynamics 365 Partner Transition Take?

Six to twelve weeks for most single-app environments, in our planning experience. Finance and operations environments with heavy integrations, several ISV add-ons, or an outgoing partner who approves the CSP transfer on day 29 instead of day 2 will run noticeably longer.

Timing matters too. Don’t cut over in the weeks around an April or October release, a finance and operations service update, or year-end close. And remove the old firm’s access last, after the new one has closed real tickets, not first in a fit of frustration.

Wrapping Up

Switching partners is a business decision with a technical tail. Try fixing the relationship once, in writing. If the problems return, collect your code and documentation, let the new partner request the CSP transfer, record the knowledge transfer, and only then strip the old firm’s remaining access. Expect 6 to 12 weeks.

ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric, and AI consulting firm based in Irving, Texas. We help US companies that already run Dynamics 365 plan partner transitions and set up ongoing support with clear ownership of code and documentation. If you’re weighing a move, request a partner transition review and we’ll look at your environment, exit terms, and license setup, then tell you whether to fix, switch, or wait for renewal. Teams in North Texas can also see how we work as a Dallas Dynamics 365 partner.

Questions Teams Ask Before Changing Partners

Can we switch Dynamics 365 partners in the middle of a license term?

Do we lose our data or customizations when we change partners?

What if the old partner won’t approve the CSP transfer?

Partner of Record vs CSP partner, are they the same thing?

Realistically, how fast can a partner switch happen?

Should the new partner be a Microsoft Solutions Partner?