What’s new in DataMigrate Pro?

DataMigrate Pro can reconcile data between NAV and Business Central. A lot has been added since this function was introduced. This overview covers what helps most in day-to-day migration work. It is a selection, not a complete change log.

Reconcile NAV and Business Central

Do the numbers add up after the migration? The reconciliation answers that. It compares the data in the NAV SQL database with the current values in Business Central, only reads and changes nothing. It checks open customer and vendor entries as well as the balances of G/L accounts, customers and vendors. Further reports compare postings by general and product posting groups and by VAT groups, plus inventory quantities and inventory values.

The reconciliation takes cut-off dates, periods and opening balances into account, as well as the value mappings used in the migration. Differences and control totals are presented in plain terms. You can save the results as CSV, HTML or JSON.

GDPdU export for audits

For selected financial data, DataMigrate Pro creates separate GDPdU archives from NAV and Business Central. The export runs directly from the reconciliation or on its own. You set company and posting period independently of each other. Each archive contains the index file index.xml, the GDPdU DTD and the exported raw data.

The configurable finance profile covers 32 tables and 430 fields. For NAV, DataMigrate Pro reads the stored columns of the chosen tables from the source schema, customer-specific fields included. FlowFields that are not stored, and optional fields that do not exist in older NAV versions, do not count as gaps. For Business Central, the published pages and the profile determine the selection.

The data is streamed and the archives are checked offline against the DTD. Missing tables, keys, pages or fields are named explicitly, and an incomplete export is marked as such. If a technical error occurs, you do not get a half result: neither archive is published.

Prepare cutover and opening balances

The ledger cutoff functions support a planned switch. They analyse data up to a cut-off date, check open entries and account balances, and determine opening balances and the necessary offsets consistently. Depending on the scenario, they also take inventory and fixed assets into account.

Business departments review and decide in a guided interface. Every setting is documented with its effective value, origin, default value and decision note. Changes and invalid combinations are checked, and verification detects decisions that were frozen after the opening balance. A SHA-256 fingerprint ties the effective settings to the evidence of the run.

Evidence for analysis, start block and verification

Ledger cutoff diagnostics can create an audit ZIP automatically. It contains HTML reports in German and English, complete JSON and CSV evidence, the effective decisions, open entries, critical check results and time-stamped snapshots. A SHA-256 integrity manifest shows whether the archived files are unchanged.

The evidence is tied to the CLI runs, the previews in the Mapping Editor, the start blocks and the verifications. You can see at any time whether records were planned, confirmed, processed as a test or exported. The original source keys are kept apart from the converted target numbers.

Inventory and fixed assets also leave a trail: layer and stock evidence, inventory values against G/L accounts, fixed asset control totals, and CSV exports of the results. On request, verification runs these checks again and tests offsets, lookups and transfer limits. Whether an error counts as a blocker is up to you, set by decision. That way it does not slip unnoticed into a start block.

Maintain value mappings more easily

Classification suggests mappings for important master data and posting groups. You review the suggestions, add missing values from the source data and check the changes before they are applied. The interface also shows the descriptions and the conditions that apply to a mapping.

Editing has become easier: values can be pasted from Excel, imported and exported as CSV, and filtered. Preview, validation and synchronisation make changes easier to follow. That lowers the risk of applying a wrong mapping to further tables.

More transparent control of mapping and migration

The Mapping Editor has become clearer and more reliable in many places. You can select and reset mappings precisely, and changes are saved reliably and passed on to Business Central. You check configuration changes before applying them, and missing source fields or ambiguous mappings show up early.

New is a read-only mapping audit report in German or English. It explains table and field mappings, links, calculations, value translations and transfer evidence, and contains complete value lists and a mapping fingerprint. You can export it as print-ready HTML, as Markdown or JSON, and individual sections also as CSV.

The report includes the actual transfer data: which tables transferred records, how many, and over what period. It describes the relevant value mappings in the language of an audit, for example how G/L, customer and vendor numbers from NAV are translated into the numbers in Business Central. Source and target values are listed in full. Whoever audits can therefore compare the documented mapping state with the migration that was run.

Coverage reports for value mappings add key figures and lists of open or conspicuous mappings, as CSV or HTML.

Keeping an eye on large runs

During cutover and migration, progress indicators show the current step and the run status. Analyses can be cancelled on purpose. You adapt larger transfers to your environment through configurable batch sizes. Additional checks and clearer error messages show problems before anything is written to Business Central.

Demo mode

Demo mode guides you through setting up a local demo environment and prepares sample data for a test run. This way you get to know DataMigrate Pro without first building a source environment of your own.

DataMigrate Pro with AI agents

An MCP server that a few customers are testing at the moment makes selected functions available to AI agents such as GitHub Copilot. Writing and executing actions are off by default. More in a separate post: DataMigrate Pro with AI agents: the MCP server.

Further improvements

• An offline decoder supports the analysis of FOB codeunits.
• DataMigrate Pro now handles NAV schema variants and missing fields more robustly.
• Progress, diagnostic and audit information make troubleshooting and the review of results easier.

Individual technical fixes and version-specific details are in the version history. If you would like to see one of the new features on your own data, get in touch: Contact. More about the product is on the DataMigrate Pro page.