Your ERP Vendor Is Being Acquired: What a City Should Do in 2026
Facing an ERP vendor acquisition? What cities should do in 2026: review assignment and price cap clauses, get roadmap terms in writing, know when to reassess.
On this page
- Key takeaways
- Why ERP vendor acquisition keeps happening in govtech in 2026
- What actually changes for your city (and what doesn’t)
- What to do when your ERP vendor is acquired: a 7-step playbook
- The contract clauses to review first (ERP contract review checklist)
- Questions to ask the new owner, in writing
- What’s different for a city than for a private company
- When to replace your ERP system after an acquisition, and when to stay
- Who should own the response
- ERP vendor acquisition FAQ
- Conclusion: an acquisition is a contract event, not a crisis
When your ERP vendor is acquired, your contract almost always stays in force and the software keeps running the next morning. What changes is who sets price, roadmap and support. So the answer to what to do when your ERP vendor is acquired is simple: read your assignment, price and termination clauses now, get the new owner’s commitments in writing, and set clear triggers for re-evaluating.
The press release is rarely the moment that matters in an ERP vendor acquisition. The moments that matter come later: the first renewal under the new owner, and the day a version you depend on gets a sunset date.
The City of Hutchins, Texas is a good example. Its financial system changed hands in 2019, and the real decision point arrived in 2025. Below you’ll get a seven-step playbook, a clause checklist, a question list for the new owner and a stay, watch or re-evaluate table.
Key takeaways
Your contract usually transfers to the new owner. The clauses decide what that owner can change, and when.
Five clause families matter most: assignment, price protection, version and roadmap support, termination and exit, and data export or escrow.
Get the acquirer’s commitments in writing, ideally as a contract amendment, not a FAQ page or a webinar slide.
The real decision often comes years later at a version sunset, as Hutchins and Great Bend, Kansas both found.
Re-evaluate on triggers, not headlines. An ownership change alone isn’t a reason to replace a system that works.
Why ERP vendor acquisition keeps happening in govtech in 2026
Govtech acquisitions keep reshaping local government ERP, through both private equity investment and strategic buyers. Here’s a sample of recent public-sector software deals, taken straight from each announcement.
Swipe to see all columns →
| Date | Deal | Type | What the announcement said |
|---|---|---|---|
| Feb 2024 | Cox Enterprises and OpenGov | Majority investment | Valued OpenGov at $1.8 billion; nearly 1,900 customers in all 50 states (Cox Enterprises) |
| Apr 2024 | TA and Edmunds GovTech | Growth investment | More than 2,100 municipalities and authorities in more than 20 states; LLR Partners remains an investor (TA) |
| Jan 2025 | Tyler Technologies and MyGov | Strategic acquisition | About 150 community development software clients, mostly in Texas, gain access to other Tyler products and ERP integrations (Government Fleet) |
| Feb 2025 | BS&A Software and Boyce Systems | Strategic acquisition | Over 1,200 Boyce customers; Keystone users will gain access to BS&A’s cloud platform “over the coming months” (BS&A release via Business Wire) |
| May 2026 | TA and Govineer Solutions | Growth investment | Govineer, which previously acquired Caselle and Black Mountain Software, serves more than 2,300 local governments in 43 states (TA) |
Older deals show the same pattern. In September 2018, Superion, TriTech, Zuercher and Aptean’s public sector and healthcare business merged to form CentralSquare. In January 2020, Accela sold Springbrook Software to Accel-KKR.
Divestitures count too: your product can be sold out of a larger vendor, not just into one.
None of this is bad news by default. OpenGov’s CEO said the investment would help the company “accelerate product development,” and new capital often does exactly that.
Action: Check who owns your vendor today, using its website’s “About” page or latest press release, and add a dated note to your vendor file.
What actually changes for your city (and what doesn’t)
On day one, almost nothing changes. Over the following years, pricing, roadmap, support and version life can all shift, within whatever limits your contract sets.
What usually stays the same at first
The software, the support desk, your contract terms and usually your account team.
What can change over time
Pricing and packaging at renewal, including new bundles or product names.
Roadmap and version support, especially for on-premise or older versions.
The support model, such as a new portal, tiers or offshore hours.
The partner channel, meaning who’s allowed to implement or support the product.
Cross-sell pressure toward the new owner’s other products.
A useful way to frame this comes from TechTarget’s September 2026 analysis of Progress Software’s purchase of Domo’s AI and data platform business. It lists six areas an ownership change should put back under review:
Two city examples of the long tail
Hutchins shows how long the gap can be. According to a November 2025 city council staff report, the city’s on-premise STW financial system “was acquired by OpenGov during 2019.” OpenGov later told the city it would discontinue support for the version in use, so Hutchins needed to either upgrade to OpenGov or change providers.
The vendor offered a path forward. The city chose to test the market, evaluated proposals and recommended Oracle NetSuite through a Texas DIR cooperative contract. Conversion was estimated at $312,186, with annual costs estimated at $58,203.84, per the staff report.
Great Bend shows a related pattern: product-line consolidation. The Great Bend Post reported in February 2025 that the city was told its Tyler finance software, covering general ledger, payroll, AP and utility billing, would reach “end of life” and be retired by the end of 2026. Staff sat through demos from three companies, and council approved an Edmunds GovTech quote of $98,778: a $59,715 one-time conversion fee plus about $39,063 in annual fees, as reported.
The article doesn’t tie Great Bend’s case to an acquisition, but the decision is the same: a version sunset, years after signing.
Action: Write a short note on each of the six areas for your ERP today. When something changes later, you’ll have a baseline to measure against.
What to do when your ERP vendor is acquired: a 7-step playbook
Seven steps cover it, and none of them commits you to replacing anything.
Confirm the deal type and who your contracting counterparty will be.
Pull the full contract set, including documents incorporated by URL.
Review the five clause families that decide what can change.
Send the new owner a written question list within 30 to 60 days.
Ask for key commitments as a contract amendment.
Brief council and the finance committee with a short factual memo.
Set re-evaluation triggers and calendar every renewal and notice date.
Step 1: Confirm the deal type and your counterparty
Deal type matters. A majority investment, like Cox and OpenGov, usually leaves the same company as your counterparty. An asset purchase, like Progress buying Domo’s platform business, can move your contract to a different legal entity.
Owner and deliverable: the finance director, with a one-paragraph summary of the deal and the name of the entity that now holds your contract.
Step 2: Pull the full contract set
Gather the master agreement, order forms, amendments, the SOW, license or SaaS terms and the support policy. Watch for policies incorporated by URL, because a vendor can often update those without a signature.
Owner and deliverable: purchasing, with a single folder and an index of every document and its effective date.
Step 3: Review the clauses that matter
Owner and deliverable: the city attorney and purchasing lead, with the completed clause table in the next section.
Step 4: Send a written question list early
Send your questions within the first 30 to 60 days (KCT rule of thumb), while the new owner is working hardest to keep customers calm.
Owner and deliverable: the finance director, with a dated letter and a requested response date.
Step 5: Turn promises into amendments
Webinars and FAQ pages rarely bind anyone. Ask for key commitments, such as a support date for your version, in a signed amendment.
Owner and deliverable: the city attorney, with a short draft amendment covering the two or three commitments you care about most.
Step 6: Brief council
Owner and deliverable: the city manager’s office, with a factual memo and no premature recommendation to replace.
Step 7: Set triggers and calendar dates
Calendar the renewal date, the non-renewal notice deadline and any end-of-support date. Then write down the signals that would make you re-evaluate.
Owner and deliverable: IT and finance jointly, with calendar entries and a one-page trigger list.
The contract clauses to review first (ERP contract review checklist)
Five clause families decide what a new owner can change: assignment, price protection, version and roadmap support, termination and exit, and data export or escrow. Read them together, because they work as a set.
Swipe to see all columns →
| Clause | What to look for | Why it matters after an acquisition | What to ask for |
|---|---|---|---|
| Assignment and change of control | Who can assign, with or without consent | Decides whether your contract can move to a new entity and whether its obligations move intact | Mutual consent, or written confirmation that all obligations transfer |
| Price caps and escalators | Cap level, what it applies to, whether it survives repackaging | New owners often revisit pricing at renewal | Confirmation the cap applies to successor products |
| Version and roadmap support | Minimum support periods, end-of-support notice | Version sunsets are where cities feel an acquisition most | A dated support commitment and a notice period |
| Termination and transition | Non-appropriation, convenience exit, auto-renewal, transition help | Keeps your exit options open if things change | Transition services and no evergreen renewal |
| Data export and escrow | Export format, timing, escrow triggers | Protects your records if support ends | Usable export plus transition assistance |
Assignment and change of control
The assignment clause says what happens when a supplier sells to, merges with or transfers the agreement to another company. Virginia’s state IT agency says each party should have equal rights to assign, or not assign, the agreement.
Its BUY IT Manual suggests this wording: “This agreement may not be assigned or otherwise transferred by either party, in whole or in part, without prior written consent by the other party.” That’s Virginia guidance, not law that binds cities elsewhere, but it’s a solid model.
Many vendor contracts allow assignment to a successor by merger without consent. What matters is whether every obligation, from service levels to price caps, travels with the contract. Have your city attorney confirm your wording.
Price caps and renewal escalators
A renewal cap only protects you if it still applies after the deal. Check whether it covers successor or renamed products, because a forced move to a new platform with a new SKU can look like a brand-new purchase at a brand-new price.
We cover caps on net versus list price, true-ups and auto-renewal traps in detail in our guide to avoiding hidden costs in an ERP vendor contract. Use that method here; the only new question is whether the cap survives a change of product.
Product roadmap and version support commitments
Look for three things: a minimum support period for the version you run, a notice period before end of support, and who pays for migration if the vendor initiates the platform change.
Notice matters because you need runway to budget, procure and convert. Hutchins estimated 12 to 18 months for conversion, per the staff report.
Termination, non-appropriation and transition assistance
The VITA BUY IT Manual advises negotiating transition services in case the supplier is acquired by another company, goes out of business or the contract ends early. It also warns about evergreen clauses that renew the term automatically.
Also confirm your non-appropriation language survives any assignment.
Data export and source code escrow
Virginia’s February 2025 escrow guidance names acquisition directly. It lists a supplier being purchased by another entity that “fails to provide ongoing support” as a situation where you may need the source code. The same guidance adds that a supplier’s reputation, size or viability “does not offer any assurance.”
Escrow has limits. VITA notes it doesn’t apply to off-the-shelf, packaged software purchases. In our experience it also does little for multi-tenant SaaS, where the practical equivalent is a right to export all your data in a usable format, plus transition assistance (KCT rule of thumb).
An acquisition is often the first time anyone rereads the assignment clause since signing. KCT’s ERP Consulting & Selection Advisory team can review the agreement with you, build the question list for the new owner and run a market check if one is warranted. KCT is not a Tyler partner or reseller and takes no referral fees from Tyler.
Questions to ask the new owner, in writing
Cover roadmap, support, pricing, partners, security and integrations for your exact product and version, and set a response date.
Product and roadmap
What is the support commitment, with a date, for the version we run today?
Is our product being merged into another platform? If so, when, and at whose cost?
Support and people
Will our support desk, hours and service levels change? When?
Will the list of certified implementation and support partners change?
Commercial terms
Will our current price cap apply at the next renewal and to any successor product?
Are any modules being repackaged, renamed or moved into new bundles?
Will you confirm these answers in a signed amendment?
Security and data
Will hosting location, security certifications or data ownership terms change?
What integrations with your other products are planned, and are any required?
What is the export process and format for our full data set?
Your job is to turn announcements into dated commitments. The 2018 CentralSquare launch release said the new company “will support all current products from each business.” The sensible follow-up is always the same: for how long, and for which version?
Action: Send the questions on city letterhead, request a written response by a set date and file the reply with the contract.
What’s different for a city than for a private company
Cities answer to council, budgets and procurement law. Your response needs a clean paper trail and a budget horizon that a private company’s IT team doesn’t have to think about.
Council and finance committee briefing
Keep the memo to one page: deal facts, contract position, main risks, next key dates and current staff actions. Hold any recommendation to replace until you have the vendor’s written answers.
Budget and appropriations
Model a possible forced migration in your multi-year forecast. Hutchins staff identified Series 2025A certificates of obligation as the funding source, according to its staff report. Funding like that takes time to line up.
Procurement options if you do need to move
You can run a competitive RFP or use a cooperative contract. Hutchins staff recommended buying through the Texas DIR cooperative program. Check what other agencies, your state and your associations have in place, and still review the pricing and terms yourself, because a cooperative vehicle doesn’t do that work for you.
Public records
Assume your vendor correspondence is a public record. Keep it factual, polite and specific.
When to replace your ERP system after an acquisition, and when to stay
Most acquisitions call for watching, not replacing. The table below is a KCT rule of thumb for sorting signals.
Swipe to see all columns →
| Signal | Stay | Watch | Re-evaluate |
|---|---|---|---|
| Roadmap for your version | Written and dated | Verbal only | Refused or vague after follow-up |
| End-of-support notice | None | Announced beyond your planning horizon | Inside your budget and procurement runway |
| Price at renewal | Within cap | New bundle at similar total cost | Increase beyond cap or forced repackaging |
| Support performance | Meeting SLA | Slipping occasionally | Repeated SLA misses, documented |
| People and partners | Stable | Some turnover | Key staff and your implementer gone |
| Platform change | None planned | Optional, with migration help | Forced, with new license or migration fees |
| Contract amendments | Signed | Under discussion | Declined |
If you re-evaluate, keep it fair
Treat the incumbent’s new platform as one serious option in a fair comparison. Hutchins and Great Bend both compared alternatives before deciding. Our guide on how to shortlist ERP vendors for a city or county walks through a structured process.
If support slips before you decide
Document every miss against the contract’s service levels, with dates. If problems repeat, follow the escalation steps in our guide on what to do when your government ERP vendor isn’t delivering.
Action: Run an ERP Health Check now so you have a baseline of system health and support quality to compare against later.
Who should own the response
The finance director should own it, with the city attorney, purchasing, IT and key department heads on the team. One owner keeps the letters and council memo consistent.
An independent advisor helps most with contract review, the new-owner question list and an unbiased market check. KCT works as both an advisor and an implementer, so the same team can stay with you if the answer turns out to be a move. For the City of Oxnard, KCT has managed the vendor relationship on a multi-module ERP program continuously since 2021, as described in the Oxnard case study.
How much outside help you need depends on your modules, departments and stakeholders. Start with an assessment; KCT can support you at any point.
ERP vendor acquisition FAQ
What happens to your contract when a software vendor is acquired?
Your contract usually stays in force and transfers to the new owner, either because the same company remains your counterparty or because the agreement is assigned to a successor. The terms you signed still apply until renewal or a signed amendment.
Can a software vendor assign a contract to a new owner without consent?
A software vendor often can assign a contract without consent if the agreement allows assignment to a successor by merger or sale, so read your exact wording. Virginia’s BUY IT Manual recommends equal assignment rights for both parties and suggests requiring the other party’s prior written consent.
Will ERP maintenance prices go up after an acquisition?
Maintenance prices don’t change automatically, because your current term and cap still apply. Changes usually show up at renewal, or when products are repackaged or moved to a new platform. Check whether your price cap covers successor products, and ask the new owner to confirm renewal pricing in writing.
What is a change of control clause in a software contract?
A change of control clause sets out what happens when ownership of a party changes, for example through a merger or majority sale. It may require notice, allow assignment, or give the other party rights such as consent or termination. Not every contract includes one, so confirm what yours says.
Should we replace our ERP if the vendor is acquired?
An ERP vendor acquisition alone isn’t a reason to replace a system that works. Re-evaluate when real triggers appear, such as an end-of-support notice inside your runway or a forced platform move.
What is source code escrow and does it help in an acquisition?
Source code escrow places the software’s code with a third party, released to you if specific events occur. Virginia’s escrow guidance names acquisition followed by a failure to support as a trigger. For multi-tenant SaaS, data export and transition terms matter more (KCT rule of thumb).
How long do acquired software products stay supported?
There’s no universal number: support lasts as long as your contract and the vendor’s notices say, sometimes years past the deal. Ask the new owner for a dated commitment for your version.
Conclusion: an acquisition is a contract event, not a crisis
Ownership changes are normal in govtech. Your protection comes from the clauses you already have and the dated commitments you ask for next. Treat the announcement as the start of a calm 90-day review, and calendar the real decision points well before a sunset forces the issue.
A good first step is an ERP Health Check to baseline where you stand. If you want help reading the contract or testing the market, KCT’s ERP Consulting & Selection Advisory team can start whenever you’re ready. Contact KCT to talk it through.