Dynamics GP end of life: dates, risks and a practical data plan

The published Dynamics GP dates

Microsoft has announced the end of Dynamics GP product enhancements, regulatory updates and technical support on 31 December 2029. Security updates continue until 30 April 2031. New perpetual license sales ended on 1 April 2025 and new subscription license sales ended on 1 April 2026.

These are product-wide milestones. Older GP releases also have version-specific fixed lifecycle dates, so identify the exact version and build before relying on the final 2029 and 2031 dates.

What end of support changes

GP does not erase itself when support ends. A working installation may continue to launch, and the SQL databases remain on disk. The operating risk changes around it:

• Tax, payroll and regulatory changes stop arriving through the supported product channel.
• New defects and compatibility problems no longer receive ordinary fixes.
• The application and its dependencies become harder to keep on supported Windows and SQL Server versions.
• After security updates end, newly discovered vulnerabilities can remain unpatched.
• Staff and partners with deep GP knowledge become less available over time.

A read-only GP server still contains production-grade financial and personal data. Stopping users from posting reduces operational risk, but it does not remove the server, authentication, backup, patching or breach surface.

The migration and the history problem are separate

A new ERP project usually has a clear operational scope: current master records, open transactions, opening balances and the data needed for business continuity. Twenty years of posted history often stays behind because old document structures, posting behavior, dimensions, currencies and third-party modules do not map cleanly into the destination.

Leaving history out of the new ERP can be the right decision. It still requires a separate answer for old invoices, payment applications, item history, serial numbers, record notes, tax requests and audit samples.

There are four common history strategies:

1. 01Keep GP and SQL Server running in read-only use.
2. 02Keep database backups and restore them when a question arrives.
3. 03Export selected tables or SmartLists to flat files.
4. 04Create a purpose-built archive with search, queries, documents and reconciliation.

Compare them in detail in ways to keep Dynamics GP history.

A practical schedule

12 to 24 months before target retirement

Inventory GP companies, databases, modules, versions, integrations, third-party products, custom tables, reports and retention obligations. Decide which records will enter the new ERP and who still needs historical access afterward.

During migration design

Create a rehearsal archive or equivalent historical environment. Ask controllers and auditors to use it for real questions. Build repeatable migration extracts and settle how balances will be compared at cutover.

Before go-live

Define the final posting freeze or SQL snapshot, named approvers, reconciliation thresholds, archive permissions, backup locations and rollback period. Do not leave the historical data decision for the week of go-live.

At cutover

Extract from a consistent source state. Reconcile row counts, fiscal-year trial balances and module control totals. Record the final file hash and have the controller sign off on the result.

After go-live

Keep GP available for a short, agreed parallel period. Route real historical requests through the archive. Once the team can answer them and the final evidence is accepted, decommission the old environment according to the approved plan.

Questions the steering group should answer

• ✓Which exact GP versions and SQL Server versions are running?
• ✓Which companies and modules contain records with active retention requirements?
• ✓Which third-party tables and document attachments must survive?
• ✓What will be loaded into the destination ERP, and what will remain historical only?
• ✓Who needs to search history after cutover, and from which devices or networks?
• ✓Which totals must reconcile before the shutdown is approved?
• ✓How will the final archive be permissioned, encrypted, backed up and recovery-tested?
• ✓Who owns the final decommission decision?

Primary source: Microsoft Dynamics GP documentation and discontinuation notice. Verify current dates and your contract-specific use rights with Microsoft or your licensing adviser before making a legal or procurement decision.