NOTE: for the purposes of this blog I'm using Dynamics NAV, this scenario applies to any ERP that has multiple versions of predefined projects in the Jet Enterprise CubeStore.
We're all familiar with this situation. Acme Corp has been on NAV 2009 or v5 for years and they've finally decided to upgrade to NAV 2015. How do we handle data migration? Do we transfer beginning balances? Move all the transactions? Restructure the Chart of Accounts? Redo the Dimensions? All of the above?
Instead of handling the data migration in the new ERP, I'd consider using Jet Enterprise to combine legacy and current data in your Data Warehouse (DWH) and Cubes. In addition to saving time and effort during NAV implementation, integration into the DWH ensures that the user will have a complete and consistent historical view of their data across two generations of ERP's, as opposed to truncating reporting history at the Go Live date when beginning balances were imported. Additionally, if ERP's perform best with smaller table sizes, then choosing not to import the past few years of data can only be beneficial. In fact, data warehousing with Jet Enterprise could allow you to begin truncating old data from your CURRENT NAV system to maintain system performance.
The solution in this case study is the integration of data from a New NAV 2015 Enterprise project into a highly customized NAV 2009 Enterprise project by use of the Add External Business Unit feature.
Readers might ask, "Why have two projects? Wouldn't it make the most sense to just have one project?" The short answer is 'yes', long term it would be most ideal to simply have two datasources and one staging database in the same project (as opposed to importing from a second live project), but the premise of this case is to minimize development time! By integrating a complete external business unit, we avoid the development time required to transform 50+ NAV 2015 tables to fit our NAV 2009 Data Warehouse's model.
NOTE: There may be additional licensing required to utilize the features mentioned in this blog. Please follow up with your Jet Enterprise software provider.
Also. This post demonstrates a feature and set of techniques that exist within Jet Enterprise. This is NOT a recommendation nor is it a Recommendation or Best Practices on how to handle a ERP upgrade.
If you are planning a Jet Enterprise upgrade, please feel free to reach out to Onyx Reporting or another knowledgeable Jet Reports certified resource for guidance.