PIPELINEGuide
Data migration: where to start without losing focus
The most common mistake when starting is not the wrong technology, but the wrong first step. A sequence that has proven itself in small businesses.
Getting started with data migration doesn't begin with the technology, but with a week of tracking: What repeats, what takes the most time. Then a single, clearly defined process with a measurable goal — only with clear scope do quotes become comparable at all.
01 — Getting started
Where to begin
Name the bottleneck
Not the most interesting thing, but what takes the most time. A week of tracking what repeats delivers a more realistic list than any workshop.
Define a small scope
One process, one measurable goal. What works gets expanded — what doesn't costs little.
Survey the starting situation
What content, data, and access is available. For data migration, this is the factor that most strongly influences effort and duration.
Decide who is responsible
For the implementation and for operations afterward. Without this definition, every system becomes outdated.
Only then request proposals
With a clear scope, proposals become comparable. Without it, you get numbers that have nothing to do with each other.
02 — Fit
When it's worth it
- The process in question occurs at least weekly.
- It follows rules you can write down — even if there are exceptions.
- Today it's manual work that no one enjoys doing.
- There's one person who decides, not three who need to coordinate.
- You can name what would tell you it worked.
03 — Checklist
Clarify before the first quote
- What should improve? In one sentence, no jargon.
- How will you know? One number that should change.
- Who decides? One person, not a committee.
- What budget is available? A range is enough — it makes quotes comparable instead of arbitrary.
- By when? And what the deadline depends on.
- Which systems are involved? And who has access to them.
- What do you already have? Content, data, preliminary work — this reduces the cost.
04 — Questions
Frequently asked questions
How long does a migration take?
The transfer itself usually hours. The time goes into analysis, rules, and trial runs — typically two to six weeks, depending on the condition of the legacy data.
What if something is missing after the switchover?
That's why count protocol and fallback option: the legacy inventory remains untouched until acceptance is complete. Subsequent additions of individual areas are possible.
What happens to attachments and documents on the record?
They are transferred along, provided the target system supports them. Where the format doesn't fit, it's clarified beforehand whether conversion is necessary or external storage remains more practical.
Can we keep working in parallel?
For short transitions yes, with a cutoff date. For longer migrations, you typically continue working in the legacy system until the switchover and transfer the additions at the end.
How do we ensure nothing gets lost?
Through the count protocol: number of records before and after is compared, samples are checked for content. Only after this acceptance is the migration considered complete.
Do we need access to both systems simultaneously for the migration?
Yes, at least for the period of trial runs and the actual switchover. After that, access to the legacy system can be restricted or terminated.
Do we take everything?
Rarely makes sense. Dead records, test datasets, and ten-year-old transactions burden the new system. We recommend migrating the active inventory and keeping the rest archived and accessible.
05 — Next
Related pages
Next step
Send us a few sentences about your project.
We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.