/ solutions · migration & modernisation
Don't migrate blind.Understand the relationships first.
Modernisation programmes rarely fail on execution. They fail on assumptions made before execution started: that a field had an equivalent, that a system had one consumer, that a sequence was safe.
/ the situation
Programmes rarely fail on execution.
They fail on assumptions made before execution started: that a field had an equivalent, that a system had one consumer, that a sequence was safe.
/ the problem
The assumptions are not written down, so they cannot be checked.
Each one is reasonable when it is made and expensive when it is wrong, and the cost lands during delivery — as a change request, at the point where changing anything is dearest.
/ why discovery workshops fall short
A workshop collects what people remember.
It cannot collect the scheduled job nobody owns, the reporting extract reading a table directly, or the consumer that was obvious to whoever built it and has never been written anywhere.
/ what Inferrex supplies
Seven things, and the last one runs for the whole programme.
Discovery
What is actually running, including what the register omits.
Dependency mapping
What consumes what, and in which direction. Sequence follows from this rather than from a workshop.
Schema comparison
Source against target, field by field, resolved through the canonical layer rather than by name matching.
Gap analysis
Matched, transformed, missing, ambiguous and unsupported. The last three are the programme's real scope.
Planning
Waves derived from dependency and gap severity.
Validation
Migrated data checked against the target's actual constraints, not against the intention.
Change monitoring
Vendors keep shipping during a migration. When a source or target changes shape mid-programme, the affected mappings are flagged rather than discovered at cutover.
/ where it fits
Inferrex does not deliver the programme.
It supplies the evidence the programme is planned against, and keeps supplying it while the programme runs. The Migration capability page covers the mechanism.
Establish the dependency map before the sequence is agreed.
Discovery done properly is the cheapest phase of a migration and the one most often skipped.