Every acquired company has one. The person who built the quoting spreadsheet nobody else understands. The one who knows which customer needs a call before the invoice goes out. The one who says the new system will never work here, usually while quietly making sure it cannot.
You cannot fire them, because the business would stop. You cannot ignore them, because the integration would stall. The answer is to handle them deliberately, and not to wait for the day they quit or refuse a request. Begin with employee retention after acquisition for the people side.
Understand the resistance before you respond
Resistance almost always has a reason. The person may fear that sharing what they know makes them replaceable. They may have watched a past change go badly. They may be right that your approach will break something. Or they may be losing status they spent years earning.
Ask them directly what worries them. Listen for the facts inside the complaint, since they often hold real information about how the business works. Then separate the part that is a legitimate operational point from the part that is fear.
Make their knowledge less fragile
The real risk is not the attitude. It is that the knowledge lives in one head. Start capturing it now, in a way that respects the person: a joint project to write down how things work, with their name on it and a role as the owner of the process.
Pair them with someone who can learn. Frame it as building the team around them, not replacing them. Put dates on the knowledge transfer, and tie some form of recognition or pay to it. A person who is paid to teach has a reason to do it.
Give them a real place in the change
The most effective step is to involve them in design. Ask them to test the new system, to find what it misses, and to propose fixes. People resist what is done to them, and defend what they built. Make them a builder of the new way.
Be honest about what is not negotiable. Some decisions have been made. Explain which ones and why, and then give real choice on the parts that remain. A person with a real say on the details can accept a fixed direction.
Set limits
Respect does not mean accepting sabotage. If someone repeatedly blocks a change after being heard, address the behavior directly and in writing. Be clear about what is expected and what happens if it does not change.
Build the contingency quietly in the meantime. Cross train. Document. Identify who else could do the work. Not to push them out, but so that the business is not held hostage by any one person. The same logic applies to the seller's most trusted deputy; see the seller's loyal number two.
Look for the pattern
A single person who resists is often a symptom. If the whole team is lagging behind, there is something about the change itself. Look at the pace, the message, and the support. Look at the pattern, not the person; see why one issue is never just one issue. For the general approach to leading people through change, see leading the change after an acquisition. The option I trust least is waiting for the indispensable person to decide, on their own, to share what they know.
Sequenced list: handle a key employee who resists
Follow in order. Each step is a conversation or a deliverable with an owner.
- Hold a private, listening conversation: what worries them, what would they change. Owner: the general manager.
- Write down what only this person knows, as a list of tasks and decisions. Owner: the integration lead, with the employee.
- Name a successor or backup for each item and set dates for knowledge transfer. Owner: the function lead.
- Give the person a defined role in designing the change, with a real decision to make. Owner: the general manager.
- Tie recognition or pay to the knowledge transfer and the deliverables. Owner: HR, with the president.
- State the limits in a second conversation, in writing: what is decided and what is expected. Owner: the president.
- Review monthly. If behavior has not changed, escalate with counsel and HR. Owner: HR.
Protect the business while you work on the person
While you build trust, put controls in place that do not depend on goodwill. Access to systems, approval limits, and shared logins should be set up so that no single person controls the only copy of anything important. Do it as a general policy and explain it that way, so it does not read as an accusation.
Review the person's workload as well. People who know everything are usually doing the work of two or three. Part of the resistance is exhaustion. Taking tasks off their plate, and giving them room to teach, often does more to open them up than any speech about the vision.
What success looks like
The best outcome is a person who still holds a central place and no longer holds the business hostage. Their knowledge is in the files. They are respected for it. Others can step in.
Keep the person, because the customers trust them. Then reduce the risk that any one of them is irreplaceable.
Get the 100 day integration tracker
The tracker puts an owner, a date, and a status on every integration task from pre-close to day 100, so decisions like this one get made on purpose and followed up.
One email with the download, and occasional Building Results notes. Opt out any time.
Questions
How do you handle a key employee who resists the integration?
Start by listening, since resistance usually has a reason, often fear of being replaced or a real operational concern. Capture their knowledge together in a way that respects them, involve them in designing the change, and tie recognition or pay to the knowledge transfer. If the behavior continues after you set limits in writing, involve HR and counsel.
Should I replace someone who resists?
Not as a first step. You need their knowledge, and you need to know whether the resistance is fear or a valid point. Build the backup in parallel.
How do I stop one person holding the business hostage?
Document what only they know, cross train others, and make sure no key process depends on one person. Do it openly and respectfully.
What if they threaten to quit?
Take it seriously and respond calmly. Know what you would lose, what you would offer, and what you would not. Do not make promises you cannot keep.