Flow blueprint
Directory merge
Two companies, two HR systems, one directory. Connect them, meet the duplicate person, cut over, and keep both feeds honest.
Simulator Directory merge
1 · Trigger an event
2 · Change the conditions
Ready. Pick an event.
Example event: Connect Company B
- HR: Company A acquirer
- HR: Company B acquired
- AuthMantra one workspace
- One directory unique userName
- Company A apps SSO already
- Company B apps moving to SSO
- Audit log every merge step
$ hr-b connect --scim POST /scim/v2/Users x1,240 ✓ scim.user.created x1,240 directory now holds A and B people ✓ no downtime for either side
- Connect Company B second HR feed
- One person, two records worked at both
- Move B's apps to SSO one at a time
- Cutover day B signs in the new way
- B person leaves mid-merge last day is today
All output on this page is simulated, with made-up names and values. Keys 1 to 5 run the events.
What you need
Both HR feeds
Able to send SCIM 2.0.
A matching rule
Which email or ID is the same person.
An app order
Which of B's apps moves first.
Both feeds on until done
Leavers keep flowing.
A cutover plan
Passkey or authenticator at first sign-in.
Try Directory merge on your own people
Free for up to 10 people. Or book a consultation and we will walk through your setup.