The email arrives on a Tuesday: your practice management vendor is "thrilled to announce" that it has joined a larger company. The message promises continuity, more investment, and no changes to your service. Sometimes that is true. Often the product you chose is now one of several in a portfolio, and the acquirer has plans that do not include it. This guide covers what to do in the weeks and months after an acquisition announcement.
The first week: read, do not react
Nothing needs to be decided immediately. Read the announcement for specifics: who bought whom, whether the product name survives, whether the acquirer already sells a competing product, and whether leadership is staying. Search for the acquirer's history with past acquisitions; a company that has previously merged products into a flagship and retired the rest is likely to do it again. Then pull the contract, the business associate agreement, and the most recent invoice, and put a note on the calendar for the renewal date. The goal of week one is to understand the situation, not to change vendors.
What the contract says about assignment
Most software contracts include an assignment clause that lets the vendor transfer the agreement to a successor in a merger or acquisition without the customer's consent. That means the acquirer steps into the vendor's shoes and inherits the obligations: price, term, service levels, and the BAA. Check for three things.
- Change-of-control language: Some contracts give the customer a termination right if the vendor is acquired. If yours does, note the window in which it must be exercised; it is often short.
- Price protection: A cap on renewal increases is your main defense against post-acquisition price harmonization. Confirm it survives assignment.
- Data return and transition assistance: Clauses that require the vendor to return data in a usable format and assist with migration are what you will rely on if the product is retired.
The BAA follows the contract: The acquirer becomes your business associate. Ask for written confirmation that the existing BAA remains in force, or for a new one on equivalent terms. Do not let the practice's protected health information sit with an entity that has not agreed to the BAA's obligations.
Protecting your data during the transition
Acquisitions bring data migrations, platform consolidations, and staff turnover at the vendor, each of which raises risk. Take a full export of your data now, while the original team and the original export tools are still in place, and store it securely. Confirm where data will be hosted after the transition and whether it will move to a different cloud region or provider. Ask whether the acquirer will apply its own security program to the acquired product and when its next third-party assessment will cover it. Update your risk analysis to reflect the new vendor relationship. If the product is one that handles protected health information, these questions are not optional, and a vendor that cannot answer them is signaling how the transition will go.
Signals to watch over the next year
| Signal | What it usually means |
|---|---|
| Product roadmap goes quiet or merges with another product's | The acquired product is in maintenance mode |
| Support moves to a shared queue with longer response times | Cost reduction is under way; service levels may erode |
| Account manager changes twice in six months | Turnover at the vendor; institutional knowledge of your setup is leaving |
| "Migration path" or "upgrade" offers to the acquirer's flagship | End-of-life is being planned for your product |
| Renewal quote arrives with new line items or a new pricing model | Price harmonization to the acquirer's structure |
| Integration partners announce they are deprecating the connection | The ecosystem is moving on |
None of these alone means you must leave. Two or three together, especially a formal end-of-life notice, mean you should be planning.
Pricing and renewal tactics
Acquirers frequently raise prices at the first renewal, sometimes substantially, on the theory that switching costs will keep most customers in place. Prepare early. Start the renewal conversation several months before the term ends, ask for the renewal quote in writing, and compare it against the contract's cap. If the acquirer proposes moving you to its flagship product, ask for migration at no charge, a price hold for a defined period, and a written data return commitment in case the migration fails. A practice that has already requested demos from two alternatives negotiates from a very different position than one that has not.
Deciding whether to stay
Many acquisitions turn out fine: the product gets more investment, support improves, and the price stays reasonable. Give it a year unless the signals are unmistakable. Use that year to document your requirements, since the acquisition is a natural moment to ask whether the product still fits, and to keep your export current. If an end-of-life notice arrives, treat the acquirer's migration offer as one option among several, not the default; the effort of moving to the flagship is often comparable to the effort of moving to a competitor, and the competitor may be a better fit. Whatever you decide, decide it on your timeline, with your data in hand, and with the contract terms you negotiated still in force.
Common questions
Can a vendor transfer our contract to the acquiring company without asking us?
Usually yes, if the contract contains a standard assignment clause permitting transfer in a merger or acquisition. The acquirer then inherits all obligations, including pricing, service levels, and the business associate agreement. Check whether your contract gives you a termination right on change of control.
Do we need a new business associate agreement after an acquisition?
If the contract and BAA were assigned, the existing BAA binds the acquirer. Request written confirmation. If the acquirer proposes a new BAA, review it carefully for changes to breach notification timelines, subcontractor terms, or data return obligations.
How soon after an acquisition do prices typically change?
Most acquirers honor the current term and revisit pricing at renewal. Increases at the first renewal are common. Start renewal discussions several months early and rely on any price cap in the existing contract.
Should we take a data export right away?
Yes. Export your complete data while the original tools and staff are still in place, verify that the export opens and is complete, and store it securely. It protects you against migration problems and strengthens your position in any later negotiation.