06 / 10 · Data & knowledge
Traceable data migration
Mapping, validation and a rehearsal before switching systems.
The starting point
Move data along a route you can verify.
Changing tools also means deciding which fields to keep, how to handle duplicates and what to do with incomplete records. We begin with a sample: the final load needs an approved plan and a recoverable backup.
From one field to another, keeping the rule
Source
cliente_emailfecha_altaValidation
Format · duplicates · required fields
Target
emailcreated_at| Source | Transformation | Target |
|---|---|---|
| cliente_email | Trim whitespace | |
| fecha_alta | DD/MM/YYYY → YYYY-MM-DD | created_at |
All three records meet the sample rules.
Demonstration using fictional data. This is not a connected application or an actual client result.
What you are buying
A clearly defined
first handover.
Base prices for the stated starter scope, including applicable taxes. The final quote and external costs are confirmed before contracting.
- Up to two source CSV formats and one target with documented import support.
- Up to 20 fields and an initial batch of up to 10,000 records.
- Field mapping, validation and a rehearsal with an exception report.
- One agreed execution and a plan to recover the previous state.
Outside this scope
Non-exportable databases, special-category personal data, continuous operation and manual cleanup of the entire dataset are excluded. An absolute absence of issues is not promised.
What we need
Anonymised samples, target-system specifications and a person who can validate business rules.
What you receive
Field mapping, scripts, reconciliation report and a repeat or recovery procedure.
How we verify it
Every record is identified as imported, rejected or pending; totals reconcile with the source.
Timing depends on materials, access and reviews. The date is confirmed in your quote.
Another part of the journey.
All solutions ↗
From the problem to the next version