Bought, Merged, Renamed: When Your Software Supplier Changes Hands

Software suppliers get bought, merged and quietly renamed far more often than most small UK teams notice. The first clue is rarely a press release. It is usually a privacy notice with a new company name at the bottom, a support portal that looks slightly different, or an email from an account manager you have never spoken to before.

That is not automatically a problem. Acquisitions can bring better funding, stronger security or a wider product set. But they can also reset support tiers, change who is handling your data and put a question mark over the roadmap you were sold eighteen months ago. The sensible response is not a full tender. It is a light re-procurement: a short, deliberate check that confirms what has actually changed and what you need to do about it.

Start with the contract you already signed

Before you ask the vendor anything, pull out the agreement and look for three phrases: change of control, assignment and novation.

A change-of-control clause usually says what happens if the supplier is bought or merges with another company. An assignment clause may allow the vendor to transfer the contract to a successor without your consent. A novation clause is stricter: it generally requires both parties to agree to move the contract to a new legal entity.

Many SaaS terms include a broad assignment right, which means the supplier may be able to hand your contract to a new owner without asking. That does not mean you have no say. Data protection obligations, notice periods and termination rights can still apply. Read the clause carefully, note what notice you are entitled to, and check whether the acquisition has triggered a right to object.

If the contract is silent, ask for written confirmation of which legal entity now holds it. A short email is enough. You are not trying to build a legal case; you are trying to avoid discovering at renewal that your agreement sits with a company you have never assessed.

Confirm who is the controller or processor now

If the supplier processes personal data on your behalf, you should already have a data processing agreement. Check whether the acquisition changes the entity named as processor, the sub-processor list or the countries where data is stored.

Under UK GDPR, a processor cannot simply swap in a new sub-processor without giving you the chance to object, depending on the terms you agreed. If the supplier is now part of a larger group, there may be new sub-processors, new retention rules or a different security contact. Ask for an updated DPA or a written confirmation that nothing has changed. If the supplier is a controller rather than a processor, check the privacy notice for the new entity and the contact details for data protection queries.

This is not about being difficult. It is about keeping your record of processing accurate and being able to answer a simple question from a client or auditor: who holds our data, and where?

Use Companies House to see what actually happened

Companies House is a useful reality check. Search for the old supplier name and the new one. Look at the filing history, confirmation statements, persons with significant control, appointment changes and any charges. You may see a name change, a new parent company or a merger that was never mentioned in an email.

The register will not tell you whether your support tier is safe, but it does tell you whether the story you have been given matches the public record. If the supplier says it was a small internal reorganisation but Companies House shows a new parent company with a different registered office, ask a follow-up question. Keep it factual: "We noticed the entity changed on Companies House. Can you confirm which company now employs the support team and holds our contract?"

That single question often surfaces the most useful answer you will get all month.

Ask three questions, not thirty

A short, friendly email to the account manager will do more than a sprawling questionnaire. Keep it to three questions:

1. Which legal entity now holds our contract and our data, and can you confirm that in writing?
2. What changes, if any, are planned for support tiers, service levels, roadmap commitments or renewal pricing before our next renewal date?
3. Who is our named account contact and technical escalation path for the next 90 days?

Those three cover the practical essentials: the legal relationship, the commercial risk and the human route to help. If the answers are vague, ask for a call and take notes. If they are clear, save them with the contract.

Write a one-page continuity note

You do not need a fifty-page report. A single page is enough. Note the old supplier name, the new legal entity, the contract reference, the renewal date, the support tier, the data location, the name of your account contact and any actions you have taken. Add a review date three months from now.

This note is not bureaucracy. It is the thing that stops a future colleague from asking, "Who do we actually pay for this?" and getting three different answers. It also makes the next renewal conversation much easier, because you can see at a glance whether the acquisition changed anything that matters.

Treat it as a light re-procurement, not a panic

An acquisition is a prompt to check your exit plan, confirm your backup arrangements and revisit any data residency promises that were made by the old owner. It is not a reason to rip out working software. If the product still does what you need, the support is still responsive and the data protection paperwork is in order, you can carry on with a note in the file and a calendar reminder.

But if the new owner has different pricing, a different support model or a roadmap that no longer includes the feature you rely on, you now have time to plan rather than react. That is the whole point of doing this early.

Here at SealSoft, we think the best software management is often unglamorous. A short email, a saved confirmation and a one-page note will outperform a heroic rescue mission every time. When the logo changes, keep it simple: check the contract, confirm the entity, ask three questions and write it down.