Objects upgrade time depends on how heavily customized the database is. For data upgrade we are using path NAV 2009 -> NAV 2015 -> BC14 -> BC18 and the main challenge is to migrate custom data from BC14 C/AL to BC18 extensions as data migration of custom field and tables should be handled by SQL scripts which have to be written manually.

The main step where all limitations are handled is from BC14 C/AL to BC18 extensions. We are using SQL scripts to handle the migration of all custom fields and tables and also to handle the workarounds of all limitations where migrating data is required.

We usually make all layout changes in BC14 C/AL version and then convert the layout using txt2al. After that, you just have to fill in the RDLCLayout property in ReportExtension objects that show the path of the report layout.

Data migration from NAV 2017 to BC14 C/AL is handled using Microsoft upgrade toolkits as usual. The part from BC14 to BC18 on-prem is handled using Microsoft tools for Migrating standard tables and fields and SQL scripts for migrating custom tables and fields. The last part from BC18 on-prem to BC18 SaaS is handled by SaaS toolkits that are stored in Microsoft cloud and no manual work has to be done in this step regarding toolkits – you just run the data migration process straight from the SaaS environment.

If you have any unanswered questions, please contact us at [email protected].