Introduction
When one company acquires another, the first conversations often focus on systems, applications, and infrastructure.
Eventually, the identity team receives a familiar instruction:
“Move the acquired company’s users into our environment.”
At first glance, the task appears straightforward.
Create accounts in the target directory.
Migrate users.
Move applications.
Transfer data.
Decommission the old environment.
Project complete.
Or so everyone thought.
The Hidden Problem
A large enterprise recently faced this exact challenge following an acquisition.
The integration team had already developed a migration plan. New accounts would be created in the target environment, users would be moved, and the acquired company’s infrastructure would eventually be retired.
Everything looked achievable.
Then a simple question changed the direction of the project:
"What happens to everything attached to those identities?"
The room became quiet.
Because identity is never just a username.
Every user account carries years of accumulated decisions, permissions, relationships, and dependencies.
What appeared to be a user migration was actually an identity preservation challenge.
What Was Really at Risk
The team quickly realized that creating new accounts would generate entirely new identities.
That introduced several risks.
Existing file permissions could stop working because access was tied to the original identity.
Linux servers relying on UID and GID mappings could lose ownership associations.
Application access might require extensive remediation across dozens or even hundreds of systems.
Thousands of employees would likely need password resets.
The service desk could become overwhelmed with support requests.
Most importantly, business users would immediately feel the impact.
What started as an infrastructure project now had the potential to disrupt daily operations across the organization.
The Turning Point
The team stepped back and reconsidered the objective.
Was the goal simply to move users?
Or was the goal to preserve everything those users already had?
The answer was obvious.
Users did not care which directory their account resided in.
They cared about whether they could access their files, applications, systems, and data the next morning.
Success would not be measured by how many accounts were migrated.
It would be measured by how little disruption employees experienced.
A Different Approach
Rather than recreating identities, the organization adopted an identity-preservation strategy.
Instead of treating users as new objects, the migration synchronized critical identity attributes across environments.
This included:
- User accounts
- Existing passwords
- Group memberships
- Organizational structures
- SID history
- Linux UID and GID attributes
By preserving identity continuity, the organization preserved the access decisions that had accumulated over many years.
File permissions continued functioning.
Applications continued recognizing users.
Linux ownership mappings remained intact.
Employees retained their existing passwords.
The migration became largely invisible to the workforce.
The Outcome
When migration weekend arrived, something unusual happened.
Nothing.
Employees logged in as normal.
Applications worked.
Files opened.
Access permissions remained intact.
Helpdesk call volumes remained low.
Business operations continued uninterrupted.
Most employees never realized a major migration had taken place behind the scenes.
For the project team, that was the ultimate measure of success.
The Lesson
Many organizations approach mergers and acquisitions as directory consolidation projects.
But identity migrations are rarely about moving users.
They are about preserving everything attached to those users.
Permissions.
Access rights.
Passwords.
File ownership.
Group memberships.
Years of governance decisions.
The most successful migrations are often the least visible.
Because when identity is preserved correctly, business users never experience the complexity happening behind the scenes.
Key Takeaways
In mergers and acquisitions, the challenge is not moving accounts.
The challenge is preserving trust.
Because identity is more than a user object.
It is the foundation of how people access, collaborate, and work across the enterprise.
