One of the first worries we hear from finance teams planning to leave Microsoft Dynamics GP is simple: what happens to all our history?
It is a fair concern. Many organizations have ten, fifteen or even twenty years of transactions in Dynamics GP. Auditors ask about past invoices, the sales team wants to see what a customer bought three years ago, and tax authorities can request records long after a year has closed. Nobody wants to lose that information when they move to a new system.
The good news is that you do not have to bring every transaction into your new ERP to keep it available. In this article, we explain the realistic options for GP historical data, including how to keep GP itself running in a read-only state, and how to choose the right approach for your business.
Why Not Simply Migrate Everything?
It can seem easiest to move every record from Dynamics GP into your new system. In practice, this is rarely a good idea.
- It adds time and cost: Every extra year of detail must be mapped, transformed, loaded and reconciled.
- It adds risk: Older data often contains inactive accounts, retired items and inconsistent coding that does not fit cleanly into a new structure.
- It clutters the new system: Your team wants a clean start, not years of old transactions mixed in with current activity.
- It is often unnecessary: Most history is looked at occasionally, not used every day.
That is why most projects split data into three groups: what you need live in the new system, what you need available for reference, and what you only need archived for compliance.
What Microsoft’s Migration Tools Bring Across
If you are moving to Dynamics 365 Business Central, it helps to recognize what Microsoft’s cloud migration tool already handles:
- Master data and open transactions: Such as customers, vendors, items, open invoices and unreconciled bank transactions.
- Summary General Ledger history: The tool creates summary transactions for open and historical years, based on your GP fiscal periods. You choose the oldest year you want to bring across.
- GP Historical Snapshot: You can choose to migrate detailed history for General Ledger, Receivables, Payables, Sales Order Processing, Purchase Order receipts and Inventory. This detail is stored in separate extension tables in Business Central, and users can view it through GP Detail Snapshot pages. It does not post to the live ledger, so your new books stay clean.
For many businesses, the Historical Snapshot covers most day-to-day lookups. It is not a full copy of GP, though. You will not have GP’s inquiry windows, SmartLists or custom reports, and anything not selected for the snapshot stays behind. That is where the options below come in.
Option 1: Keep Dynamics GP Running as Read-Only
This is the most familiar choice. You keep your GP system available after go-live, but lock it down so nobody can enter or post new transactions.
How to Make GP Effectively Read-Only
- Post or clear every open batch before cutover, and take a full backup.
- Close all fiscal periods for every series in Fiscal Period Setup, so no transactions can be posted to any date.
- Change most users to Limited users. In GP, Limited users can only read data through inquiry windows, reports and SmartLists. They cannot enter transactions.
- Review security roles so that only inquiry and reporting tasks remain assigned.
- Keep one administrator account with full access, for emergencies or auditor requests, and control who can use it.
- Restrict direct SQL access, so data cannot be changed outside GP.
- Document the setup, including which version you are on and where the backups are kept.
Advantages: Users see data exactly as they always have, with drill-downs, SmartList favorites and familiar reports. There is very little to learn.
Things to Consider
- You still need servers, SQL Server, Windows licensing, backups and security updates.
- You must keep a valid GP license. Under Microsoft’s current plan, GP subscription licenses can no longer be renewed after April 30, 2031, which is also when security updates end. Perpetual licenses can continue to run, but without any patches.
- Over time, older software becomes harder to support on newer operating systems and SQL versions.
Keeping GP read-only works well as a short to medium-term bridge, typically for the first year or two after go-live, while users get comfortable with the new system.
Option 2: Use the GP Historical Snapshot in Business Central
As described above, the Historical Snapshot brings detailed Dynamics GP transactions into Business Central without affecting your live ledger. Users find history without leaving the new system, which is a real advantage for daily lookups.
This works best when you plan it early. Decide which modules and how many years you need during the migration design, because the snapshot runs as part of the cloud migration. It is also worth testing with your finance team, so they know where to find the information after go-live.
Our Dynamics GP to Business Central migration process includes reviewing which history belongs in the snapshot and which belongs in an archive.
Option 3: Move Dynamics GP Data into a Data Lake or Data Warehouse
Another approach is to copy your GP database into a modern data platform, such as Azure Data Lake or Microsoft Fabric. Microsoft’s GP-to-Business Central migration tooling includes an option to copy GP data to Azure Data Lake, which makes this route easier than it used to be.
Once the data is there, you can build Power BI reports for summarizing and analyzing past performance, combine GP history with Business Central data for long-term trends, and switch off the GP application completely.
Advantages: No GP software to maintain, scalable cloud storage, and powerful reporting.
Things to consider: You need someone who understands GP’s table structure to build useful reports. Users will not have GP’s familiar screens, so common lookups should be prepared in advance.
Option 4: Third-Party Archive and Viewing Tools
Several independent software vendors and partners offer tools designed specifically for keeping GP data accessible after a migration. Some provide a web-based viewer of your GP data, some can display historical records inside Business Central screens, and some offer hosted copies of your GP environment for audit access.
These can be a convenient middle ground, but each adds an ongoing subscription or license, so compare the long-term cost with the other options.
Option 5: A Cold Archive for Compliance
For data you are unlikely to need except in an audit or legal request, a simple archive may be enough:
- A final SQL backup of every GP company database, stored securely with clear labels.
- Exported reports for key items, such as year-end trial balances, aged trial balances, vendor and customer history and fixed asset registers, saved as PDF or Excel files.
- A short document explaining what is in the archive and how to restore it if needed.
This is the lowest-cost option, but retrieving detailed information later may require technical help. Always check your retention requirements with your auditors and tax advisors before deciding what to keep.
Choosing the Right Mix
In reality, most organizations combine options. A common pattern we recommend looks like this:
| Data | Typical Approach |
|---|---|
| Master data, open transactions, current-year balances | Migrate live into Business Central |
| Last two to five years of detail | GP Historical Snapshot in Business Central |
| Older history needed for occasional lookups | Read-only GP for a limited period, or a data lake with Power BI |
| Long-term compliance records | Final SQL backups and exported reports |
We want to emphasize that there is no single right answer. The best mix depends on how often your teams look up old data, your audit and tax requirements, your IT resources and your budget.
Frequently Asked Questions
Can I Keep Using Dynamics GP After Moving to Business Central?
Yes. Many organizations keep GP available in a read-only state for a period after go-live. You will need to maintain a valid license and the supporting infrastructure, and security updates for GP end on April 30, 2031.
Does Business Central Migrate All My GP History?
Not into the live ledger. The cloud migration tool brings summary General Ledger history for the years you select, and the GP Historical Snapshot can bring detailed transactions into separate tables that users can view in Business Central.
What Is a Limited User in Dynamics GP?
A Limited user can view data through inquiry windows, reports and SmartLists but cannot enter or post transactions. It is a practical way to give read-only access to historical data.
How Long Should I Keep GP Historical Data?
It depends on your legal, tax and industry requirements. Check with your auditors and tax advisors, and plan your archive so the data stays accessible for that full period.
How Nevas Technologies Can Help
At Nevas Technologies, we have more than two decades of experience with Microsoft Dynamics and have helped many organizations move from GP while keeping their history safe and accessible. We can help you decide what to migrate, configure the GP Historical Snapshot, lock down GP for read-only use, and set up reporting on archived data.
If you are still running GP day to day, our Dynamics GP support team can keep it stable while you plan. And when you are ready to move, our Business Central consultants and implementation plans make sure nothing important is left behind.
Planning your move away from GP? Contact our team, or schedule a demo to see how your GP history can live alongside Business Central.
