Data migration

2–5.8 weeks typical Fixed quote after scoping

Moving your existing data onto the new system — profiled, mapped, backfilled, reconciled, and cut over with a rehearsed rollback.

Scope your project →

What we build

Replacing a system is rarely about the new system; it is about the years of data already in the old one. This profiles what you actually have (including the parts nobody documented), maps it onto the new model, builds the pipeline that moves it, and proves the result reconciles record for record. The cutover is rehearsed before it is run, with a rollback that has been tested rather than assumed. Choose this whenever there is an existing system, spreadsheet or database whose history has to survive the move. A one-off import of a single clean spreadsheet is an activity inside the backend data layer, not this service.

What you get

  • A source data profile report covering row counts, null rates and integrity issues per table
  • A field-level mapping document from the legacy schema to the new model
  • The extract-and-transform pipeline in a Git repository, rerunnable end to end
  • A reconciliation report proving record counts match between source and target
  • A written cutover and rollback plan
  • A cutover rehearsal completed in staging, with timings logged
  • All in-scope records live in the new system, with the post-cutover reconciliation signed off

How the work unfolds

  1. Profile the source data and its quality
  2. Map the legacy schema onto the new model
  3. Build the extract and transform pipeline
  4. Backfill and reconcile record counts
  5. Rehearse the cutover and the rollback
  6. Run the live cutover with verification

What shapes the price

Before you see a number, our scoping conversation asks:

  • How many systems is the data coming out of? Each source system is its own extraction, quirks and credentials.
  • Roughly how many kinds of records are moving — tables, sheets, collections? Each record type is profiled, mapped field-by-field and reconciled.

How an engagement starts

This work builds on Discovery workshop, so scope, boundaries and constraints are agreed before anything is built.

Teams often combine it with:

Get a priced plan →