How to announce an acquisition to employees on both sides of the deal

Announcing an acquisition to employees is how a company tells its own staff and the acquired team about a deal, what it means for them and what happens next. It usually goes wrong in the gap between the two sides. The buyer’s staff hear it at an all-hands, the acquired team hears it from a press release or a nervous manager, and by lunchtime there are two versions of the story.

This playbook covers the announcement and the first 30 days after it, for both workforces. For the full week-by-week integration plan, see how to build an M&A communications plan.

Why do acquisition announcements go wrong?

Acquisition announcements go wrong when the two workforces hear different things at different times, and silence fills with rumor.

• Managers hear it last. Managers on the acquired side get the news with everyone else and can’t answer a single question.
• No list of who’s who. The acquired team isn’t in your HRIS or email yet, so the welcome never reaches some of them.
• One message for everyone. Your staff and the acquired team have different worries, yet both get the same all-staff email.
• The big questions go unanswered. Pay, benefits, managers and jobs. If you don’t answer them, the rumor mill will.

What does a good acquisition announcement look like?

A good acquisition announcement reaches everyone on both sides on the same day, with one story and a clear answer to “what changes for me?”

• Leaders and managers on both sides were briefed before the news broke.
• Both workforces heard it the same day, from leadership, before the press.
• Each group got a personal note on what changes for them, and what stays the same.
• Acquired staff were reached even without your email or systems.
• There’s one place to find answers, and new questions get answered quickly.
• You know, by site and legacy company, who has seen it.

How do you announce an acquisition to employees, step by step?

This sequence runs from a week before the announcement to day 30. Plan every step for both workforces separately.

Step 1 (7 days before): Build both lists

Import the acquired workforce from their HRIS or a file, and tag everyone by legacy company, site, role and language. You can’t target a message to a group you can’t find.

Step 2 (7 days before): Brief leaders on both sides, confidentially

Give every leader and manager the why, the timeline and three talking points, plus answers to the questions they’ll get first. Keep drafts and audiences restricted until the announcement is approved.

Step 3 (day 1): Announce to both workforces at once

Send a welcome from both CEOs to everyone, timed to local working hours. Follow it with a short note for each group on what changes for them. Use text or WhatsApp for acquired staff who aren’t on your email yet.

Step 4 (week 1): Open one place for answers

Publish an FAQ covering pay, benefits, managers, jobs and tools, in every language your sites speak. Our guide to creating an M&A employee FAQ lists the questions to cover. Add new answers as questions come in.

Step 5 (week 2): Explain benefits and pay, person by person

Send each person a plain guide to what changes for them and when. A general summary leaves people guessing about their own situation.

Step 6 (day 30): Ask both sides how it’s going

Send a three-question pulse to both workforces and compare results by legacy company and site. Share what you heard and what you’re changing.

What should each workforce hear?

Both workforces need the same core story, and each needs its own answer to “what does this mean for me?”

• Do tell the acquired team who you are, why you bought the company and what stays the same. Don’t assume they know your business.
• Do tell your own staff how the deal affects their teams and roles. Don’t leave them out because “nothing changes” for them.
• Do give dates, even rough ones, for pay, benefits and systems changes. Don’t say “in due course”.
• Do say what you don’t know yet and when you will. Don’t guess.

Example text to acquired staff: “Hi Rosa, today we officially joined Northfield. Your pay, manager and time off stay the same for now. Tap the link to see what changes for you, or reply to this text with any question.”

How do you know the announcement landed?

The announcement landed when everyone on both sides has seen it, the same questions stop coming back, and the day-30 pulse shows people know what’s changing.

Track reach and reads by legacy company, site and role, and chase anyone who hasn’t opened the welcome. Watch which questions people ask most, and update the FAQ when the same one keeps coming up. Then compare the day-30 pulse across both workforces to spot the site that’s struggling.

Common worries, and what to do about them

“We can’t risk a leak before the announcement.”

Brief leaders in a tight window, keep drafts and audiences restricted to the people who need them, and schedule the send only once it’s approved.

“The acquired team isn’t in our systems yet.”

Import them from their HRIS or a spreadsheet, and reach them by text, WhatsApp or a hub link until email and IT accounts merge.

“There’s bad news for some people.”

Tell the affected groups first, separately and in person where you can. Keep it out of the all-staff message, and give them a named contact for questions.

Run the announcement for both workforces from one plan

ChangeEngine runs the people side of an acquisition: leader briefings, a day-one welcome, FAQs and a 100-day integration path, sent to each workforce by legacy company, site, role and language.

You describe the deal and ChangeEngine drafts the leader briefing, CEO welcome, what-changes note and FAQ in your brand. Both workforces can come in from either HRIS or a file, and acquired staff can be reached by SMS, WhatsApp or the hub before email and IT accounts merge. Drafts stay restricted until you approve the send, you can keep separate brand kits during the transition, and pulse surveys and Engagement Analytics show reach and sentiment by legacy company and site. See the full approach on the M&A employee communications page, or start from the M&A Integration Hub template.

For IT and security: SOC 2 and ISO 27001 certified, GDPR compliant, SSO on day one and 75+ HRIS integrations.