INDEPENDENT PRODUCT — NOT AFFILIATED WITH OR ENDORSED BY MICROSOFT hello@erpdataarchive.com
eda ERPDataArchive

For companies retiring Microsoft Dynamics NAV

Keep 20 years of Navision history without keeping NAV running.

Your migration to Business Central will take two or three years of history. This is where the rest of it goes — one local, searchable file, checked against NAV before anything is switched off.

READ-ONLY SQL ACCESS/ NO AUTOMATIC UPLOAD/ ONE-TIME — NO RENEWAL
Your NAV support dates
NAV 2016Ended April 2026
NAV 201711 January 2027
NAV 201811 January 2028
NAV 2009 / 2013 / 2015Already unsupported

NAV 2018 was the final release. Confirm your exact build against Microsoft's current lifecycle dates before planning around a deadline.

01

Runs on your network

Your NAV records are not uploaded to us.

02

Read-only source access

The supplied SQL user cannot post or change NAV data.

03

Reconciled before shutdown

Counts and accounting totals are checked against NAV.

04

No reader subscription

Opening and exporting an existing archive never expires.

What it saves you

You are paying to keep a server alive for data that never changes again.

NAV history is finished. Nothing will post to it. Everything below is what you stop spending once those records live in a file your team can actually use.

At cutover — this year

  • The server bill stops.The Windows Server licence, the SQL Server licence, the VM and the backup job exist to hold history. When the history is elsewhere and proven, they can all be cancelled — and NAV 2018 and earlier need ageing Windows and SQL versions that get harder to stand up every year.
  • One payment, known in advance.Pricing starts at $2,495. The free assessment confirms the scope and fixed price before you buy.
  • The migration gets smaller.Once the history has a home, it stops being an open question in the project. The free assessment takes 5 to 10 minutes and answers what is actually in there, which is usually the meeting nobody can finish.

Every year after — for as long as you must keep records

  • Nothing renews.No reader subscription, no per-seat charge when the auditor needs to look, no renewal to renegotiate. Opening the archive in year seven costs nothing.
  • An old question takes minutes, not days.Search a name or an invoice number, open the document, export it. No restoring a backup, no finding the one person who still knows the table layout, no standing a retired system back up to answer one email.
  • New staff do not need to learn NAV.The archive uses business labels and direct search, so historical lookups do not depend on the people who remember the old client and table layout.

Use your own licence, hosting and support costs when comparing the options. The archive replaces a recurring history-access cost with a one-time extraction price; the free assessment provides the fixed quote.

What your team can do

Old NAV data becomes easier to use.

Search across history

Find a customer, vendor, invoice, order, item or original NAV reference without reopening the old client.

Follow related records

Move between document headers, lines, ledger entries, dimensions and master records while retaining source-field context.

Build repeatable queries

Choose fields, dates, filters, groups and totals visually, or use the read-only SQL workspace for deeper analysis.

Export usable files

Create CSV, typed XLSX and PDF files with filters, row counts and the source archive identity recorded.

Answer an auditor

Produce a defined population, supporting records and totals from the same approved archive whenever the request arrives.

Use your own tools

Connect Excel, Power BI or another reporting tool when the built-in search and exports are not enough.

The problem, before the product

Business Central will not take all of it — and that is the right call.

Most migration teams choose a limited history window for Business Central instead of loading every posted transaction from NAV. The exact window belongs in your migration plan; older records still need a dependable home.

Business Central cannot answer a question about data that was never loaded into it. The archive keeps that older history searchable without adding it to the live ERP.

What moves, what stays behind →

The questions that keep arriving

Years after go-live, usually to someone who never used NAV.

  • ✓The annual audit. A date range, a customer, and the documents behind the numbers.
  • ✓A tax review. Transaction-level detail from before the migration.
  • ✓A customer dispute. One order from 2017, with its lines and its terms.
  • ✓A new finance hire. Who has never seen a NAV screen and never will.

How it works

Start free. Retire NAV only after the archive ties out.

The free software tells you what is in NAV. The paid software copies the records out, proves the copy matches NAV, and gives your staff a permanent way to use it after the server is gone.

  1. 01

    Assess, freeOne read-only program against your NAV SQL Server, 5 to 10 minutes. Reports companies, years of history per module, transaction counts, database size and any custom tables. Copies no transaction rows.
  2. 02

    RehearseThe first of two included extraction runs creates a working archive while NAV is still live, so your team can check real values against the source before cutover.
  3. 03

    Extract and reconcileThe final run works from the frozen cutover state and produces a reconciliation report: row counts per table, and the general ledger trial balance for every fiscal year with a difference column.
  4. 04

    Then switch NAV offOnly after your controller and IT provider have both accepted the evidence. Keep the archive and reader on your own storage, with your own backups.
Versions we support: NAV 2013 through NAV 2018. NAV 2009 and earlier used a different dimension model and are out of scope — we would rather say so here than discover it halfway through your project. See archive pricing →

Research before you commit

Dynamics NAV retirement guides

Browse all guides →
Lifecycle

Dynamics NAV end of life

The dates, what actually stops working, and what to decide.

Business Central

NAV history after a BC migration

What moves, what stays behind, and where the rest can live.

Options

Ways to keep NAV history

Dormant VM, SQL backup, Azure copy, subscription viewer or archive.

Find out what is in your NAV system.

Start with the free assessment. One read-only program against your NAV SQL Server, about ten minutes, and you get a local report showing exactly how much history you have and what it will cost to keep. Nothing is installed on the server and nothing is uploaded.

Request the free assessment