How to Choose a Business Central Implementation Partner
The software is the same with every partner. The delivery team, the written scope and the support model are what you are actually choosing.

On this page
- Before you compare Business Central implementation partners
- 12 questions to ask a Business Central implementation partner
- 1. Who will actually deliver the project?
- 2. What Business Central work have you done that resembles ours?
- 3. How do you run discovery and fit-gap analysis?
- 4. What exactly will be in the written scope?
- 5. How do you decide between standard features, a Marketplace app and custom AL?
- 6. What data will migrate, and how will you prove it is correct?
- 7. How will integrations be run when something fails?
- 8. What is the testing and cutover plan?
- 9. How will users be trained?
- 10. How are changes priced and approved?
- 11. Who owns support after go-live?
- 12. Which partner credentials do you hold, and what do they prove?
- What Microsoft partner credentials prove, and what they do not
- A 100-point Business Central partner scorecard
- Remote delivery and onsite time
- Red flags when comparing Business Central partners
- How Bitta Apps runs a Business Central implementation
To choose a Business Central implementation partner, compare four things: who will actually deliver the work, how the partner discovers and controls scope in writing, how it handles data migration, integrations and custom AL, and who owns support after go-live. The software is the same with every partner. The delivery team, the statement of work and the support model are not.
This guide is for finance leaders, operations owners and IT managers comparing Business Central implementation partners before they sign a statement of work. It covers 12 questions to ask every finalist, what a good answer looks like for each, a 100-point scorecard, what Microsoft partner credentials actually prove, and the red flags worth walking away from. Microsoft facts were checked on Microsoft Learn on 2026-11-04.
Choosing a partner now? Book a free discovery call to agree practical next steps, or use the short form on the Business Central partner page. Replacing a current partner? Start with the free BC Environment Snapshot: one hour with a senior Business Central consultant on a screen share, then a written summary of your environment within five business days. Prefer to talk now: (626) 766-9732.
Before you compare Business Central implementation partners
Start with your business, not a feature list. Write down the three to five outcomes that justify the project, such as a faster month-end close, several legal entities, or retiring an unsupported legacy ERP. If you run Dynamics GP, plan the move against the Dynamics GP end of support timeline. If you are still deciding whether to move at all, read when to switch from QuickBooks to Business Central or the ERP cost and scale comparison first.
Then document the boundaries that change scope and price: entities, locations and currencies; finance, distribution, manufacturing or project requirements; systems that must integrate; the data history you want to migrate; audit requirements; and the periods when the business cannot absorb a cutover. You do not need a finished requirements document. You need enough clarity to see which partner asks informed questions and which one agrees with everything.
Microsoft's Dynamics 365 implementation guide organizes a project into five Success by Design stages: Strategize, Initiate, Implement, Prepare and Operate. Ask each partner how its method covers all five, not only configuration and licensing.
12 questions to ask a Business Central implementation partner
Ask every finalist the same questions, in writing where possible, so the answers can be compared side by side.
1. Who will actually deliver the project?
Ask for the names and roles of the people who will run discovery, configure Business Central, build AL extensions, migrate data, test, manage the plan and support go-live. Then ask which of them were in the sales conversation and which will still be assigned after the contract is signed. Company size is not the same as team continuity.
Good answer looks like: named people for engagement lead, functional lead, developer, project manager and QA, their availability against your dates, and those names written into the statement of work.
2. What Business Central work have you done that resembles ours?
"We implement ERP" is too broad. Ask about projects with similar operational complexity: multi-company finance, distribution, manufacturing, EDI, e-commerce, project accounting, moving NAV customizations to Business Central online, or a QuickBooks migration. Ask for a reference you can call. Where a client cannot be named, the partner should still describe the problem, scope and outcome without inventing a result.
Good answer looks like: two or three comparable projects described in specifics, and a reference call offered without being chased.
3. How do you run discovery and fit-gap analysis?
A partner should explain how it maps current processes, identifies controls, separates true requirements from preferences, and decides what stays standard. Ask what you receive at the end of discovery. Be cautious when a partner offers a fixed implementation price after one short sales call. A price can be fixed only when the assumptions behind it are written down.
Good answer looks like: a defined discovery deliverable, such as a process map, fit-gap register, integration inventory, data migration plan, risk log and written scope.
4. What exactly will be in the written scope?
The proposal should name deliverables, milestones, responsibilities, assumptions, exclusions, acceptance criteria and the change-control process, including who owns data cleansing, testing and sign-off. Ask for a redacted statement of work. "Configure finance" is vague. A list of companies, posting groups, dimensions, approval flows, reports and migration objects is useful.
Good answer looks like: a sample statement of work where you could point to any line and say who does it, when, and how it is accepted.
5. How do you decide between standard features, a Marketplace app and custom AL?
Business Central can be extended with configuration, workflows, apps from Microsoft Marketplace (formerly AppSource) and per-tenant AL extensions. Use standard functionality when it fits. Use a proven app when it solves a common need and its support and update record are acceptable. Use custom AL when the requirement differentiates the business or cannot be met another way.
Upkeep is the hidden cost. Business Central online receives two major updates a year, in April and October, according to Microsoft's update cycle documentation. Microsoft's guidance on maintaining Marketplace apps and per-tenant extensions makes the partner responsible for keeping that code compatible, and extensions that block a major update might be uninstalled during the enforced update period. The article on Business Central customization and technical debt shows how that cost builds up.
Good answer looks like: a standard-first rule, source control and automated tests for custom code, and a named process for testing extensions against each release wave preview.
6. What data will migrate, and how will you prove it is correct?
Ask for an object-level migration plan: master records, open transactions, opening balances, dimensions, inventory quantities and costs, attachments and history. Each object needs a source, transformation rules, an owner, a rehearsal count, a validation method and a reconciliation sign-off. Not every year of history belongs in the new ERP. A validated opening position plus a read-only archive is often safer and costs less to run.
Good answer looks like: at least one full trial load, reconciled by your finance owner against the trial balance, aging and inventory valuation before cutover.
7. How will integrations be run when something fails?
An integration is not finished when one test order reaches Business Central. Ask about retry behavior, duplicate prevention, error queues, monitoring, alert ownership and reconciliation. For every API, EDI flow, bank connection or storefront, someone must know how to detect a failure and recover without corrupting data. If the proposal lists only endpoints and field mappings, the operational design is missing.
Good answer looks like: for each integration, a named owner, a failure alert, a retry and duplicate rule, and a scheduled reconciliation.
8. What is the testing and cutover plan?
Ask which test cycles are included and who owns each one. A credible plan covers configuration, extensions and integrations, migrated data, full business scenarios, permissions, user acceptance testing and a cutover rehearsal. "We will migrate over the weekend" is not a plan.
Good answer looks like: a cutover runbook with tasks, owners, timings, go/no-go criteria, reconciliation steps and a rollback decision point, rehearsed before the real cutover.
9. How will users be trained?
Generic product training rarely prepares people for the processes your project configured. Ask whether training is role-based and built on your data, approvals, exceptions and month-end steps, and how late process changes found in training are triaged without destabilizing go-live.
Good answer looks like: role-based sessions for each user group, recorded for future hires, with power users trained first.
10. How are changes priced and approved?
Every ERP project discovers something new. Ask what triggers a change request, who estimates it and who can approve it. Avoid arrangements where the first sign of scope growth is a larger invoice.
Good answer looks like: a written change order that states the reason, deliverable, price, schedule impact and what happens if you decline, approved by you before any work starts.
11. Who owns support after go-live?
Microsoft's technical support overview says each Business Central customer has a partner who assists with technical support, and that the reselling partner is the frontline, triaging requests and escalating to Microsoft. Ask what hypercare includes, how long it lasts, where users submit issues, what response targets apply, and how larger improvements are separated from break/fix work. If a different team takes over at go-live, it needs a documented handoff. The Business Central support ticket checklist shows what a useful ticket contains.
Ask how the partner will access your tenant. Microsoft's delegated admin documentation recommends the Dynamics 365 Business Central Administrator role as the least-privileged role in a granular delegated admin privileges (GDAP) relationship, and lets your internal administrators restrict partner access per environment.
Good answer looks like: a defined hypercare window, response targets in writing, a named support owner, and GDAP access limited to the roles the work needs.
12. Which partner credentials do you hold, and what do they prove?
Ask the partner to separate organizational designations, specializations, individual certifications and CSP status rather than presenting them as interchangeable badges. Each answers a different question, as the next section shows, and none replaces checking the delivery team.
Good answer looks like: each credential named precisely, plus the names of the certified people who will work on your project.
What Microsoft partner credentials prove, and what they do not
Microsoft publishes the criteria behind each credential, so a partner's claim can be checked against the source.
Credential | Held by | What it shows | What it does not show |
|---|---|---|---|
Solutions Partner for Business Applications | The organization | At least 70 of 100 points, with at least one point in each of the three categories (performance, skilling, customer success) and each of their five subcategories, for Dynamics 365 and Power Platform | That the points came from Business Central work, or that your team is certified |
Small and Midsize Business Management specialization | The organization, on top of the designation | 15 new Business Central deployments with five or more monthly active users and at least 15% monthly active user growth in the trailing 12 months from a baseline of at least 50 monthly active users 12 months earlier, five people certified as Business Central Functional Consultant, and a Business Central consulting offer on Microsoft Marketplace | Fit with your industry or your scope |
Business Central certifications (exams MB-800, MB-820) | An individual | The Business Central Functional Consultant Associate (MB-800) or Developer Associate (MB-820) credential | That this person is assigned to your project |
Cloud Solution Provider (CSP) | The organization | Authorization to sell Microsoft cloud licenses, directly or as an indirect reseller through a distributor | Implementation ability |
The sources are Microsoft's Solutions Partner for Business Applications criteria, its page on applying for specializations, and the CSP program overview, which says direct-bill partners sell to, bill, manage and support their customers themselves.
The firm that sells your licenses and the firm that implements Business Central can be the same company, but they do not have to be. If they differ, write down who owns license sizing and who is the first line of support. The guide to Business Central Essentials vs Premium vs Team Members covers the license decision.
A 100-point Business Central partner scorecard
Score every finalist against the same evidence, using the answers to the 12 questions. Require written evidence for high scores. A polished demo should not outweigh a vague statement of work.
Area | Points | Questions | What earns full points |
|---|---|---|---|
Delivery team | 20 | 1 | Named people for each role, stated availability, and the same people from discovery to hypercare |
Relevant experience | 15 | 2 | Comparable operational and technical work, with a reference you can call |
Discovery and scope | 15 | 3, 4 | Written deliverables, assumptions, exclusions and acceptance criteria |
Solution quality | 15 | 5, 12 | Standard first, Marketplace apps chosen on support and update record, update-safe AL with tests |
Data and integrations | 10 | 6, 7 | Rehearsed migration with reconciliation sign-off, and integrations with monitoring and recovery |
Testing and cutover | 10 | 8, 9 | Named test owners, user acceptance testing, a cutover rehearsal, go/no-go criteria and role-based training |
Commercial clarity | 10 | 10 | A transparent pricing structure and written change control |
Support | 5 | 11 | A named post-go-live owner and response targets in writing |
Total | 100 |
Remote delivery and onsite time
Most Business Central work can be delivered remotely. Onsite time pays off when a physical process must be observed, a workshop needs fast decisions, or a cutover is operationally complex. If you are comparing Business Central partners in Southern California, proximity makes those sessions easier, but it should not outweigh delivery quality.
Red flags when comparing Business Central partners
A fixed price with no discovery, assumptions or exclusions.
A salesperson who cannot name the delivery team.
Pressure to customize before standard Business Central has been demonstrated.
Integrations described without monitoring or failure recovery.
Credentials presented vaguely, or in a way you cannot check against Microsoft's published criteria.
A request for broad administrator rights when the Business Central Administrator role would do.
No named support owner after go-live.
How Bitta Apps runs a Business Central implementation
Bitta Apps is a Microsoft Dynamics 365 Business Central partner and Microsoft Cloud Solution Provider, based in Corona, California and working remote-first across the United States. Its Business Central implementation method answers the questions above in writing:
Every implementation runs with a named engagement lead, project manager and QA, and the consultants who scope the project stay accountable for delivering it.
Discovery comes first. A written fixed-price proposal follows within five business days of discovery, with milestones and deliverables attached to the price, as set out in how Bitta Apps prices its work. If something cannot be priced fixed yet, Bitta Apps says what would make it priceable.
Scope growth arrives as a written change order that you approve or reject before any work happens.
Typical implementations take 8 to 16 weeks from discovery to go-live, followed by at least 30 days of hypercare and, if you want it, a handoff to ongoing Business Central support.
This video shows how Bitta Apps works on Business Central implementations.
Published implementation bands, assessment fees and support retainers are on the Bitta Apps pricing page.
The same 12 questions work whether you are choosing a first partner or replacing one. Send them to every finalist, score the written answers, and decide on evidence rather than on the demo.
Next step. If you are selecting a first partner, book a free discovery call to agree practical next steps, or call (626) 766-9732. If you already run Business Central and are replacing a partner, start with the free BC Environment Snapshot: one hour with a senior Business Central consultant on a screen share, then a written summary of your environment within five business days. If you prefer to start in writing, send Bitta Apps your requirements and a Business Central consultant replies within one business day.
FAQ
Frequently asked questions
How do I choose a Business Central implementation partner?
Compare finalists on four things: the named people who will deliver the work, how they run discovery and write scope, how they handle data migration, integrations and custom AL, and who owns support after go-live. Ask every finalist the same questions in writing and score the answers against the same criteria. Ask for a sample statement of work and a reference you can call before you sign.
How much does a Business Central implementation cost?
The cost of a Business Central implementation depends on five drivers: the number of user roles, the source system, how much history migrates, the integrations, and how much is customized rather than configured. Bitta Apps publishes its implementation bands on bittaapps.com/pricing: Standard from $28,500 for a single company on standard modules, Extended from $45,000 to $90,000 with scoped AL extensions and up to two integrations, and Complex from $90,000, which adds multi-company and intercompany configuration, manufacturing and advanced warehousing workflows, and a phased go-live. The fixed price follows discovery, or a paid assessment where deeper analysis is needed. Microsoft licenses, third-party app licenses and work outside the agreed scope are quoted as separate lines.
How long does a Business Central implementation take?
Bitta Apps' typical Business Central implementations take 8 to 16 weeks from discovery to go-live. Finance-first projects with clean data land near the front of that range, while multi-entity structures and integration-heavy scopes run toward the back. Complex projects need a tailored schedule, and the go-live date should be written into the proposal.
Does a Business Central partner need to be local?
No. Most discovery, configuration, development, testing and support for Business Central online can be delivered remotely. Onsite time helps when a physical process must be observed, a workshop needs fast cross-functional decisions, or a complex cutover or hands-on training benefits from being in the room. Ask each partner what it would do onsite and what it would do remotely, and judge delivery quality before distance.
What is the difference between a CSP and an implementation partner?
A Cloud Solution Provider (CSP) is authorized by Microsoft to sell Microsoft cloud licenses such as Business Central, either directly or as an indirect reseller through a distributor. An implementation partner scopes the project, configures Business Central, migrates data, builds extensions and integrations, trains users and supports go-live. One firm can do both, but CSP status alone says nothing about implementation ability, so check each separately.
What certifications should a Business Central partner have?
For individuals, look for the Microsoft Dynamics 365 Business Central Functional Consultant Associate (exam MB-800) and Business Central Developer Associate (exam MB-820) credentials on the people assigned to your project. At the organization level, Microsoft awards the Solutions Partner for Business Applications designation to partners that score at least 70 of 100 points, with at least one point in each of the three categories (performance, skilling, customer success) and each of their five subcategories, and the Small and Midsize Business Management specialization adds Business Central deployment and certification requirements on top of it. Ask which credentials belong to the firm and which belong to the people who will do your work.
Sources
Claims in this article were checked against the following on Nov 11, 2026.
- learn.microsoft.com/en-us/partner-center/membership/solutions-partner-business
- learn.microsoft.com/en-us/partner-center/membership/specializations-apply
- learn.microsoft.com/en-us/partner-center/enroll/csp-overview
- learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/overview
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/update-rollout-timeline
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/app-maintain
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/technical-support
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/delegated-admin
- bittaapps.com/pricing
- bittaapps.com/pricing/how-it-works
- bittaapps.com/services/business-central-implementation
- bittaapps.com/business-central-partner
Work with Bitta Apps on this
- Business Central partner servicesImplementation, customization, integrations, licensing and support, with published pricing and a written fixed-scope proposal.Read more
- QuickBooks to Business Central migrationWhat moves, what is archived, the published pricing and who signs off the cutover.Read more
- Dynamics GP end of lifeMicrosoft's GP support dates, what migrates to Business Central and how to plan the move.Read more