Guide · Comp policy

Harmonizing pay after an acquisition

Harmonize the levels first. Bring pay together over cycles, with nobody cut.

Short answer: After an acquisition, map both workforces to one level structure by job content before touching anyone's pay. Then sort the differences into kinds and close them over a set number of cycles. Do not cut pay, do not match titles and do not leave two structures running indefinitely. People will compare from day one, so tell them what will happen and when.

Two senior engineers, two structures

Picture a 230-person company in Billings that makes telematics software for farm equipment. It has just acquired a 60-person data analytics startup in Denver. The deal closed in September. By October, the questions have started.

The acquirer has six levels and published ranges. The startup had no levels and salaries set one at a time by its founders. Its "senior engineers" earn between $128,000 and $171,000. The acquirer's senior engineers, a level with a narrower scope, earn between $135,000 and $150,000. Two of the startup's people have "head of" titles and run teams of two. The acquirer's equivalent title runs teams of twelve.

The integration lead proposes moving everyone onto the acquirer's ranges on 1 January, matched by title. Finance points out that six startup engineers would be well above the top of their new range and ten would be below the bottom. The startup's founders, now on retention agreements, ask that their people be left alone for two years. Meanwhile an acquirer engineer has found out what a startup engineer with the same title earns and wants to know why it is $20,000 more.

This is a composite of a common situation at companies this size, not a client. The details and figures are illustrative.

Why harmonizing pay is hard

Harmonization sets two good goals against each other. The first is fairness across the combined company. Once two workforces share an employer, people doing similar work will compare their pay and expect a single, explainable basis. The second is continuity. The acquired people were hired on their own terms, often by founders they trusted. The deal's value depends on many of them staying. Changing their pay or titles too fast is the quickest way to lose them.

The comparison starts immediately. People already doubt their own pay. A compensation data provider's analysis of more than 327,000 salary survey responses found that 63% of people paid at market believe they are paid below it [1]. In a merger, every acquired employee suddenly has a new group of colleagues to compare against and every existing employee has a new group too.

The law adds constraints that depend on how the deal was done. In a share purchase, the employing company usually stays the same and contracts carry on unchanged. Where a business or part of one is transferred to a new employer in the EU, the employees' contracts and rights transfer with it, the new employer must keep collectively agreed terms for at least a year in most cases and the transfer itself is not a lawful reason for dismissal [2]. In the United States, an employer that finds an unlawful pay difference between men and women doing equal work may not fix it by reducing anyone's pay [3].

And once the two workforces are one, equal pay comparisons apply across both. Under the EU pay transparency directive, the comparison of pay for equal work or work of equal value extends to situations where pay is set by a single source, such as one employer [4]. Under US federal guidance, job content, not titles or classifications, decides whether jobs are equal [5]. Legacy titles from two companies are not a defense for different pay for the same work.

The acquired company's pay also carries its own history. Salaries set one at a time by founders reflect who negotiated, when the money was available and what the founders promised. Some of those numbers will look generous next to the acquirer's ranges and some will look low. Neither tells you much about the job. Treating the startup's salaries as data about the market, rather than as a set of individual deals, is one of the most common errors in an integration.

Two terms will help. Harmonization is the process of moving two pay structures to one. Mapping is the step of placing each job from the acquired company into the acquirer's level structure, or a new one, by what the job involves.

Five traps in post-acquisition pay

"Match the titles"

What it looks like: Each acquired employee is placed in the acquirer's structure at the level whose title matches theirs.

Why smart teams fall into it: It is fast, it seems neutral and it lets people keep the title they had.

What it costs: Titles at a startup and titles at a larger company describe different jobs. A "head of" at 60 people may lead two people. A "senior engineer" may have the scope of a mid-level role or a principal one. Matching by title puts people at the wrong level, which puts them in the wrong range, which produces either overpayment that looks unfair to existing staff or underpayment that drives the acquired people out. Map jobs by content: Scope, complexity, accountability and the size of what they own. Where an acquired job has no equivalent, it may be a sign the acquirer's structure needs a new job or level, not that the person should be forced into the nearest box. Titles follow once levels are set. Our guide on mapping job titles to levels covers how to do that without a revolt.

"Everyone on our bands on day one"

