How to choose the right Dynamics 365 product
By Emil Björk · Microsoft business apps consultant, Gothenburg
A practical framework for picking the right Dynamics 365 apps — by company size, industry, complexity, and starting point.
On this page (7)
Choosing a Dynamics 365 product is rarely a single decision — it's typically three: one for the ERP, one or more for the CRM side, and a decision about how much Power Platform you'll layer on top. The good news is the choices are reasonably orthogonal once you understand the segmentation. This guide walks each decision in the order most organisations actually face them, and links to the head-to-head comparison for each fork in the road.
If you're still orienting yourself in the product family, start with what is Dynamics 365 and the Dynamics 365 product family overview, then come back here.
Decision 1: which ERP tier
Microsoft splits the ERP market into two tiers, and this is the decision with the biggest cost and timeline consequences.
Business Central is the right answer for organisations with up to roughly 250–300 users, a single primary entity (or a small group of entities with limited consolidation needs), and operations that aren't heavy process manufacturing or highly regulated industries like banking. Implementations run weeks to months, and the partner ecosystem is broad. Start with what is Business Central.
Dynamics 365 Finance + Supply Chain Management is the right answer for everything above that line: multi-hundred to multi-thousand users, dozens or hundreds of legal entities, multi-country statutory complexity, or operations like food and pharma process manufacturing, multi-modal logistics, or large-scale retail. Implementations run quarters to years. Start with what is Dynamics 365 Finance and what is Dynamics 365 Supply Chain.
The full head-to-head is in Business Central vs Finance and Operations. If you're coming off a smaller system rather than choosing between the two, the migration guides for QuickBooks, NetSuite, and SAP Business One cover what actually changes.
One trap worth naming: don't overbuy. Customers regularly outgrow Business Central in five years and migrate up. That's normal — and far cheaper than starting on Finance and SCM five years before you needed it.
Decision 2: which customer-facing apps
On the CRM side, pick by the customer process you run, not by feature lists. The apps are not mutually exclusive — many companies own three or four, and they share one data platform (Dataverse), so adding a second app later is an increment, not a new implementation.
- Selling to businesses with a pipeline? Sales. If Salesforce is on the shortlist too — it usually is — read Dynamics 365 Sales vs Salesforce.
- Running case management for inbound enquiries? Customer Service.
- Dispatching technicians to customer locations? Field Service.
- Running customer-billable projects with resourced engagements? Project Operations. The line between these last two is genuinely confusing; Field Service vs Project Operations draws it.
- Running marketing campaigns and orchestrating customer journeys? Customer Insights – Journeys.
- Unifying customer data from many systems for analytics and AI? Customer Insights – Data.
- Running retail across stores, e-commerce, and call centre? Dynamics 365 Commerce — which, note, sits on the F&O side of the house, not the CRM side.
Decision 3: buy an app or build one
A recurring fork: license a full Dynamics 365 app, or build a lighter custom app on Power Apps against the same Dataverse platform. The short version — buy the app when your process matches the industry-standard shape it encodes; build when your process is genuinely unusual or only needs a fraction of the app. The long version is Power Apps vs Dynamics 365 CRM, with the broader make-or-buy reasoning in build vs buy in the Dynamics 365 ecosystem.
Related, one level down the stack: when custom development enters the picture, decide deliberately between low-code and pro-code Azure services. Azure vs Power Platform is the decision guide for that line.
Look at the integration surface
If you already run heavy Microsoft 365 (Outlook, Teams, SharePoint), Dynamics 365 is dramatically less integration work than non-Microsoft alternatives — the Outlook app, Teams embedding, and SharePoint document management come close to free. If you run mostly on Google Workspace, or your sales team lives in Salesforce while finance evaluates Business Central, the integration calculus changes and deserves honest weighting. How Dynamics 365 apps connect covers what integration between the Dynamics apps themselves looks like — it is not automatic just because the logos match.
Pick the partner before the product
The partner network is uneven by region, industry, and product. A great Business Central partner in your country with deep experience in your industry is worth far more than a marginal feature advantage from a different ERP. Weight the partner evaluation as heavily as the product evaluation — choosing a Dynamics 365 partner gives you the questions to ask.
Model the real cost
List price per user per month is the least interesting number in the decision. Licence tiering, attach pricing (your second Dynamics app is cheaper than your first), storage, environments, ISV add-ons, and implementation services dominate the ten-year picture. Dynamics 365 edition comparison covers the licensing shape; TCO modelling covers how to build the honest spreadsheet.
A worked shortcut
Three profiles cover a surprising share of real decisions:
A 50-person distributor or services firm — Business Central, probably with the built-in CRM-lite capabilities first, adding Sales only when a real pipeline process demands it.
A 500-person manufacturer selling through a direct sales force — Finance + Supply Chain for the ERP, Sales for the pipeline, Field Service if you service what you sell, and Customer Insights – Journeys once marketing outgrows mail merges.
A 5,000-person retailer — Finance + Supply Chain + Commerce as one platform decision, Customer Insights – Data and Journeys for the customer side, and a serious integration architecture conversation before signing anything.
None of these are prescriptions — they're starting hypotheses to test against your own complexity. And whatever you choose, decide the rollout shape deliberately: phased vs big-bang go-live is the last decision this guide leaves you with.
Frequently asked questions
When is Business Central enough, and when do I need Finance and Supply Chain?
- Business Central suits up to roughly 250–300 users, a single primary entity or small group, and operations that are not heavy process manufacturing or highly regulated. Above that — hundreds of legal entities, multi-country statutory complexity, process manufacturing, large-scale retail — Finance and Supply Chain Management is the tier built for it.
Which CRM app do I need?
- Pick by the customer process: Sales for a B2B pipeline, Customer Service for inbound case management, Field Service for dispatching technicians, Project Operations for billable resourced engagements, Customer Insights – Journeys for marketing, Customer Insights – Data for unifying customer data, and Commerce for retail. They share Dataverse, so adding a second app later is an increment.
Should I buy a Dynamics 365 app or build a Power App?
- Buy when your process matches the industry-standard shape the app encodes; build on Power Apps against the same Dataverse when your process is genuinely unusual or needs only a fraction of the app.
Is overbuying the enterprise tier a safe hedge?
- No. Customers regularly outgrow Business Central in five years and migrate up, and that is far cheaper than starting on Finance and Supply Chain five years before it was needed.
How important is the implementation partner?
- As important as the product. A strong local partner with depth in your industry is worth more than a marginal feature advantage, so weight the partner evaluation as heavily as the product evaluation.
Further reading
Related guides
- Architecture decision records for Dynamics 365How ADRs capture the architectural choices in a Dynamics 365 program — what they are, what to record, and the long-term value they provide.
- Build vs buy in the Dynamics 365 ecosystemWhen to customise Dynamics 365 with AL / X++ / Power Platform vs buy an AppSource solution — the trade-offs, the framework, the practical guidance.
- FastTrack for Dynamics 365Microsoft's FastTrack program for Dynamics 365 — eligibility, what's offered, key engagements, and how to make the most of it.
- Phased vs big-bang go-liveWhen to phase a Dynamics 365 go-live and when to go big-bang — the trade-offs across complexity, risk, integration burden, and organisational change.
- The Success by Design methodologyMicrosoft's current Dynamics 365 implementation methodology — iterative delivery, fit-to-standard, and the role of Solution Blueprint Reviews.
Browse every guide in Implementation or just Methodology.
Was this helpful?
Signals which guides land and which need work. No account, no comment box — corrections go through the contact page.
Spot something wrong or want a topic covered? Send a correction or a topic request — both are welcome.