Service / Data migration

Move your data. Lose none of it.

From spreadsheets, old databases or SaaS exports into a new system, mapped field by field and verified before you switch.

Describe your project →See an example
From
spreadsheets, databases, exports
Verified by
row counts, checksums, samples
Switch
planned window, rollback ready
You keep
scripts and mapping

01 / What you get

Six deliverables. In writing or in code.

Source inventory

Every source, its owner and what it holds.

inventory.md

Field mapping

Old field to new field, with every transformation written down.

mapping.csv

Migration scripts

Repeatable, so the test run and the real run do the same thing.

migrate/

Verification report

Row counts, checksums and a sample you check yourself.

verify-report.md

Cut-over plan

The window, who does what, and how to roll back.

cutover.md

Rejects list

Duplicates and broken records we found, for you to decide on.

rejects.csv

02 / How it runs

Five steps. The real data moves once.

  1. Inventory

    every source and owner

  2. Mapping

    signed off by you

  3. Test run

    on a copy, then verified

  4. Cut-over

    planned window, rollback ready

  5. Handover

    scripts and report to you

03 / Example

A test run, verified. Before anything touches production.

Illustrative. Counts and file names are invented.

Example · invented data

migrate · staging
$ make migrate SOURCE=crm-2014.sql TARGET=stagingread 18,402 customers · 61,977 invoicesmapped 31 fields · 4 transformations$ make verifyrow counts match (80,379 / 80,379)checksums match27 duplicate customers → rejects.csv

04 / What to send us

  1. 01The systems the data lives in today
  2. 02A small sample, with personal data removed
  3. 03Where the data has to end up
  4. 04Your deadline, if there is one

05 / Related

06 / FAQ

How do we know nothing was lost?

Every run is verified: row counts per table, checksums, and a sample you compare yourself. Records that cannot move cleanly go to a rejects list.

Do we have to stop working during the migration?

Only for the cut-over window, which we plan with you. Test runs use a copy while you keep working in the old system.

Can you migrate personal data?

Yes, under a data processing agreement, as GDPR Article 28 requires. Test runs use anonymised data wherever that is enough.

What if the old system has no export?

We read its database or files directly where your licence allows. If neither is possible, the inventory says so before any build is quoted.

Describe your migration

Where the data is, where it goes, and by when.

  • Fixed-scope quote — no obligation
  • Reply within 1 business day

By sending this, you agree that we may contact you about this inquiry.