Dynamics 365 Finance & Operations: A Complete Implementation Guide
April 2, 2026A practical guide to implementing Dynamics 365 Finance and Operations. Phases,...
Read moreMicrosoft Dynamics NAV served businesses well for over two decades, but it has reached end of mainstream support. Business Central is its successor - cloud-native, continuously updated, and integrated with the full Microsoft ecosystem.
If you are still running NAV (any version from 2009 to 2018), migration is not optional - it is a question of when, not if. Here is how to approach it.
A NAV to BC migration typically includes:
This is the hardest part. NAV customisations were built in C/AL - which does not exist in Business Central. Every customisation needs to be evaluated:
A typical NAV to BC migration runs 3–6 months depending on complexity. Heavily customised systems with large datasets take longer. We run 2–3 mock migrations before the real cutover to validate data accuracy.
At DynamicUnit, we have migrated businesses from NAV 2009 through NAV 2018. We know where the data mapping breaks, where the edge cases hide, and how to get your opening balances right on day one.
A practical guide to implementing Dynamics 365 Finance and Operations. Phases,...
Read moreA practical guide to data migration for ERP implementations. Planning,...
Read moreAn honest comparison of Microsoft Dynamics 365 CRM and Salesforce. Features,...
Read more