Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsMicrosoft will end product support and updates for Dynamics GP on December 31, 2029, with security patches scheduled to continue through April 30, 2031. The product-support date was revised from September 30, 2029, in a January 2025 update. The deadline does not mean GP will stop running, and Microsoft has not made migration to Business Central mandatory. It does mean customers should plan how they will manage support, security and compatibility risks. Microsoft’s announcement sets out the current dates.
What Microsoft is ending—and when
The announcement concerns Microsoft Dynamics GP, the on-premises ERP product formerly known as Great Plains. It does not cover Microsoft’s entire Dynamics portfolio, and it does not announce the end of Dynamics 365 Business Central.
Microsoft first announced a September 30, 2029 end date for GP product support and updates on September 25, 2024. On January 15, 2025, it moved that date to December 31, 2029, citing customers’ need to complete payroll and tax obligations for the full year. Security patches are scheduled to end separately, on April 30, 2031. Microsoft’s published dates are the current commitment; customers should check the applicable terms for their version and agreement.
| Milestone | Date | What it means |
|---|---|---|
| GP product support and updates end | December 31, 2029 | Microsoft’s current date for the end of product support and updates. |
| GP security patches end | April 30, 2031 | Scheduled end of Microsoft security patches for GP. |
Microsoft’s broader direction developed over several years: it announced an end-of-innovation direction for GP in 2022, and new GP license sales were to end after April 2025. The later support announcement set the product and security dates. For licensing and transition context, see CIO’s report.
#1 Best Overall
End of support is not an automatic shutdown
GP is not scheduled to switch off on January 1, 2030. An organization may be able to keep using its installation, but it should not expect ordinary Microsoft product fixes or updates after the product-support date. After the security-patch date, newly discovered vulnerabilities may not receive Microsoft patches.
That can complicate security reviews, audits, cyber-insurance assessments and customer or regulatory requirements. The actual exposure depends on the GP version, hosting arrangement, connected systems, controls and contractual obligations; the deadline alone does not make every installation unlawful or unusable.
Migration to Business Central is not mandatory
Microsoft recommends Dynamics 365 Business Central as a destination for many GP customers. That recommendation is not the same as a universal requirement to adopt Business Central. Depending on its needs, an organization could continue operating GP with accepted safeguards, obtain specialist maintenance, select another ERP, or replace some functions with separate applications.
Business Central is not necessarily a direct, in-place upgrade. The right destination depends on functional requirements, the amount of customization and integration work, data-retention needs, geography, compliance constraints, budget and appetite for cloud release changes. A GP customer with complex manufacturing or international requirements should validate product fit rather than assume the recommended destination covers every workflow.
Why GP migration takes more than installing new software
Microsoft’s documented path for migrating an on-premises Business Central environment to the online service illustrates the work involved: planning, data review, cloud setup, replication, data upgrade, configuration, user access, integration reconnection, testing and go-live. That documentation is for Business Central migration, not a guarantee that every GP customer’s data or configuration will move automatically.
Microsoft warns that data, users, permissions, system tables, record links and extension data may not all migrate automatically. Replication can also overwrite online data if configured incorrectly. See Microsoft’s migration documentation for the documented process and limitations.
Before choosing a platform, build an inventory that covers:
- GP version, service pack, database version, companies, legal entities, currencies and countries.
- Modules in use, such as general ledger, payables, receivables, fixed assets, inventory, manufacturing, project accounting, payroll and distribution.
- Customizations, Dexterity code, VBA, third-party add-ons, reports and extensions.
- Connections to banks, tax and payroll services, CRM, e-commerce, warehouses, EDI, payment processors and reporting tools.
- Historical-data retention, user roles, segregation-of-duties controls, audit trails and contractual requirements.
- Month-end, year-end, payroll, tax and regulatory processes that need validation.
- SQL Server and Windows Server support status, backups, disaster recovery and restore-test results.
- Available internal staff and experienced external partners.
Microsoft, SAP and Oracle have different support models
The shared trend is toward cloud platforms, but these vendors are not applying identical deadlines. Microsoft has set GP product-support and security-patch dates. SAP offers successive maintenance stages for relevant Business Suite 7 products. Oracle’s current policy lists long support horizons for several continuous-innovation products, subject to exceptions.
| Vendor and product family | Current support position | Important qualification |
|---|---|---|
| Microsoft Dynamics GP | Product support and updates through December 31, 2029; security patches scheduled through April 30, 2031. | The product-support date was revised from September 30, 2029. See Microsoft’s announcement. |
| SAP Business Suite 7 | Mainstream maintenance through the end of 2027; optional extended maintenance through the end of 2030. | Extended maintenance carries a two-percentage-point premium on the maintenance basis. Scope and product conditions apply. See SAP’s support strategy. |
| Oracle PeopleSoft Continuous Innovation | Premier Support through at least December 2037 in Oracle’s policy effective August 7, 2026. | Product exceptions apply, and “at least” is not a promise of permanent support. See Oracle’s Applications Lifetime Support Policy. |
| Oracle E-Business Suite 12.2 | Premier Support through at least December 2037 in the August 7, 2026 policy. | Continuous-innovation and product-exception rules apply. See Oracle’s Applications Lifetime Support Policy. |
| Oracle JD Edwards EnterpriseOne 9.2 | Premier Support through at least December 2037 in the August 7, 2026 policy. | Tools and individual components can have separate conditions. See Oracle’s Applications Lifetime Support Policy. |
For SAP, mainstream maintenance, paid extended maintenance and customer-specific maintenance are different levels of coverage; they should not be treated as interchangeable. For Oracle, the listed continuous-innovation releases receive functionality, updates and fixes through updates to the existing release, rather than necessarily requiring a major-version replacement. Oracle encourages customers to consider Fusion Cloud Applications, but that does not erase its published support commitments for the named products.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to choose a path away from GP
Continue with GP for a defined period
Keeping GP can minimize immediate disruption where the installation is stable and a replacement requires careful preparation. It is a risk decision, not a way to extend Microsoft’s dates. Specialist support may cost more as expertise becomes harder to find, while surrounding operating systems, databases, hosting platforms or integrations may become unsupported sooner. A read-only historical archive may be more appropriate than a fully operational system when GP is used mainly for lookup.
Evaluate Business Central
Business Central is a natural candidate for organizations that fit its capabilities and value alignment with Microsoft’s cloud ecosystem. Assess whether its selected edition and extensions cover the organization’s manufacturing, distribution, payroll, reporting and localization needs. Include recurring subscription costs, partner services, integration work, training and data conversion—not just software licensing.
Consider a different ERP or a narrower replacement
Larger, global or process-intensive organizations may assess SAP S/4HANA Cloud or Oracle Fusion Cloud ERP; a finance-led or midmarket buyer may compare other systems, including Sage Intacct or Acumatica. These are options, not rankings: compare deployment model, operational depth, payroll availability, customization approach, partner coverage and geographic fit. Some organizations may replace only selected accounting, inventory, payroll or finance functions rather than move every process to one suite.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Build a migration plan around business risk
- Set the scope. Identify every GP instance, business unit, module, integration, customization and reporting dependency. Include acquired entities and regional variations.
- Define requirements and constraints. Record functional needs, data-location or sovereignty rules, audit obligations, historical-retention periods, deployment preferences and release-management tolerance.
- Compare full costs. Model subscriptions or maintenance, implementation, data cleansing, customization replacement, integration redevelopment, testing, training, internal staffing, parallel operations, cutover, ongoing administration and exit or data-export needs. No single public price establishes the total cost for an individual migration.
- Shortlist partners and products. Ask each implementation partner for deliverables, assumptions, exclusions, milestones, testing responsibilities and post-go-live support. Reject a generic “upgrade” proposal that does not first assess data, modules, customizations and integrations.
- Run a representative pilot. Migrate realistic data and test more than basic accounting: include payroll, tax, EDI, warehouse operations, reports, month-end and year-end tasks, permissions and reconciliations.
- Plan cutover and recovery. Set rules for source-system changes during migration, reconciliation ownership, backups, rollback criteria, parallel operation and user sign-off. Document how audit history and retained records will be accessed.
- Review cloud terms where relevant. Examine service levels, release timing, price changes, renewal and termination terms, data export, portability and data retention before signing.
Waiting until 2029 may leave too little room to resolve difficult customizations, integration failures or payroll and tax timing. The schedule should reflect the organization’s risk and project complexity, not just the final support date.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
