What should dealers do when a software vendor is acquired or rebranded?

Resolve the entity and product

Document the current legal party, brand, product name, former name, ownership date and which agreements or privacy terms apply.

Ask what changes operationally

Review support contacts, hosting, subprocessors, authentication, integrations, invoicing, account teams, product development and planned migrations.

Protect decision options

Revisit renewal dates, notice periods, data exports, transition effort and credible alternatives before changes become urgent.

Separate the announcement from the changes

A press release describes intent; it does not change your contract. Ask the vendor in writing which entity now holds your agreement, whether the terms, pricing or support process change and when.

Note the effective date of anything they describe. Until you have that in writing, continue to treat the existing contract as the source of truth.

What may change operationally

Support teams, hosting, authentication, subprocessors, integrations and invoicing sometimes change after an acquisition, even when the product name stays the same. Some products are merged or retired over time.

Ask whether a product roadmap has been published and how much notice customers receive of a change. Check each of your integrations for changes to approval or fees.

Use the moment to review your options

An ownership change can be a reasonable time to check the renewal date, notice window and data-export terms, and to see how credible alternatives compare. That is not a decision to leave; it is preparation. A dealer that knows its dates and its options can respond calmly if terms change, and often gains bargaining room from asking clear questions.

Common mistakes after an acquisition

Ignoring the news until a notice arrives is the first. Assuming the old contract terms automatically carry over unchanged is the second; confirm them.

A third is missing new privacy or data-processing terms sent by email. Assign one person to track vendor changes, keep the register of contacts current and read every notice from the new owner.

Questions to send the vendor

Who is the contracting entity now and from what date? Do the terms, pricing or support process change?

Will the product be renamed, merged or retired? Which subprocessors and hosting locations change?

Are integrations affected? What is the timeline?

Ask for written answers and keep them with the contract for reference.

Keeping records straight

Update the vendor register with the new name, entity and contacts, and note the date of change. Make sure invoices, privacy terms and data-processing agreements name the correct entity. Mismatches can cause problems in an audit, a dispute or an insurance claim, so correct them while the change is fresh.