Migrating from Dynamics NAV without losing your history
NAV companies have G/L registers, CLE/VLE, and dated exchange rates. Re-posting history as if it were new invoices destroys the audit trail you already paid for.
NAV migrations fail in a specific way: the partner re-implements live posting for documents that already hit the G/L a decade ago. You get doubled revenue, broken customer statements, and a project that “almost ties.”
If you are not on NAV, skim for the principle: historical subledgers must link to historical journals, not invent new ones. If you are on NAV, this is the migration shape that keeps auditors calm.
Treat G/L registers as the authority
Every NAV G/L Entry already belongs to a balanced register. The destination system should import those registers as journals and leave them immutable. Sales invoices, credit memos, and payments then link to that history instead of posting a second time.
Skipping the G/L and only bringing open AR is how you lose the story of how you got here. Open items matter for collections; registers matter for truth.
Bring the exchange-rate log
NAV Currency Exchange Rate is not optional colour. Dated rates let P&L convert per posting date and keep statutory current result aligned with net result. A single closing rate card will understate old assets and break that tie.
Store rates as local currency per 1 foreign unit (scaled), not as NAV’s inverse currency factor, or every imported LCY amount will fight the UI forever.
Masters, then documents, then proof
Customers, vendors, bank accounts, number series, and the chart of accounts must land before invoices. Then posted sales and purchases, ledger entries, and bank ledger. Then reconcile counts and known golden documents.
Omnizone’s migration path is built for that full company import — including Lebanese P&L classifications on expense leaves after CoA repair. Partial “AR only” imports are fine for demos, not for production cutover.
What we refuse to fake
We do not silently rewrite branding on promote. We do not pretend Item Ledger / full FA history is done when only register seeds exist. Saying the gap beats discovering it in week two.
If your NAV company is a test copy named Z-Cronus, do not migrate it. Production candidates deserve the full pass; junk companies deserve deletion.
Related modules
Related guides
- Multi-currency accounting: what a system actually has to handle
- What actually goes wrong in an ERP implementation
Related glossary
FAQ
Will imported NAV invoices post again in Omnizone?
No. When G/L history is imported, payment and document journals stay skipped so registers remain the authority.
Do we need every NAV bank account?
Yes for statement continuity. Dormant accounts can be inactive after import, but dropping them mid-migration orphans bank ledger rows.