Your ERP Is Going End of Life After 2026: 4 Options for Cities, Counties and Districts
ERP end of life in 2026? Compare extended support, upgrade in place, vendor cloud and re-selection for cities and counties, with verified 2027 to 2031 dates.
On this page
- Key takeaways
- What ERP end of life actually means (and what it doesn’t)
- ERP sunset dates public agencies are facing (2026 to 2031)
- Why your real deadline is earlier than the vendor’s date
- Your 4 options when your ERP reaches end of life
- Upgrade or replace your ERP? How to choose the right option
- Common mistakes when an ERP end-of-support date is announced
- ERP end of life FAQ
- Plan your legacy ERP replacement before the sunset date
If your vendor has announced ERP end of life for your system, you have four real options in 2026: buy extended or third-party support, upgrade in place, move to the vendor’s cloud successor, or re-select through a competitive process. The right choice depends on how much time the sunset date actually leaves you once your budget cycle and procurement are done.
The vendor’s end-of-life date is not your deadline. For most cities, counties and districts, the real deadline lands well before it, because budget adoption, procurement and council approval all have to happen first.
Tyler has told the City of San Rafael it will stop supporting Eden beginning March 2027. SAP’s mainstream maintenance for ECC ends at the close of 2027. And Microsoft ends Dynamics GP product support on December 31, 2029.
Most end-of-life guides target manufacturers, so this one gives public agencies verified sunset dates, a comparison of the four options and a decision rule for each.
Key takeaways
Vendor sunset dates between 2027 and 2031 are already published for platforms many agencies run, including Tyler Eden, SAP ECC and Microsoft Dynamics GP.
Extended support buys time, not a plan. Australia’s federal government took SAP’s extension to 2030 specifically to get a longer transition window.
Third-party support can lower cost, but it can also cut you off from patches and updates, as Fresno found in 2021.
Start the decision at least two budget cycles before the vendor’s date (KCT rule of thumb).
Re-selection is the only option that tests the market, and it needs the most lead time.
What ERP end of life actually means (and what it doesn’t)
ERP end of life is the date a vendor stops developing, patching or supporting a software version. End of support usually arrives in stages: mainstream support ends first, then extended or security-only support, and finally nothing at all. Your system keeps running after that date, but the vendor stops fixing it.
Nothing switches off on the sunset date. What disappears is the safety net: bug fixes, tax table updates, security patches and someone to call when payroll will not run.
End of life vs end of support vs end of sale
The terms get used interchangeably, but they describe different milestones.
SAP and Microsoft both show how staging works in practice. SAP offers mainstream maintenance for ECC until the end of 2027, optional extended maintenance from 2028 to the end of 2030, and then customer-specific maintenance for anyone who does not opt in. Microsoft ends Dynamics GP product support and updates on December 31, 2029, but keeps issuing security patches until April 30, 2031.
So when someone says “our ERP goes end of life in 2027,” ask which stage they mean.
Is it safe to keep running an unsupported ERP?
Not for anything that touches the internet, payments or utilities. The Cybersecurity and Infrastructure Security Agency (CISA) lists the use of unsupported or end-of-life software as the first entry on its Bad Practices list for critical infrastructure, and calls it especially egregious in internet-facing technology. If your agency runs water, wastewater or electric service, assume that warning applies to you.
Security is only half of the risk. Public-sector ERPs carry payroll, tax and benefits logic that changes every year. Microsoft even moved the GP support end date from September 30 to December 31, 2029 so customers could finish the payroll and tax year on a supported system.
Action: list every module that faces the public, such as citizen portals, online payments and utility customer self-service. Those are the pieces you cannot leave unsupported, even for a few months.
ERP sunset dates public agencies are facing (2026 to 2031)
Published ERP end-of-support dates for Tyler Eden, SAP ECC, Microsoft Dynamics GP and NYC’s CGI-built FMS/3 start in 2026 and run into the early 2030s. Each date below comes from the vendor or from a public agency’s own records.
Swipe to see all columns →
| Product | Key date | What ends | Source |
|---|---|---|---|
| Tyler Eden | March 2027 | Tyler support for the Eden platform | City of San Rafael |
| Microsoft Dynamics GP 2016 | July 2026 | Extended support (already ended) | Microsoft Lifecycle |
| SAP ECC (Business Suite 7) | End of 2027, then end of 2030 | Mainstream maintenance, then optional extended maintenance | SAP |
| SAP transition option | 2031 to end of 2033 | Only for large, complex customers who sign a cloud migration deal | The Register |
| Microsoft Dynamics GP (all versions) | December 31, 2029, then April 30, 2031 | Product support and updates, then security patches | Microsoft |
| Oracle PeopleSoft 9.2 | Rolling, about 10 years out | Premier Support date moves forward one year at each annual review | Washington SBCTC |
| Custom or vendor-built systems (example: NYC FMS/3) | End of 2027 (extended from end of 2025) | Vendor maintenance contract | NYC Comptroller |
CentralSquare products and other Tyler legacy platforms are not in the table because we could not find a published, primary-source end-of-support date for them. No date does not mean no risk. In a 2021 staff report, the City of Fresno noted that CentralSquare’s focus had shifted to other platforms and its utility billing product had gone several years without significant new features.
If you run one of these products, ask your vendor for the written product roadmap and any end-of-support notice, and keep both in your contract file.
Tyler Eden end of life: the March 2027 sunset
San Rafael, California has used Eden since 2002 for its financial and HR recordkeeping. In an August 2024 project update, the city said Tyler will no longer support Eden beginning March 2027, and it is moving to Tyler Munis. The city kicked off that project in August 2024, about two and a half years ahead of the sunset, with target go-lives of July 1, 2025 for finance and January 1, 2026 for payroll and HR.
Munis is the natural path Tyler offers Eden customers, and it includes Utility Billing and Asset Management modules. But it is one path, not the only one. A move from Eden to Munis is still a new implementation, with data conversion, new workflows and retraining, so it deserves the same scrutiny as any other option.
SAP ECC end of support: 2027, 2030 and the 2033 fine print
SAP set the end of 2027 as the end of mainstream maintenance for ECC back in 2020. Customers can buy extended maintenance through the end of 2030 at two percentage points above their existing maintenance basis.
In January 2025, SAP said it would offer a further transition option from 2031 to the end of 2033. According to The Register, it is limited to large, complex customers who sign a cloud migration deal, and SAP says it is not an extension of the 2027 deadline.
Public agencies are already using these bridges. Australia’s Digital Transformation Agency took SAP’s option to extend ECC support through 2030 for federal agencies, covering about 35 production SAP instances that around 90 entities rely on. The stated goal was a longer transition window, not a longer life for ECC.
PeopleSoft support policy and Dynamics GP end of support
PeopleSoft is not being discontinued. The Washington State Board for Community and Technical Colleges, which runs PeopleSoft 9.2 for its ctcLink system, explains that Oracle moves the Premier Support date forward one year at each annual review, keeping a rolling window of roughly ten years. Major upgrades are no longer required either, because new features arrive as cumulative updates.
Check Oracle’s current Lifetime Support Policy for the latest date, and see our Oracle PeopleSoft page for platform-specific paths.
Dynamics GP is a different story. Microsoft has set a hard end, and it points GP customers to Dynamics 365 Business Central as the path forward. Smaller districts and special districts on GP 2016 should note that its extended support already ended in July 2026.
Action: pull your current maintenance agreement and find the exact end-of-support clause. Note the date, the version it applies to, and whether any extension is priced in.
Why your real deadline is earlier than the vendor’s date
Public agencies typically lose 12 months or more to budget adoption, procurement and council approval before a government ERP replacement can even start (KCT rule of thumb). Add the implementation itself, and a 2029 vendor date can become a 2026 decision.
New York City is a clear example. A December 2025 report from the office of the NYC Comptroller found the city’s FMS/2 budget system is no longer supported by CGI, its developer, and its FMS/3 accounting system had its maintenance extended from the end of 2025 to the end of 2027. The report recommended tying the modernization timeline to FMS/3’s support horizon and funding planning, vendor selection and change management up front.
The same report flags a second clock: nearly 40% of employees at FISA-OPA, the agency that runs the city’s financial and payroll systems, were immediately eligible to retire at the end of 2024. The citywide figure was 14%. When the people who understand the old system leave, every option gets harder.
Work backwards from the sunset date
Build your plan in reverse. The durations below are a KCT rule of thumb for a mid-size city or county replacing core finance and HR, and yours will vary with modules and staff capacity. Our ERP implementation timeline guide goes deeper on each phase.
Vendor end-of-support date.
Your hard stop.
Go-live with a buffer.
Aim for at least 3 to 6 months before the date, so the first 30 days post go-live and your first month-end close happen with the old system still supported.
Implementation.
Often 12 to 24 months for finance and HR, longer if utility billing or permitting are included.
Contract negotiation and council approval.
2 to 4 months, depending on your agenda calendar.
Selection or RFP.
6 to 9 months for a full competitive process.
Budget request.
One fiscal year before selection starts, so the money exists when you need it.
Add those up and you get roughly three to four and a half years. An agency facing a 2029 or 2030 date should be requesting funds now.
Action: put the end-of-support date, in writing, in next year’s budget request memo.
Your 4 options when your ERP reaches end of life
Every agency facing an ERP sunset date has the same four choices:
Buy extended or third-party support to buy time while you plan the move.
Upgrade in place to the vendor’s supported version of the same product.
Migrate to the vendor’s cloud successor, such as Eden to Munis or GP to Business Central.
Re-select through a competitive process that tests the whole market.
Swipe to see all columns →
| Option | Time it buys | Cost profile | Main risk | Best fit when |
|---|---|---|---|---|
| Extended or third-party support | A defined bridge, usually a few years | Ongoing premium or contract fees, no new value | Becoming permanent, or losing patches and tax updates | The sunset date lands before you can realistically go live |
| Upgrade in place | Until the new version’s own support date | Lowest disruption of the four | Carrying old processes and workarounds forward | The system still fits and a supported version exists |
| Vendor cloud successor | Long term, if the successor fits | Subscription plus a full implementation | Treating a reimplementation like an upgrade | The successor meets your requirements after benchmarking |
| Re-select | Long term | Highest upfront effort, strongest negotiating position | Starting too late for a full competitive process | You have major fit gaps or a strained vendor relationship |
Option 1: Extended or third-party ERP support
Extended support is a bridge, and every bridge needs an exit. It works when your vendor date arrives before you can realistically go live on something new.
SAP’s extended maintenance for ECC runs to 2030 at two percentage points above the existing maintenance basis. Australia’s DTA bought it explicitly to allow a longer window of transition, not to stay on ECC indefinitely.
Third-party support is the cheaper cousin, and it comes with real trade-offs. In a January 2021 staff report, the City of Fresno explained that it moved its PeopleSoft system to third-party support to save money during a downturn. That arrangement “did not allow for the latest patches, fixes and updates,” and the city ended up facing a significant upgrade or replacement anyway.
Action: only sign an extension with a funded exit plan and a target go-live date attached. If you consider third-party support, confirm in writing how it handles tax, payroll and regulatory updates.
Option 2: Upgrade in place
Upgrading in place is usually the least disruptive path, when the vendor still offers a supported version of the same product. Staff keep familiar screens, and the data model largely stays put.
PeopleSoft is the clearest public-sector example. Because Oracle now delivers features through cumulative updates rather than major upgrades, agencies on 9.2 can stay current without a forced re-platform.
The catch is that an upgrade carries your old processes forward, workarounds included. If your staff already run the month-end close out of spreadsheets, a new version will not fix that.
Action: before you sign, confirm the upgraded version’s own support horizon, and read the renewal terms closely. Our guide to avoiding hidden costs in ERP vendor contracts covers the clauses to check.
Option 3: Migrate your ERP to the vendor’s cloud successor
Migrating to the vendor’s successor product is often the path the vendor prefers, and sometimes the right one. But it is a reimplementation, not an upgrade.
San Rafael is moving from Eden to Munis. Microsoft points GP customers to Business Central. SAP ties its 2031 to 2033 transition option to signing a cloud migration deal.
In each case you still convert data, redesign processes, retrain staff and test payroll and utility billing in parallel. Budget and staff it like a new implementation.
Action: ask for migration credits and contract terms in writing, and benchmark the successor against at least one alternative. If you plan to use cooperative purchasing, check what other agencies, your state and your associations have already contracted.
Option 4: Re-select through a competitive ERP selection process
Re-selection is the only option that tests the whole market, and it needs the most lead time. It fits when your current system has major gaps or your vendor relationship has worn thin.
Fresno took this route. After an RFP that drew 14 responses, the city approved a SaaS agreement with a different vendor in January 2021 to replace both PeopleSoft and its CentralSquare utility billing system in a single agreement.
Action: start with requirements, not demos. Our step-by-step guide on how to choose an ERP system for the public sector walks through the full process.
The hardest part is rarely picking an option. It is proving to council which one fits your modules, staff and budget cycle. KCT’s ERP Consulting & Selection Advisory team builds that options analysis and, if you re-select, runs the selection with you.
KCT is not a Tyler partner or reseller and takes no referral fees from Tyler.
Upgrade or replace your ERP? How to choose the right option
Pick your option with three tests: how much time is left after budget and procurement, how well the current system fits, and how much staff capacity you have for a project. Answer those honestly and the choice usually narrows to one or two paths.
Questions to ask your vendor in writing
What are the exact end dates for each module and version we run?
What support continues after each date, and at what cost?
What is the successor product’s published roadmap?
Are migration credits or transition terms available, and until when?
In what format can we export our full history if we leave?
Questions to answer internally
Which modules are failing or frustrating staff today?
What workarounds and shadow spreadsheets exist, and who owns them?
Who could retire in the next three years? NYC’s finding that nearly 40% of its financial systems staff were eligible to retire is worth checking against your own roster.
Can your team run a project through fiscal year-end and audit season?
A simple decision rule
Use this as a starting point (KCT rule of thumb), then test it against your own requirements:
Action: start with an honest assessment of the current system. KCT’s ERP Health Check is a practical first step.
Common mistakes when an ERP end-of-support date is announced
Most end-of-life trouble comes from timing and assumptions, not technology. Watch for these:
Waiting for the vendor to push. By the time sales calls, your procurement window may be gone.
Calling a cloud migration an “upgrade.” Labeling it that way leads to underfunded conversion, testing and training.
Taking extended support without an exit date. Even Australia’s DTA framed its extension as a transition window.
Dropping to third-party support without checking update coverage. Fresno’s 2021 experience shows the risk.
Assuming the successor is the only fit. Without a benchmark, you have weak footing in negotiation and no proof for council.
Replacement is very doable when it is sequenced well. In Oxnard, California, KCT took over a stalled multi-module replacement and sequenced go-lives for Finance, then HCM, then EPL.
ERP end of life FAQ
What happens when ERP software reaches end of life?
When ERP software reaches end of life, the vendor stops fixing, patching and updating it. The system keeps running, but you lose security patches, tax table updates and a support line to call.
Is it safe to keep using an ERP after end of support?
Running an ERP after end of support is risky, especially for internet-facing modules like payments and citizen portals. CISA lists unsupported software as a bad practice for critical infrastructure, which includes water and electric utilities.
What is the difference between end of life and end of support?
End of support usually refers to one stage, such as the end of mainstream support, after which limited extended or security-only support may continue. End of life means the vendor provides no support of any kind. Ask your vendor which stage each date in your contract refers to, and get the answer in writing.
Can you get third-party support for an end-of-life ERP?
Third-party support is available for many major ERPs, and it can lower maintenance costs. The trade-off is access to vendor patches, fixes and updates. Fresno moved PeopleSoft to third-party support to save money and, by 2021, still faced a significant upgrade or replacement, so treat it as a bridge with an exit plan.
When does SAP ECC support end?
SAP ECC mainstream maintenance ends at the end of 2027, with optional extended maintenance through the end of 2030. A 2031 to 2033 transition option is limited to large, complex customers who sign a cloud migration deal.
How long does it take to replace a government ERP system?
Replacing a government ERP often takes three years or more from budget request to go-live, once budget adoption, selection, council approval and implementation are counted (KCT rule of thumb). Scope drives the range, and utility billing or permitting add time. See our ERP implementation timeline for phase-by-phase detail.
Should we upgrade our ERP or replace it?
Upgrading your ERP makes sense if the system still fits and the vendor offers a supported version. Replacing it through re-selection makes sense if you have major fit gaps, heavy workarounds or a strained vendor relationship. If time is short, bridge support covers the gap while your team runs the decision properly.
Plan your legacy ERP replacement before the sunset date
An ERP end-of-life notice is really a procurement deadline with a software label on it. The vendor sets the date, but your budget calendar, RFP process and council agenda decide how many options you still have when it arrives.
Pull your maintenance contract, find the date, and work backwards.
If you want help building the options analysis your council will ask for, KCT’s ERP Consulting & Selection Advisory team can support you at any point, from the first assessment through selection and implementation. The scope depends on your modules, departments and stakeholders, so the best place to begin is an ERP Health Check.