Dynamics GP end of life: what to do with the history in your GP database

At Dynamics GP end of life, treat the migration and the history as two decisions. Confirm Microsoft's current lifecycle dates, choose how much GP history moves to the new ERP, and keep the rest in a tested, read-only archive. For companies with 50+ full-time employees at peak and many connected systems, assess that history before the GP database is retired.

What does Dynamics GP end of life mean for your data?

End of life ends Microsoft's support and updates, not the data. Every GP company database still holds its general ledger, payables, receivables, purchasing, sales and inventory history in SQL Server tables. That history stays usable only as long as someone keeps a compatible GP installation, a SQL Server instance and the knowledge to query it.

Microsoft has announced the retirement of Dynamics GP and publishes the dates for the end of new sales, product updates and security fixes on its product lifecycle page. Confirm the current dates there, and with your Microsoft partner, before setting a migration timeline; this page deliberately does not restate them.

For ERP consultants and GP resellers, the migration is the visible project. The history is the quieter decision: a typical migration moves master records, open transactions and a limited slice of history, and years of GP detail stay in a database that is eventually switched off.

What history a GP database holds

GP area	Records it holds	Why the history matters
General Ledger	Journal entries, account history, budgets, year-end closes	Shows how the business was run and reported over time
Payables Management	Vendors, invoices, payments, holds, voids	Captures approval, exception and dispute patterns
Receivables Management	Customers, invoices, receipts, credit and write-off decisions	Shows credit and collection decisions with their outcomes
Purchase Order Processing	Requisitions, purchase orders, receipts, matching	Records procurement workflows end to end
Sales Order Processing	Quotes, orders, fulfillment, returns	Links customer demand to delivery and returns
Inventory and manufacturing	Items, transfers, adjustments, costing	Records how operations responded to demand
Payroll and HR, where used	Headcount, pay history, positions	Confirms peak headcount, and contains personal data
Notes, attachments and add-ons	Record notes, attached documents, third-party tables	Often hold the reasoning behind a transaction

GP has been sold for decades, so a company that adopted it in its early years can hold its entire transaction history in one set of databases. Add-on products from independent software vendors often keep their own tables in the same databases, which matters for both the migration and the archive.

What makes GP history valuable beyond compliance

Finance records alone show what happened. Connected to the rest of the business, they show how decisions were made: a purchase approved after an email thread, an invoice disputed through a support ticket, a customer put on credit hold after a CRM note. AI developers are building agents that carry out multi-step business work, and training them needs records of real workflows with outcomes, material that rarely appears on the public web. Epoch AI researchers have projected that, if current trends continue, language models could use up the effective stock of public human-generated text between 2026 and 2032; it is a forecast with wide uncertainty, but it helps explain why permissioned, non-public business records are in demand.

A GP database on its own is rarely the whole story. The strongest candidates pair long GP history with email, Teams or Slack, a CRM, a ticketing system and project tools, often 10-15+ systems in all.

Migration paths and what each does to history

Path	History that usually moves	What stays behind	Watch for
Business Central using Microsoft's migration tooling	Master records, open items and the history options the tooling supports	Detail outside the migrated scope	Check Microsoft's current documentation for what is included
Another cloud ERP	Opening balances, open items and often summarized GL history	Most transaction detail	Each vendor's import limits and the mapping effort
Stay on GP for now	Everything, for the time being	Nothing yet	Growing security and support exposure as dates pass
Read-only GP archive	Full history on a retained installation	Nothing, if restores are tested	Licensing, server upkeep and someone who can still query it
Export to open formats or a data warehouse	Whatever you extract, in readable tables	Screens, drill-down and some context	Document what each table means before the GP experts leave

The last two rows belong in every plan. Whatever the destination, keep a full backup of every company database and the system database, and record which GP and SQL Server versions can restore them.

Export and retention realities

Restores need the right stack. A GP backup is only useful if a compatible GP version and SQL Server can open it, so test a restore before the old server is retired.
Customizations hide data. Modified forms, add-on tables and custom fields need a written map, or exported tables lose their meaning.
Retention depends on the record. Tax, payroll and contract records carry different retention periods by jurisdiction and industry; confirm them with the company's tax adviser and counsel.
Personal data comes along. Payroll, HR and some vendor records contain personal information, which needs access controls in any archive and would be redacted or excluded from any license.
People are the real deadline. The controller or administrator who knows the GP setup may leave after cutover, so capture what they know while they are still on the project.

