Home›Use cases›Merging & clean-up
◉ 3 examples from practice

Merging sets of data
After an acquisition there are suddenly three truths

When two companies come together, two sets of data meet that describe the same people differently. Duplicates, different field names, duplicate personnel numbers. By hand that is weeks of work, and afterwards not reliably right.

2 weeks until two workforces fit together estimated from comparable projects
Monthstypical time after an acquisition
2 weekswith us
automaticallyduplicates found and cleaned up
The starting point

What merging
costs in time today.

1

The same person sits in two systems with two personnel numbers

2

Fields have different names and are filled in differently

3

Nobody knows which record is the leading one

4

The clean-up is not finished after the first pass

Programmes involved

These are the systems
tied to this area.

All already connected. If yours is missing, we build the integration at no extra cost, on average within three days.

Personio Workday DATEV Sage SAP SuccessFactors Greenhouse

Is your programme included?

Three examples

Simple, medium
and genuinely complex.

All of them examples from live operation. What gets built is whatever comes up in your work.

SimpleA few steps, ready straight away

Find duplicates

TriggerA suspicion of duplicate records

  1. Compare the records
  2. List the matches
  3. Put them forward for review

ResultDuplicate employee files become visible before they cause damage.

MediumWith conditions and approvals

Merge two workforces

TriggerAn acquisition or a merger

  1. Align the personnel numbers
  2. Merge the duplicates
  3. Reassign the cost centres
  4. Unify the management structure
  5. Archive the old records

ResultTwo sets of records become one, traceably, with the history preserved.

ComplexBranches, deadlines, several systems

Consolidate an international landscape

TriggerTwelve legal entities, seven systems, five countries

  1. Record the systems and their data
  2. Define the leading system per data object
  3. Reconcile the field catalogues of each country
  4. Unify formats and codes
  5. Preserve local mandatory fields
  6. Resolve conflicts by the rule set
  7. Respect the data protection limits of each country
  8. Have the result approved per legal entity
  9. Generate complete migration documentation

ResultSeven home-grown systems in five countries become one dependable set of data.

The exceptions

And what about
the special cases?

That is the question most automation projects fail on. With us the exceptions get built in, not left out.

An acquisition with a different collective agreement
International consolidation across several jurisdictions
A partial business transfer where only some staff move across

Each of these cases can be mapped in the builder as its own branch, with a condition, an approval and a different route. Without a line of code.

Common questions

What we are asked about merging
most often.

How are duplicates found?
By several attributes at once, not just the name. Doubtful cases are put forward for review rather than merged automatically.
What happens to duplicate personnel numbers?
They are reissued under a rule you set. The old number is kept as a reference so historical documents can still be matched.
How do we handle different collective agreements?
They stay separate. The workflow decides per person which rules apply, even when both groups sit in the same system.
Is the clean-up finished after one pass?
Rarely. That is why the reconciliation keeps running and reports new differences, instead of cleaning up once and then drifting apart again.
The next step

Tell us
what comes up in your work.

30 minutes on your actual programmes. We rebuild your data merging workflow live, not on a made-up company.