Microsoft Dynamics 365 in 2026: a nearshore playbook for F&O, Business Central and CE
Microsoft Dynamics 365 covers a wider surface than most buyers realize — Finance & Operations for enterprise ERP, Business Central for midsize, Customer Engagement for CRM, plus the Power Platform that quietly holds it all together. In 2026, with AX and NAV moving out of support and Copilot embedded across the stack, most Dynamics estates need a sourcing reset. This playbook explains how to run implementation, upgrades and managed support with a nearshore partner — and where AI genuinely earns its keep.
Pick the right Dynamics, not the biggest one
F&O is the right answer when finance complexity, multi-entity consolidations or manufacturing depth justify it. Business Central wins for midsize companies that want a clean ledger, fast rollout and a healthy ISV ecosystem. CE (Sales, Customer Service, Field Service) is the CRM layer on Dataverse. Most buyers we meet have the wrong tier — F&O when BC would have shipped in half the time, or BC when F&O was always going to be needed. Fix this in scoping, not after go-live.
AX / NAV to cloud: brownfield, greenfield, or hybrid
On-prem AX upgrades to F&O and NAV to Business Central are rarely lift-and-shift. Brownfield preserves history but inherits a decade of custom layers. Greenfield re-engineers processes — cleanest, most expensive. The pragmatic middle is selective: rebuild the chart of accounts and core processes, migrate open transactions only, archive history out of the ERP. Most midsize migrations belong here.
Where AI cuts time without cutting corners
- Customization analysis: agents classify extensions and overlayered code by usage and remediation effort.
- Test data and regression: AI generates and maintains regression scripts across F&O and BC modules.
- Functional spec drafts: retrieval over existing config produces first-pass FS docs that consultants edit.
- Copilot rollout: pragmatic evaluation of which Copilot features earn their license cost in your org.
- Power Platform governance: agents audit Apps, Flows and Dataverse usage for shadow IT.
A realistic timeline
Business Central for a midsize, single-entity company: 4–7 months end-to-end. F&O for a multi-entity, multi-country group: 9–14 months with a nearshore senior team plus your internal process owners. The big-four 18–24 month number assumes a different team shape and a different billing model.
Risks we see most often
- Treating it as an IT project, not a business transformation.
- Carrying every overlayered customization forward by default.
- Buying Copilot licenses before evaluating where it actually pays back.
- Letting Power Platform sprawl unchecked across the org.
- Hiring a partner with no senior consultant on your time zone.
What to ask before signing
Who is the named lead consultant in my business hours? Show me a recent F&O or BC cutover runbook. What AI tooling do you use in regression and where is the human checkpoint? Which Copilot features have you actually shipped to users, and what was the measured impact? What does month-13 look like if we slip?