NAV 2009 to Business Central (Migration)

Read here how you can migrate directly from Dynamics NAV versions up to 20 years old to Business Central.
If you want to carry out a migration from NAV 2009 to Business Central, there is currently no official, direct migration path.
The classic path of migrating from version to version is used very often. However, it comes with considerable disadvantages:

• Considerable extra effort and therefore high costs
• Carrying over / modifying code that will be dropped later anyway (keyword: automation objects, dotnet)
• No way back
• "Hard cut" with the old system

When we speak of drawbacks, we mean technical and cost-related hurdles only. Our experience also shows that the longer a migration process takes, the faster user acceptance for the project drops.

Microsoft’s official website has a help article on the subject. The earliest officially supported path is NAV 2015 via Business Central 2019 (version 14) into the Business Central cloud. The many customers with installations on NAV 5.0, NAV 2009 (R2) and NAV 2013 (R2) usually have no choice but to start with a new installation. All historical data is lost in the process.

There is another route, however, that differs from the classic upgrade path and can be used from NAV 5.0 onwards.
With DataMigrate Pro (DMP) we offer a flexible way to transfer data from NAV to BC seamlessly. A short overview of our DataMigrate Pro tool:

• Continue working in the old system (e.g. NAV 2009)
• Parallel provisioning of Business Central (cloud)
• "Lift and Shift" - Both systems can be used in parallel (including transfer of balances, open entries and fixed assets and reconciliation of the number series) with live synchronization in both directions (NAV 2009 <-> Business Central Cloud)
• You decide when "Go Live" happens. Until then your users can work in both systems.

With DMP, live synchronization in parallel operation is possible, which ensures an uninterrupted migration. In addition, both master data and historical data can be transferred later on. This flexibility and efficiency make DataMigrate Pro a preferred solution for companies seeking a comprehensive and reliable migration of their data.

Setup

First the Navision objects of the configuration were installed so that the mapping of the data to be transferred could be carried out. Via the DataMigrate Pro menu, the structures of the current installation could be inserted into the mapping tool.

The structures of the target system have to be made available to the migration tool so that the target elements can be selected. A recurring job is run for this via SQL Integration Services.

Mapping JSON files are generated from the configuration. These are read out with a SQL query and the data is transferred.

Transfer master and setup data

Based on the change log, changes to the master data are now transferred regularly from NAV to BC.

Transfer entries

As a rule, entries in NAV are not logged. For this reason a mechanism determines which data has not yet been transferred from NAV to BC. Likewise, entries in BC may only be written by the posting codeunits intended for that purpose. In the second part of the setup, a DataMigration Pro Extension for BC ensures that the posting identity is preserved. After the entries have been transferred into shadow tables in BC, codeunits of the BC Extension are called from the NAV system.

Automatic interface check

The BC Extension contains overviews that automatically compare account totals from NAV with those from BC after the data transfer and present them via the Role Center.

Does that sound interesting to you as well? Then contact us by e-mail (kontakt@ioitempold.dreamhosters.com), or use the option to book a Teams appointment directly.