What it looks like: On a fixed date soon after closing, every acquired employee is moved into the acquirer's ranges. People above the new maximum have their pay frozen or reduced. People below the minimum are raised at once.

Why smart teams fall into it: One date feels clean and decisive. It ends the comparisons quickly.

What it costs: Raising everyone below the minimum at once can cost more than the integration budget allows. Freezing or cutting people above the maximum hits the acquired company's most valuable people at the moment they are deciding whether to stay. In the EU, where a business was transferred to a new employer, changes to terms because of the transfer can be restricted [2]. In the US, any pay difference between men and women doing equal work cannot be corrected by cutting pay [3]. The day-one approach also locks in the mapping before anyone has had time to check it. Our guide on pay above the band maximum covers the honest options for people above the range.

"Leave both structures running"

What it looks like: To protect retention, the acquired company keeps its own pay practices indefinitely. Two structures run side by side under one employer.

Why smart teams fall into it: It avoids every difficult conversation and keeps the deal's key people happy in the short term.

What it costs: Two classes of employee emerge. People in the same jobs are paid on different bases, hired through different processes and reviewed under different rules. The differences become visible as teams merge. The explanation that "they came from the other company" weakens every year. Equal pay comparisons do not stop at the legacy boundary once one employer sets pay for both groups [4] [5]. A temporary period of two structures is often wise. An open-ended one is a liability that grows. The longer it runs, the more hires, promotions and raises are made under two sets of rules. The eventual harmonization gets more expensive with each of them.

"Retention bonuses solve it"

What it looks like: Key acquired people get retention bonuses payable after a year or two. Base pay questions are left for later.

Why smart teams fall into it: Retention bonuses are standard in deals and they work for their purpose: Keeping key people through the transition.

What it costs: A retention bonus delays the base pay question. It does not answer it. When the bonus pays out, the person compares their base to colleagues' for the first time without a cushion. If the gap was never addressed, the end of the retention period is when they leave. Retention bonuses also usually go to a small group, so the rest of the acquired workforce sees the founders protected and themselves left to wait. Use retention awards for retention and a harmonization plan for pay. They are different problems.

"Harmonize quietly"

What it looks like: Pay adjustments are made person by person over time without telling either workforce what the plan is.

Why smart teams fall into it: Announcing a harmonization plan invites questions and the company wants to avoid making promises it might not keep.

What it costs: Both workforces are already comparing. Without a plan, each adjustment looks like a favor and each non-adjustment looks like neglect. Research on reactions to pay decisions found that the fairness of the process shapes trust in the supervisor and commitment to the organization, separately from how people feel about the amount [6]. A merger is the moment when that trust is most fragile. Saying what will happen, in what order and by when costs little and protects a great deal.

What sound pay harmonization looks like

Sound harmonization does not make everyone's pay identical on day one. It establishes one structure everyone is measured against and closes the differences at a pace the company can afford and explain. At 50 to 500 people, the integrations that hold up share these qualities.

Levels come first. Both workforces are mapped to one level structure by job content before any pay changes. Where the acquirer's structure does not fit the new jobs, it is adjusted rather than forced.

Differences are sorted into kinds. People above the new range, below it, inside it but out of line with peers and those with special terms from the deal. Each kind gets one rule, applied to everyone in it.

Nobody's pay is cut. People above the range keep their pay. Their future increases follow a written rule. They hear that rule early, well before they start to wonder whether their own pay is at risk.

Gaps close on a schedule. The company decides how many cycles it will take to bring people below the range up and says so. The cost is in the integration budget, not taken from the merit pool.

The legal form of the deal is respected. Where the deal moved employees to a new employer in the EU, the transfer protections are followed. Changes are timed and justified accordingly [2].

Both workforces are checked together. The combined pay data is reviewed by gender and job family, across the legacy line, before and after harmonization.

Retention awards and pay are separate. Retention awards keep key people through the transition. The harmonization plan answers the pay question for everyone.

Benefits and variable pay have their own plan. Bonus schemes, equity awards and benefits often differ far more than salaries. They are harmonized on their own timetable, with the same openness.

New decisions use the new structure. From closing, every hire, promotion and raise in either workforce is made against the combined structure, even while legacy pay is still being brought into line. That stops the gap from growing while the plan closes it.

