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.
What merging
costs in time today.
The same person sits in two systems with two personnel numbers
Fields have different names and are filled in differently
Nobody knows which record is the leading one
The clean-up is not finished after the first pass
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.
Simple, medium
and genuinely complex.
All of them examples from live operation. What gets built is whatever comes up in your work.
Find duplicates
TriggerA suspicion of duplicate records
- Compare the records
- List the matches
- Put them forward for review
ResultDuplicate employee files become visible before they cause damage.
Merge two workforces
TriggerAn acquisition or a merger
- Align the personnel numbers
- Merge the duplicates
- Reassign the cost centres
- Unify the management structure
- Archive the old records
ResultTwo sets of records become one, traceably, with the history preserved.
Consolidate an international landscape
TriggerTwelve legal entities, seven systems, five countries
- Record the systems and their data
- Define the leading system per data object
- Reconcile the field catalogues of each country
- Unify formats and codes
- Preserve local mandatory fields
- Resolve conflicts by the rule set
- Respect the data protection limits of each country
- Have the result approved per legal entity
- Generate complete migration documentation
ResultSeven home-grown systems in five countries become one dependable set of data.
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.
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.
What we are asked about merging
most often.
How are duplicates found?
What happens to duplicate personnel numbers?
How do we handle different collective agreements?
Is the clean-up finished after one pass?
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.