How to spot a GP client worth a records conversation

The company had 50+ full-time employees at peak, contractors excluded; GP payroll or HR history can confirm it.
GP has been live for several years, with historical years kept rather than purged.
The company uses modules beyond the ledger, such as purchasing, sales orders, inventory, projects or field service.
Email, chat, CRM and ticketing systems run alongside GP, along with archives of retired tools.
The records are the company's own transactions, not data it processes on behalf of clients.
The owner or CFO would consider a one-time, exclusive AI-training license for an agreed term.
A full GP backup still restores.

Pitfalls that destroy GP history

Pitfall	Consequence	Fix
Decommissioning the SQL Server along with the GP install	Backups exist but nothing can open them	Keep one restorable environment or a documented export
Purging history to speed up the migration	Years of transaction detail are gone	Archive a full backup before any purge or cleanup routine
Ignoring add-on tables	Notes and workflow history are lost	Inventory add-ons and export their tables
Letting a hosted GP contract expire	The provider disposes of the data under its terms	Get full backups delivered and tested before the contract ends
Migrating mail or chat in the same window without preserving history	The context around finance decisions disappears	Coordinate with the Exchange Server end-of-support plan and any Slack to Teams migration

What to say to the client's CFO

If the client has a new CFO who is still mapping systems, the new CFO first 90 days guide shows where the GP history decision fits.

How the introduction works for a GP partner

Once the owner or CFO agrees, submit the company via your referral link or the referral form with a few basic fit details.
SourceX checks peak headcount, operating history, data breadth and rights with the company's authorized sponsor.
The company lists its own systems in a data inventory, and agrees price, terms and redaction rules before any buyer review.
AI labs and data buyers review; after signing, the company delivers its data and is paid.

Your migration work stays separate. You never send GP backups, exports or descriptions of what the databases contain to SourceX.

Next step

Add a GP history decision to every migration statement of work, and check long-standing clients against the who qualifies baseline. If one fits, register as a partner and draft the introduction with the introduction email builder. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company; rewards become payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The ERP consultant partner page covers the program in more detail.

Step 1Share your linkSend your personal link to a company you know.
Step 2Company appliesThe company applies itself at /apply.
Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Does Dynamics GP data disappear when Microsoft support ends?

No. The data stays in the company's SQL Server databases. What ends is Microsoft's support, updates and fixes for the product, so the risk is practical: servers age, licenses lapse, security exposure grows and the people who know the setup leave. Keep a tested, restorable backup and a documented export so the history stays readable after GP is retired.

How much GP history should we migrate to Business Central?

Enough for daily operations and comparative reporting, which for many companies means master records, open transactions and a limited number of prior years. Moving everything adds cost and mapping work. Keep the full history in a read-only archive or a data warehouse instead, and check Microsoft's current migration documentation for what its tooling can bring across.

Can a company keep GP running read-only after the migration?

In many cases, provided it keeps a working server environment, appropriate licensing and a SQL Server that can host the databases. Security exposure grows once updates stop, so restrict access and consider moving to a static export or warehouse over time. Confirm the licensing terms for read-only use with the company's Microsoft partner before relying on it.

What should we do if a hosting provider runs the client's GP?

Read the hosting contract before the end date, because it governs access, backups and what happens to the data at termination. Request full backups of every company database and the system database, confirm that they restore in an environment the client controls, and get the provider's deletion schedule in writing before the contract lapses.

Is payroll and HR data in GP a problem for a data license?

It needs care. Payroll and HR tables contain personal information, so they may be excluded or de-identified, and redaction and de-identification requirements are agreed with the company before any work begins. The finance workflows around vendors, purchasing and receivables often matter more for licensing than payroll history does.

Free resources

Enterprise value calculator — Enterprise value from equity value, debt and cash.
Earnout scenario calculator — Probability-weighted earnout value and its present value.
Profit margin calculator — Profit and margin across three scenarios.
All free tools · MCP resource center

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment