Same vendor, no upgrade path and the danger of false familiarity
Understand why Business Central's shared Microsoft branding with D365 F&O creates a programme-shaping illusion — identical vocabulary hiding incompatible architectures, and why this path is explicitly not the AX 2012 same-lineage upgrade.
What you will be able to do
Explain why Business Central shares no code, data or upgrade path with D365 F&O despite the common Microsoft brand
Name the five defining migration challenges that shape programme effort
Distinguish the BC posting-group matrix from the D365 posting-profile architecture
Describe the AL extension model and why no artifact converts to X++
Classify companies, environments and tenants as the first programme decision
Identify the false-familiarity terms that cause the most dangerous design errors
Introduction
Every other migration path on this site brings a source system from a different vendor into D365 Finance & Operations. SAP, Oracle, Infor, Workday — none shares a vendor relationship with the target, so teams expect a full translation effort and staff accordingly.
Same branding, different product architecture
The relationship between Business Central and D365 F&SCM is frequently misunderstood. The confusion is understandable — both products carry the "Dynamics 365" marketing name, both are sold by Microsoft, and both address ERP scenarios. But beneath the brand they are architecturally independent systems with independent histories.
The NAV lineage and where your customer sits
Business Central is the current generation of a product line that stretches back to Navision Financials in the 1990s. The version a customer runs determines what the programme encounters:
The five defining migration challenges
These are the structural challenges that consume programme effort. They are not configuration tasks — they are design decisions with downstream consequences that cascade through every subsequent workstream.
The false-familiarity lexicon
These terms appear in both products but mean structurally different things. Programmes that fail to disambiguate them early produce designs that look correct on paper but fail in functional testing.
Deployment and extraction: online versus on-premises
Business Central online is a fully managed SaaS environment. There is no direct database access. Evidence must be acquired through:
What does transfer: business meaning and auditable totals
Despite the architectural incompatibility, the programme does preserve genuine business content:
Knowledge check
Summary
Business Central and D365 Finance & Operations share a vendor and a great deal of vocabulary. They share no application runtime, extension model, organisation model, posting model, or database-upgrade path. This is not the AX 2012 same-lineage upgrade — there is no code or data upgrade path at all.