What you are actually choosing between
If you are retiring Dynamics GP, someone has told you that history still has to be reachable. Auditors ask for FY2019 invoices. A customer disputes a 2017 order. Tax reviews reach back years. Business Central will not answer those questions, because that data was never loaded into it.
There are two commercial shapes for solving it, and the difference is not really technical:
- ✓A subscription viewer. You pay monthly or annually. The vendor gives your staff a way to browse the old records, often through a connector or a portal alongside the new ERP. Access continues while you keep paying.
- ✓A one-time archive. You pay once. The history is extracted into a file that you keep, with a reader that opens it. Nothing renews, and nothing switches off.
Both are legitimate products. They suit different situations, and the honest comparison is about ownership and time, not features.
The five-year arithmetic
Retention obligations are measured in years, not months, so any comparison over a single year is misleading. Most finance teams need historical records available for at least seven years, and often longer for fixed assets, warranty and employment records.
Put both options over the period you actually have to keep the data:
| Over five years | Subscription viewer | One-time archive |
|---|---|---|
| What you pay | A recurring fee, typically per user or per connected data source, for every year you still need access | One payment, at the start |
| What happens if you stop paying | Access ends. The history is still in the vendor's format or platform, not in your hands | Nothing. The file and the reader keep working |
| Where the data lives | Often in the vendor's cloud or behind their connector | On your storage, on your network |
| Price certainty | Subject to renewal pricing and per-user growth | Known on day one |
| Auditor access | Usually needs a seat, or a person with a seat to run it | Open the file; no seat, no licence |
The question worth asking a subscription vendor is simple: what does year six cost, and what do I have if I stop paying in year four? If the answer is that access ends, then you are renting your own accounting history for as long as the law requires you to keep it.
When a subscription genuinely is the better answer
There are real cases where it is, and you should not buy an archive in any of them:
- ✓You still need live, two-way integration. If old data must feed dashboards, be joined to current ERP records inside the new system, or appear on live reports, a connector-based product is doing something an archive file is not designed to do.
- ✓Your retention window is genuinely short. If you only need to look back 18 months and then the obligation ends, a short subscription can cost less than a one-time purchase.
- ✓You want the old system's exact reports reproduced. An archive preserves the records and lets you query and export them. It does not recreate every Management Reporter or SSRS layout.
- ✓Nobody will own the file. If there is no one to store a file safely and no backup discipline, a hosted service removes a real operational risk.
If two or more of those describe you, stop reading. The subscription is the right product.
When a one-time archive is the better answer
- ✓The data is finished. Retired GP history never changes again. Nothing will post to it. Paying a recurring fee for a data set that is closed is paying rent on something that has stopped moving.
- ✓The obligation outlasts the vendor relationship. You must keep records for seven years or more. That is a long time to depend on another company's pricing, ownership and continued existence.
- ✓Access is occasional but must be immediate. Most teams query old history a handful of times a quarter, then not at all for months. Per-seat pricing fits poorly with that pattern.
- ✓You want the server gone. The point is to stop paying for a Windows Server licence, a SQL Server licence, a VM and a backup job that exist only to hold history.
Questions worth asking either vendor
Whichever direction you lean, these five answers tell you most of what you need to know:
- ✓Can you prove the copy is complete? Ask for the reconciliation method. Totals in the archive should be checked against totals in GP, account by account, before anyone switches a server off. If a vendor cannot show you that, you are trusting a copy nobody verified.
- ✓What happens when I stop paying? Ask it plainly and get the answer in writing.
- ✓Who can open it in year seven? A new controller who has never seen GP should be able to search by customer name and invoice number, not by table number.
- ✓Can I export what I find? CSV and XLSX at minimum, and a readable document for an auditor.
- ✓Does anything leave my network? For a data set containing every customer, vendor and payroll record you have ever had, this matters more than it usually does.
If you want the underlying cost categories rather than the commercial shapes, see Dynamics GP archive cost. For the alternatives that involve no vendor at all — keeping GP running, or keeping a SQL backup — see ways to keep GP history and is a SQL backup enough?