Your Business Central partner was acquired. What to check in the first 90 days

The email usually arrives with an upbeat subject line: "Exciting news." Your Business Central or NAV partner has been bought by a larger firm, an accounting practice or a private-equity-backed group. The message promises more resources, a broader team, and no change to the service you know.

Sometimes that's true. Often the first real change shows up three to six months later, when the consultant who knows your system takes a new role, or support tickets start going to a queue instead of a person.

There's been a lot of consolidation among Microsoft Dynamics partners in the last few years. If it has happened to you, here's how to protect your system without overreacting.

Don't panic, and don't wait

An acquisition isn't a reason to leave. Plenty of clients get better service afterward: deeper benches, better coverage, more specialists. But it's the moment to check, because what you're actually relying on is rarely in writing. It's a few people who know your customizations, your integrations, and why the month-end close works the way it does.

Days 1–30: Get the facts in writing

Ask your account contact for answers in writing, not on a call:

  1. Who is my named consultant, and are they staying? Get names, not roles. Ask whether key people have retention agreements.
  2. Are my support terms, rates and response times changing? Including at renewal.
  3. Where is the documentation for my customizations and integrations? If the answer is "in Dave's head," that's your biggest risk, whatever happens with the deal.
  4. Who owns the source code for my extensions? For Business Central, confirm you have access to the AL source for any per-tenant extensions written for you. For NAV, confirm you have current object exports.
  5. Who holds the admin access? Make sure your company, not only the partner, holds administrator access to your Business Central tenant, licensing in the Microsoft 365 admin center, and any integration accounts.

Items 3–5 are good hygiene with any partner. An acquisition is just the push to finally do them.

Days 30–60: Watch the signals

The early signs show up in day-to-day service, not in announcements:

  • Response times stretch or tickets bounce between people who don't know your history.
  • New faces keep appearing and each one needs your system explained from scratch.
  • Advice starts to sound like a sales pitch: new modules, new services or a platform move nobody had raised before.
  • Your project slows down because the new owner is busy integrating its own staff and systems.
  • Billing changes quietly: new rate cards, minimum blocks, or charges for things that used to be included.

One of these is normal friction. Three or more is a pattern.

Days 60–90: Make a deliberate decision

At around 90 days, ask yourself one question: is the service the same or better than before? There are three possible answers:

  • Better. Good. Keep your documentation and access up to date anyway.
  • Same, but riskier. Key people left, or knowledge sits with one person. Ask for a documented handover and a named backup.
  • Worse. It's reasonable to look elsewhere. Switching partners is far less disruptive than most people expect, as long as you have your source code, documentation and admin access, which is why the first 30 days matter.

What a clean switch looks like

A multi-company manufacturer's NAV partner was acquired, and within six months its long-time consultant had left. Support tickets took a week. Because the controller had insisted early on getting object exports and admin credentials, the new partner did a two-week system review, documented every customization, and took over support with no downtime. The NAV to Business Central upgrade that had stalled during the acquisition restarted with a fixed scope.

A new partner should start with a review of where your system really stands, not a sales proposal. You should come away knowing what's customized, what's fragile and what's fine, whether or not you hire them for more. For the practical steps, see how to switch Business Central partners mid-project.

A word of honesty

Sometimes the problem isn't the acquisition. If your system was already poorly documented, heavily customized or short on internal ownership, a change of partner exposes that rather than causing it. The fix is the same either way: documentation, access, and a clear picture of your system.

Not sure where your system stands?

If your partner has changed hands, start with a health check: a focused senior review of your setup, customizations, integrations and support arrangements, with plain-language findings. See Cateran's support options.