Dynamics GP end of support: what to do with your historical data

What does Dynamics GP end of support mean for your data?#

Dynamics GP end of support means Microsoft has set a staged retirement timeline for the product, so companies still on GP need a plan for both the system and the years of history inside it. The timeline ends sales of new licenses first and product support and security updates later. Confirm the current dates on Microsoft's official lifecycle pages, because summaries in partner marketing are not always up to date.

Installed GP software does not stop working on a given day, but running unsupported financial software brings growing risk: no vendor fixes, fewer partners and add-on vendors maintaining compatibility, and questions from auditors about controls. Microsoft offers migration tooling toward Business Central, and NetSuite, Acumatica and other ERPs are common alternatives. For most finance teams the practical question is not whether to move but what happens to the history when they do.

For a distributor, that history is substantial. Sales order processing, purchasing, inventory, receivables and payables records often reach back to the year the company first installed GP, with record notes and attachments that exist nowhere else.

A stage-by-stage timeline for your GP history#

The safest timeline for GP history follows your project milestones rather than calendar dates. Each stage below carries a data decision that is cheap to make early and expensive to make after the server is gone.

What often stays behind when GP moves to Business Central#

Detailed transaction history is the part of GP most often summarized or left behind when companies move to Business Central or another ERP. Migration tools and partners tend to focus on what the new system needs to operate: customers, vendors and items, open documents and balances, and some span of general ledger history.

What is left out depends on the tool, the options chosen and the partner's scope, so get the answer in writing. Some migration tooling can carry historical transactions across as separate read-only records rather than live documents; whether that option is used, and which modules and years it covers, is a scope decision. The records that tend to fall through the gaps are closed sales and purchasing documents at line level, inventory transaction history, record notes, Doc Attach files, custom fields and tables from ISV add-ons, Dexterity or VBA customizations, and the SmartList and report definitions people relied on.

None of that is needed to run the new ERP, which is why it is easy to drop. It is often exactly what a controller needs later for an audit question, a customer dispute or a sales tax inquiry.

What to archive before you migrate#

Archive GP history in two forms before cutover: a complete backup for fidelity and readable exports for use. A backup alone keeps everything but needs GP or SQL skills to read later; exports alone are convenient but can miss tables nobody thought to pull.

• 1Full SQL Server backups of the system database and every company database, including inactive or test companies that hold old history.
• 2Line-level sales history: quotes, orders, invoices and returns, with customer and item references.
• 3Purchasing history: purchase orders, receipts, vendor returns and landed costs.
• 4Inventory transaction history, cycle count adjustments and lot or serial records.
• 5Receivables and payables history, including applied documents and collection notes.
• 6Record notes, Doc Attach files and any document management store linked to GP.
• 7ISV add-on tables and custom fields, with whatever documentation explains them.
• 8Report definitions, SmartList favorites and month-end procedures that show how the data was used.
• 9A data dictionary of tables, keys and code values, written while staff who know GP are still there.

Archive formats compared#

The archive format decides whether GP history stays usable after the people who know GP move on. Most finance teams keep more than one, typically a backup plus readable exports.

Why a distributor's GP history may matter beyond retention#

A distributor's GP history may have value beyond compliance because it records years of real operating decisions: which customers ordered what and when, how backorders and substitutions were handled, which vendors shipped late and how returns were resolved. AI developers building tools for order management and inventory planning look for linked records with outcomes like these.

Retention and licensing are separate questions. Retention rules, set with your tax and legal advisers, decide the minimum you must keep. Licensing is an optional decision about whether part of that history, prepared to remove personal and confidential details, can be licensed to an AI developer while the company keeps ownership. A readable archive keeps that option open; wiping the server closes it.

Illustrative: a plumbing supply distributor retires GP#

Illustrative: a fictional plumbing and HVAC supply distributor with several branches has run GP since its early years and is moving to Business Central. The partner's scope covers master records, open orders and summarized ledger balances. Line-level sales history, RMA records and years of order notes are not in scope.

The controller adds a history workstream before cutover: full backups, flat-file exports of sales, purchasing, inventory and RMA history, and a short data dictionary written with the longest-serving GP administrator. GP stays read-only through the first audit on the new system. With history now readable, the CFO asks for a metadata-only fit check on the order and return history, keeping payroll and employee records out of scope from the start.

Where SourceX fits in a GP retirement#

SourceX can assess a retiring GP environment before the server is switched off, working from a description rather than files: which GP modules and add-ons were used, how far back each company database goes, and what contracts might limit use. No exports are needed for that first look.

If a package makes sense, it moves through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Rights review covers customer and vendor contracts, preparation takes out employee, contact and pricing details that should not travel, and the company approves every release, documented in a SourceX Evidence Packet.