ERP data migration without losing your history
I'm a data migration consultant for companies switching ERP, accounting or field-service systems. I map, clean, migrate and reconcile your data in SQL Server, so the new system starts with history you can trust.
Who this is for
Companies changing systems who can't afford to lose years of jobs, customers and costs, or to start the new system with bad data.
- You're moving to a new ERP, accounting or field-service system
- You want more history than the vendor's import template allows
- Your data has duplicates, old codes and records nobody uses
- You're merging two companies or systems into one
Where ERP data migrations usually go wrong
Only the basics come across
Import templates take open items and master records. Years of job costs, service history and closed invoices get left behind.
Bad data moves with you
Duplicate customers, inconsistent cost codes and inactive items get copied straight into the new system.
Nobody can prove it's right
Opening balances don't tie out and nobody knows why. Trust in the new system drops on day one.
Left to the last weekend
The data is treated as a go-live task instead of a project. Problems show up when there's no time to fix them.
What you get
A data mapping document
Every field from the old system to the new one, with each decision written down and agreed.
Data cleanup
Duplicates merged, codes standardized, inactive records archived, before anything is loaded.
Repeatable migration scripts
SQL Server scripts that run the whole migration the same way every time, so test loads are cheap to repeat.
Reconciliation reports
Counts and totals, old against new, by customer, job and period. Something you can sign off on.
A searchable history archive
Anything you don't migrate stays queryable in an archive database with simple reports, so you can retire the old system.
Cutover plan and go-live support
A step-by-step plan for the final load, and support during the first weeks on the new system.
How a data migration works
Assess
I profile your current data: what's there, what's clean, what's missing, and how much history is worth moving.
Map and clean
We map old to new together, and I clean the data at the source or in staging.
Test loads
Several full test migrations with reconciliation, so problems surface early and not on go-live day.
Cut over
Final load, final reconciliation, and support while your team settles into the new system.
Data migration: common questions
How much history should we migrate?
It depends on what your team actually looks up. A common approach is open items plus a few years of detail in the new system, with older history kept in a searchable archive. We decide together during the assessment.
Do you work with our new software vendor?
Yes. The vendor's implementation team configures the new system. I handle extraction, cleanup, transformation and reconciliation, and coordinate with them on the import format.
What happens to the old system's data?
Nothing is thrown away. Data that isn't migrated can live in an archive database with reports, so you can stop paying for the old system and still find what you need.
Can you migrate from Access, Excel or an older database?
Yes. SQL Server, Access, Excel, CSV exports and most databases that can export their data.
What if the migration uncovers problems?
That's what the test loads are for. Problems are found and fixed during testing, with time to decide what to do, instead of during the go-live weekend.
Planning a system switch?
The earlier the data is part of the plan, the smoother go-live is. Book a free 30-minute call to talk through your migration.