Included in year one
Move the records once, verify them properly
Coming from spreadsheets or another system: your first migration in year one is free — mapped in writing, imported into a trial workspace, then checked line by line before go-live.
Three steps
Map, import, verify — in that order
Most migrations go wrong at the mapping stage, not the import. So the mapping is agreed in writing first: which field moves where, what gets cleaned, and what stays behind on purpose.
- 1 · Map — a sample of your data, a written field mapping, and a decision on every ambiguous column.
- 2 · Import — customers, bookings and orders load into a trial workspace first, not the live one.
- 3 · Verify — you check counts and spot-check records against the source before we sign it off.
Scope
What is free, and what is quoted
The free migration covers one standard source. If the history is messy or spread over several systems, we quote before touching anything.
| Scope | Included — year one, once | Quoted separately |
|---|---|---|
| Customers, bookings and orders from one standard source | Included | — |
| Field mapping session and written mapping document | Included | — |
| Trial import and verification review | Included | — |
| Legacy formats, multiple sources or repeat migrations | — | Quoted |
| Cleaning heavily inconsistent historical records | — | Quoted |
After go-live
Nothing is trapped in the new system either
Migration is a one-off move. Export rights are permanent, on every plan, including the trial — the same CSV you arrive with is the CSV you can leave with.
CSV export
Customers, bookings, orders and stock exported per table, whenever you need them.
Source untouched
We never write back into the system you are leaving — it stays exactly as it was.
30-day window
Imported data stays available for 30 days after a trial ends, so nothing is lost mid-decision.
Your data is yours — before and after
Migration moves it; export rights keep it reachable. Both are part of the plan, not extras.