NAVEKSA-modules. Data-migration from C/AL to BC-AL
The migration-tool consists of two elements:
1. An export-function to be installed in and executed from the old C/AL-development environment
2. A standard function in the NAVEKSA BC-Apps to import the data into BC.
Make sure, that you execute both elements running the same language on the systems. Otherwise the
migration will not work !
First element includes a fob-file (NAVEKSA MigrationTool NAV2BC.fob) with two objects:
A report (6170500) and a codeunit (6170515). You must run the report which then executes the codeunit.
The report is not implemented in the NAV/BC menu-system, but needs to be executed from the
development environment.
When you run the report, you must select which App(s) you want to have data exported for.
You can select one or more Apps:
In addition you can select if you want data in your old database deleted after export.
Please observe: This is only relevant, if you do a full data-conversion from NAV to BC and want to remove
the NAVEKSA data before doing the conversion.
Make sure you make a full database backup before deleting any data in case you might need them later.
Deletion of old data is not needed for the migration-tool to work.
Please observe, that after deletion you can of course not run the export again.
Make sure to test everything in full scale before deleting any data.
When you run the export, the system will ask you where to save the data.
Select a place in your file-system for the data-file.
If you have selected to export data for more than one App, the system will prompt you for saving each
individual data-file.
Feedback
Powered by
Post your comment on this topic.