People hear the plan early. Within the first months, both workforces hear how levels will be set, what will happen to pay and when. Individuals then hear their own position from their manager.

The calls only you can make

Whose structure wins. The acquirer's, the acquired company's or a new one. The acquirer's is usual. A new one can be right when the acquired company is large or its jobs are different.

The pace of closing gaps. One cycle, two or three. Faster is fairer and more expensive. Slower is cheaper and keeps people waiting.

What happens to people above range. Lump sums instead of base increases, slower base growth or a defined period of protection. Each has a cost in money or trust.

How long two structures run. A short, stated transition period, or immediate integration. An open-ended period is the one answer to avoid.

Who leads the work. The acquirer's people team, a joint team with someone from the acquired company or an outside party. A joint team is slower and far more likely to be trusted by the acquired workforce.

What to say and when. How much of the plan is shared, with whom and at what point after closing. Earlier is almost always better, because silence is filled by rumor within weeks.

The data and the law

  • What people believe. A compensation data provider's analysis of 327,583 salary survey responses from 2021 to 2025 found that 63% of people paid at market and 47% of those paid above market believe they are paid below market [1].
  • European Union, transfers of undertakings. Where a business or part of one is transferred, the transferor's rights and obligations under employment contracts transfer to the transferee. The transferee must keep terms agreed in collective agreements until they end or are replaced. Member states may limit that to no less than one year. The transfer itself is not grounds for dismissal, though dismissals for economic, technical or organizational reasons are not prevented [2].
  • United States, equal pay. An employer paying an unlawful difference between men and women for equal work may not reduce anyone's wage rate to comply [3]. Job content, not job titles or classifications, determines whether jobs are equal [5].
  • European Union, pay transparency. Pay structures must allow work to be compared on objective, gender-neutral criteria (Article 4). The comparison of pay for equal work or work of equal value covers situations where pay conditions come from a single source (Article 19) [4].
  • Process and trust. A study of 217 employees' reactions to pay raise decisions found that the fairness of the process explained more of their trust in their supervisor and commitment to the organization than the amount did [6]. This study is older than the others here. We cite it because its finding is the basis of most later research on pay fairness.

This is general information, not legal advice. Rules and their national versions differ. Check the rules where you employ people.

Our view

We think post-acquisition pay goes best when the company resists two opposite temptations: Fixing everything on day one and fixing nothing for years. The first loses the people the deal was meant to buy. The second builds two classes of employee under one roof.

So we would map both workforces to one level structure by job content, sort the differences into a few kinds with one rule each, close gaps over a stated number of cycles from the integration budget, cut nobody and tell both workforces the plan early. Retention awards would do their own job and not stand in for a pay plan. Done that way, harmonization becomes the first evidence the acquired people see that the new company is fair.

Sources

  1. Payscale, 2025 Fair Pay Impact Report (327,583 salary survey responses, January 2021 to January 2025), p. 3, checked 2026-10-29
  2. Council Directive 2001/23/EC on safeguarding employees' rights in the event of transfers of undertakings, Articles 3 and 4 (EUR-Lex), checked 2026-10-30
  3. 29 U.S.C. 206(d)(1), Equal Pay Act (Cornell Legal Information Institute), checked 2026-10-30
  4. Directive (EU) 2023/970 on pay transparency, Articles 4 and 19 (EUR-Lex), checked 2026-10-28
  5. US EEOC, Compliance Manual Section 10: Compensation Discrimination, 10-IV.E.2 (comparison of work), checked 2026-10-30
  6. Folger and Konovsky, Effects of procedural and distributive justice on reactions to pay raise decisions, Academy of Management Journal 32(1), 1989, pp. 115 to 130 (abstract), checked 2026-10-29

Cleaning up founder-set salaries

Founder-set pay is inconsistent, not wrong one by one. Five traps in the cleanup and why the system has to come before individual fixes.

Job titles to levels without a revolt

Title revolts start with a public reveal or one negotiated exception. Five ways title mapping goes wrong and what a fair mapping looks like.

Paid above the band maximum: Now what?

When pay sits above the band maximum, the answer depends on why. Five ways companies mishandle it and four honest options that hold up.

See Resources for every guide and the self-check.