The Logo Changed Overnight: A First-Month Playbook for CMS Acquisitions

Your CMS looks exactly the same on Monday morning. Same login screen, same editor, same slightly annoying rich-text toolbar. But the company behind it has a new owner, and your account manager’s email signature has suddenly gained a parent company logo. That is the moment to pay attention — not because the sky is falling, but because acquisitions create small windows where facts are scarce and rumours fill the gap.

For UK web teams, the practical risks are rarely dramatic. They are quieter: a support portal moving to a different timezone, a renewal quote arriving from a new finance team, a roadmap webinar that quietly drops the integration you rely on, or an export tool that ends up behind a new admin permission. A 30-day continuity plan gives you something useful to do while the corporate machinery grinds on.

This is not legal advice, and it is not a reason to panic-migrate. Think of it as a risk checklist with a calendar attached.

Week one: separate facts from the group chat

The first job is to build a small, reliable fact file. Check Companies House for filings about the acquirer and the target. Look at the vendor’s status page, trust centre and any customer notice. Ask your account manager — politely and in writing — for confirmation of who now owns the contract, who handles support, and whether the entity you pay is changing.

Do not rely on a single all-staff email. Acquisitions produce plenty of cheerful statements about “exciting synergies” and very few details about invoice routing. Your finance team will want to know whether the supplier name on the purchase order still matches the bank details. Your procurement lead will want to know whether the contract has been assigned or novated. Those are boring questions, which is exactly why they matter.

Also check the data processing agreement. If personal data is moving to a new parent company or a different sub-processor, UK GDPR paperwork may need updating. You do not need to become a data protection lawyer overnight, but you do need to flag it early to whoever owns compliance.

Week one, part two: map the humans

Make a one-page contact sheet. Include support, billing, security, your customer success manager, and the person who actually answers escalations at 4pm on a Friday. Add backup contacts for each. If the acquisition means your usual contact is moving on, ask for their replacement before the out-of-office reply appears.

Then check your own side. Who in your organisation has admin access to the CMS? Who owns the vendor relationship? Who signs the renewal? Who receives security notices? Acquisitions have a way of exposing the fact that three people left the web team two years ago and their logins are still active. If that sounds familiar, deal with it now.

Week two: prove you can get your content out

Every CMS vendor says you can export your data. Fewer can prove it under pressure. Spend an afternoon testing the export path for pages, media, users, redirects and form submissions. You do not need a full migration rehearsal, but you do need evidence that the export works and that you can open the files afterwards.

If your CMS has an API, check that your credentials still work and that rate limits have not changed. If exports are manual, document the clicks. If a third-party agency holds the keys, ask them to run the export with you watching. The goal is not to leave; it is to know what leaving would involve.

While you are in there, take a fresh backup and store it somewhere your team controls. Confirm that restore instructions are not locked inside a support portal you might lose access to. This is the unglamorous work that makes acquisitions feel much less spooky.

Week three: brief the people who fund the website

Senior stakeholders do not need a 40-slide deck. They need a short, plain-English note covering four things: what has changed, what has not changed, what you are checking, and what decision — if any — they may need to make.

Be careful with language. “The vendor has been acquired” is a fact. “The platform is being retired” is a rumour unless you have it in writing. Keep the two separate. If you are a public sector team, mention any procurement or framework implications without pretending to give legal advice. If you are a charity or small business, make clear whether the renewal date creates a natural decision point.

Ask for one thing: a named person in finance or procurement who can handle contract questions. That keeps the web team out of invoice archaeology and gives the organisation a clean line of accountability.

Week four: decide what you are watching

By day 30, you should have a short watchlist rather than a vague sense of unease. Track support response times, roadmap commitments, pricing changes, security communications and data access. Put a review date in the diary for 90 days’ time. If nothing has changed, close the loop and tell people. If something has changed, you will have a paper trail and a calm starting point.

Acquisitions are not automatically bad news. Sometimes they bring investment, better support or a stronger product. But continuity is your job, not the press release’s job. Keep the CMS running, keep the evidence fresh, and keep the humans mapped. The logo can change overnight. Your ability to log in, export content and explain the situation should not.