GP Add-Ons and ISV Solutions: What Happens When Your Third-Party Tools Lose Support
Why 'it still works' isn't the same as 'it's supported'
The payment processing add-on still processes payments. The advanced reporting tool still generates reports. Everything looks fine, right up until an operating system update breaks something, or a new PCI compliance requirement lands and the vendor tells you they're no longer supporting that version. ISV support risk is unusual in that it's invisible until the exact moment it isn't, and by then you're troubleshooting under pressure instead of planning on your own timeline.
What losing ISV support actually looks like in practice
It rarely arrives as an announcement. More often, it shows up as a support ticket that used to get a same-day response now taking two weeks, or a vendor saying a bug fix "isn't planned for that version." Then a required OS or browser update breaks compatibility, and the vendor's answer is an upgrade to a newer, potentially GP-incompatible product line rather than a patch. Certification or compatibility assurances may lapse in the background while the add-on still appears to function.
Why this is accelerating for GP specifically right now
Some independent software vendors that build add-ons for payment processing, advanced reporting, warehouse management, and eCommerce integrations are shifting development resources toward newer ERP platforms. Support plans vary by vendor and product, so organizations should verify the timeline for every add-on rather than assume all GP integrations have the same end date.
Microsoft has confirmed that Dynamics GP product enhancements, regulatory updates, and technical support will end on December 31, 2029, with security updates available if needed through April 30, 2031, as detailed in Microsoft's official Dynamics GP support announcement. These dates refer to Microsoft's GP lifecycle—not necessarily the support commitments made by independent add-on vendors.
The domino effect: one unsupported add-on creates risk elsewhere
An unsupported add-on rarely stays contained to itself. When a payment processing tool stops receiving updates, teams may build a manual workaround to keep transactions flowing, creating new opportunities for human error and a weaker audit trail where controls should be strongest. If an add-on affects payment card data, unsupported software can also complicate PCI compliance assessments. Whether it creates an actual compliance gap depends on the organization's environment and applicable requirements.
This pattern appears in ERP internal controls work broadly: workarounds built to patch one gap may introduce new gaps elsewhere, which can accumulate until an audit or operational incident reveals them.
Auditing your ISV footprint before it becomes urgent
Start by listing every third-party add-on currently connected to GP, however minor it seems. Check each vendor's published roadmap and support timeline for its GP-specific product. Flag add-ons that touch compliance-sensitive processes such as payments or payroll, and identify which have a clear upgrade path versus which have none.
The effort required depends on how many integrations your organization has and how well they are documented. The goal is to turn a vague concern about "our add-ons" into a concrete, prioritized list, which is a far better position to plan from than discovering a gap when something breaks in production.
This doesn't have to mean an immediate full migration
Finding that two or three add-ons are at real risk doesn't automatically mean the whole ERP needs to change this quarter. Sometimes the right near-term move is replacing a single at-risk add-on with a supported alternative while GP itself stays in place a while longer. Other times, the audit reveals enough accumulated risk across multiple add-ons that it becomes a strong argument for accelerating a broader Dynamics GP services conversation instead of patching each gap individually as it appears.
Either way, having the full list in front of you is what makes that a deliberate decision instead of a reactive one. For a related assessment of platform capabilities, see our Dynamics GP vs. Business Central comparison for finance teams.
Frequently Asked Questions
How do we find out if our ISV add-on is still actively supported?
Start with the vendor's published product roadmap or support policy page, then confirm directly with their support team, since roadmap pages aren't always kept current. If they can't give you a clear support end date, treat that ambiguity itself as a warning sign.
What's the biggest risk if we do nothing?
A major risk isn't only the add-on failing outright; it's the manual workaround your team may build to compensate, which can introduce errors or controls and compliance issues that are harder to detect than the original problem.
Can we replace a single risky add-on without touching the rest of our GP environment?
Often yes, especially for relatively standalone functions. Some add-ons are deeply woven into GP's core workflows, making a standalone swap harder. Assess compatibility and dependencies case by case.
Should this audit happen before or after we decide on a migration timeline?
Before. The results of an ISV audit can directly inform how urgent a migration timeline needs to be, since a heavily exposed add-on portfolio changes the risk assessment.
Comments