Platform replacement
Move customer, asset, product, finance or operational history from a legacy system into a new application.
03 · Data & Reporting
Data migration: Move business-critical data through rehearsed, reconciled and reversible gates.
Lumaivo plans and delivers migrations from legacy databases, exports and operational systems into new platforms or trusted reporting stores. Mapping, transformation, exceptions, rehearsal and reconciliation stay visible throughout.
What this service is for
Start with the business meaning, then make the technical route explicit.
Migration is not simply copying rows from one place to another. Source history may contain duplicates, effective-dated values, hidden reference rules and records the target cannot represent directly. The business also needs evidence that the new system contains what was agreed.
We separate discovery from execution, build deterministic source-to-target logic, test with representative data and run controlled rehearsals. Cutover proceeds against agreed readiness checks, with a documented rollback position and post-load reconciliation rather than optimism.
Where it becomes useful
Common use cases, framed around the decision or hand-off.
Consolidation
Combine records from several business units or acquired systems into a governed target model.
Reporting transition
Create a trusted copied-data store when direct reporting from the live source is unsafe or impractical.
Method
A controlled route from discovery to an accepted output.
- 01
Discover
Inventory sources, targets, owners, retention needs, interfaces, volumes and critical business dates.
- 02
Map
Define field crosswalks, transformations, defaults, exclusions, reference data and duplicate handling.
- 03
Build
Create repeatable extract, transform, load and validation routines with versioned configuration.
- 04
Rehearse
Run representative migrations, measure exceptions and timings, and refine the cutover runbook.
- 05
Cut over
Execute approved gates, reconcile the loaded population and retain the evidence needed for sign-off or rollback.
Typical deliverables
What the review-ready work can contain.
- Migration scope, dependency and ownership map
- Source-to-target mapping and transformation specification
- Repeatable extract, transform and load routines
- Duplicate and exception-handling rules
- Rehearsal evidence and cutover runbook
- Post-load reconciliation and sign-off pack
Boundaries
What stays explicit instead of being over-promised.
- Production cutover is not attempted before representative rehearsal and agreed readiness criteria.
- Source records and raw extracts are retained according to the approved evidence and retention plan.
- Target limitations and excluded history are documented, not hidden in transformation code.
- Rollback requirements are agreed before the irreversible step, not after it.
Questions before the first conversation
Plain answers, with the limits left in.
Can you work with an existing implementation partner?
Yes. Lumaivo can own a bounded migration workstream, provide mapping and validation, or supply independent reconciliation and assurance alongside the target-platform team.
How many rehearsal migrations are needed?
The number depends on data quality, volume, target behaviour and cutover risk. We define exit criteria for each rehearsal rather than promising a fixed count without seeing the estate.
What happens to records the target cannot accept?
They are classified as transformations, exclusions or exceptions with an owner and decision. They are not silently dropped.
Can you migrate documents as well as database records?
Potentially, where the source, target, metadata and access route are understood. Document migration is scoped separately because file integrity, metadata and permissions need their own checks.
Do you support big-bang and phased cutovers?
Both patterns can be considered. The right approach depends on system dependencies, parallel-running options, business dates and the ability to reconcile each transition state.
Related services
Continue through the connected system.
01 · Data & Reporting
Data mapping
Make every field, key, rule and ownership decision visible before building the next layer.
Read service 02 · Data & ReportingData validation
Prove what is complete, consistent and fit for purpose - and surface what is not.
Read service 04 · Data & ReportingData integration
If it has a way out, we can usually connect it.
Read serviceStart with the messy version. Make the first useful outcome explicit.
Send the systems, reports, constraints and decisions involved. Lumaivo will help define a bounded first step and the evidence needed to accept it.
Map the first useful step