Day one arrives before the plan does
The date was set by the transaction, not by anyone who had mapped the two estates. It does not move because the mapping is not finished.
Post-M&A consolidation
Two companies, four directories, one Monday morning
The deal closes on a date decided by lawyers. Identity has to produce working access for people who now share a payroll and nothing else — while the consolidation everyone agreed to runs for the next three years.
Why identity ends up on the critical path
Every synergy in the integration plan requires somebody from one company to reach a system in the other. That is an identity problem before it is anything else.
Both sides already made their choices
Two directories, two identity providers, two naming conventions, two definitions of what a role means. Neither was wrong — they were simply made independently.
The consolidation outlives the deadline
Directory merges are slow, risky and frequently paused when something more urgent appears. Whatever you build for day one will be asked to keep working for years.
The only triage that mattersDay one Later, on your terms
What must work on Monday, and what must not be confused with it
Most integration programmes treat both columns as urgent, and then discover that the right-hand one was never blocking anything.
Access has to work
People cannot do their jobs without this. There is no acceptable version of "next quarter".
- Executives reach each other's reporting
- Finance reaches the consolidated ledger
- Joint project teams share collaboration tools
- Everyone can still do the job they did on Friday
- Nothing that was compliant on Friday stops being compliant
Consolidation saves money
Worth doing, at a time you choose. Nothing on this list stops anybody working on Monday.
- One directory instead of two
- A single naming convention
- A common definition of what each role means
- Retiring the identity provider you decided not to keep
- Consolidated licensing
And sometimes the exercise runs in reverse: a divestiture needs the same capability, used to separate cleanly rather than to join.
What integration needs from identity
First to make day one work, then to make consolidation optional rather than urgent.
Cross-access without migration
People from either company reaching shared applications while their accounts stay where they are. Migration, if it happens, becomes a later decision made calmly.
One access experience across two estates
A single sign-on that spans both, so the integration does not announce itself to every employee every morning as two sets of credentials.
Policy per entity, while it lasts
The two organisations will have different authentication requirements and different regulators for as long as they remain separate legal entities.
One picture of who now exists
Duplicate identities across the two estates have to be reconciled before anybody can answer basic questions about headcount, access or licensing.
How Monokee approaches it
Broker first, consolidate later, on your terms
Sit between rather than merge
Monokee brokers between both identity providers and the applications on either side. Day-one access becomes a configuration exercise instead of a directory migration under deadline.
Each entity keeps its domain
Separate domains with their own identity providers, branding and local rules, while the journeys that are genuinely shared stay aligned instead of forking into two drifting copies.
Consolidation becomes optional
Once access works through the broker, merging the directories is a project you undertake because it saves money — not because nothing works until it is done.
Bring us the closing date
Working backwards from it is usually more productive than working forwards from the target architecture.
Talk to an expert