How to Switch Business Central Partners (Without Disrupting Your Business)
Many companies assume they are stuck with the partner that implemented Microsoft Dynamics 365 Business Central. You are not. Your licenses, your data, and your system belong to you, and changing partners is a routine process that Microsoft supports. Done carefully, your users will barely notice the change, except that support tickets start getting answered.
This guide covers when it makes sense to switch, how the transfer works, what to prepare, and how long it usually takes.
Signs It’s Time to Switch Partners
Every partner relationship has rough patches. These are the signs that the problem is structural rather than temporary:
- Slow or no response to support requests. Tickets sit for days, or you only hear back when you escalate.
- Turnover on your account. Every call is with someone new who doesn’t know your setup.
- Problems that never get fixed. Inventory costing, posting groups, or reports have been “almost right” since go-live.
- Customizations nobody can explain. You have code in your system, but no documentation and no one who will own it.
- Upgrades keep slipping. Business Central updates twice a year. If your partner is behind on keeping your extensions compatible, you are carrying risk.
- Invoices you don’t understand. Hours are billed without clear detail about what was done.
- They don’t know your industry. Distribution, manufacturing, retail, and EDI-heavy businesses need a partner who has seen those processes before.
If two or three of these sound familiar, it is worth talking to another partner.
How a Business Central Partner Transfer Works
1. Licensing and the CSP Transfer
Most Business Central online customers buy licenses through Microsoft’s Cloud Solution Provider (CSP) program. Changing your partner of record is done in the Microsoft 365 admin center: the new partner sends a reseller relationship request, a global admin at your company accepts it, and your subscriptions move to the new partner at renewal or through a transfer. Your users, data, and environments stay exactly where they are. Nothing is reinstalled.
If you run Business Central on-premises, the new partner is assigned to your license and service plan through Microsoft, and your license file stays the same.
2. Admin Access
Your new partner needs delegated admin access (GDAP) to your tenant to manage environments, apply updates, and open tickets with Microsoft. You approve this in the admin center and choose which roles they get. At the same time, you should review and remove access for the previous partner once the handoff is complete. You stay in control of who can get into your system.
3. Documentation
Ask your current partner for whatever documentation exists: design documents, setup notes, integration details, and a list of open issues. Many partners provide this willingly. If documentation is thin, a new partner can rebuild it by reviewing your configuration directly.
4. Extensions and Customizations
This is the area that needs the most care:
- AppSource apps (for example, Avalara, Continia, or SPS Commerce) are licensed to your tenant, so they continue working. Your new partner may need to be registered with the publisher to support them.
- Per-tenant extensions (custom code built for you) should come with their source code. Your agreement usually gives you rights to it. Request the source repository, not just the compiled app file.
- Integrations such as EDI, e-commerce, payment processing, and banking should be inventoried, with credentials and endpoints documented.
A good new partner will review the code and flag anything fragile before your next major update.
What to Prepare Before You Switch
- A list of your Business Central environments (production, sandbox) and your admin contacts
- Your current license count and renewal date
- A list of installed apps and extensions
- Copies of your contract and statement of work with the current partner
- A short list of your top open issues and pain points
- Contact information for any ISVs or integration vendors
You don’t need everything to be perfect before starting. The new partner can help fill in gaps.
A Typical Timeline
For most small and mid-sized companies, a partner switch takes two to six weeks:
- Week 1: Introductory call, review of your pain points, and agreement on scope
- Weeks 1 to 2: Partner-of-record request, admin access approval, documentation and source code requested
- Weeks 2 to 4: System review of setup, extensions, integrations, and open issues
- Weeks 4 to 6: Support takes over fully, and a prioritized plan addresses the biggest problems
Day-to-day work in Business Central continues normally throughout. There is no downtime involved in changing partners.
The Secondary Partner Option
Not every company wants to cut ties completely. Some keep their existing partner for licensing or a specific area and bring in a second partner for help where they are struggling, such as inventory, accounting setup, EDI, or development. Business Central supports more than one partner with delegated access, each with only the roles you approve.
This can be a low-risk way to see how a new partner works before making a full move.
How DPFE Can Help
DPFE Corp has worked with business software since 1980 and is a Microsoft Dynamics 365 Business Central partner based in Southern California. We regularly take over Business Central customers from other partners, and we also work alongside existing partners as a secondary partner. Our partner network includes Avalara, Continia, Insight Works, Lanham, LS Retail, SPS Commerce, and Versapay/ChargeLogic, so the apps you already rely on are covered.
Learn more on our Switch Your Business Central Partner page, or contact us to set up a short introductory call.