ERP data migration
Your data, moved in order and checked before sign-off.
Mapped, cleaned, checked against the source and loaded in the order it depends on. The old system stays readable until you sign off.
What moves, from where
Moves we take on.
From
- An older ERP on SQL Server
- QuickBooks
- Sage
- Spreadsheets
- Access
- A home-built system
To
- ERPNext
- Odoo
- Another ERP
Examples of moves we take on, such as QuickBooks to a full ERP. Any other move: the assessment confirms the route before any quote.
Six stages
What happens, and what you do.
Each stage ends with something you can check. Nothing moves to the next one until it does.
01 / 06
Assess
Every source is read, never edited. What moves and what stays is written down before anything is touched.
What you doGive read access to each source and name who owns it.
02 / 06
Map
Every field gets a rule and an owner. Your team signs the rules.
What you doSign the mapping rules.
03 / 06
Cleanse
Every record is counted, not sampled. Defects are listed with row numbers. Where we would have to guess, we ask instead.
What you doDecide the held values.
04 / 06
Validate
Counts and control totals tie back to the source, or the gap is named.
What you doReview the list of discrepancies.
05 / 06
Import
Loaded in the order it depends on, into a copy first. Re-run until every run matches.
What you doCheck the test load in the copy.
06 / 06
Cutover
Go-live on a date you choose. The old system stays readable until you sign off.
What you doPick the date, then sign off.
Sample migration
The first morning.
Load the record types in any order you like, then see what the new system ends up holding. It all imported. That is the problem: nothing failed loudly enough to stop the run, and the gaps appear when somebody tries to pick an order. Two rows end as “Held for a decision”: a date that could be 3 April or 4 March, and a blank country. The source owner decides, not us.
Not loaded yet10
In the new system0
Nothing loaded yet.
In writing
What you get in writing.
- Mapping and transformation rules you can reuse.
- Import tooling that re-runs as the source changes.
- Validation against the source, with every discrepancy listed.
- A cutover plan the operations team can work from on the first morning.
On record
Why the method holds.
Before BI Margin, we delivered ERPNext migrations end to end: setting up the cloud servers, mapping and importing everything from master data to opening balances and open orders, taking over half-finished work from someone else, and carrying projects through go-live. The method carries to other platforms, Odoo included.
Behind it: 5+ years of hands-on software development, integration, optimisation and automation.
Every change carries its rule, its run and its reason.
Price
Fixed in writing after the assessment.
A migration covers one legal entity and one source system: master data, opening balances and open orders, with mapping, cleansing, a test load, reconciliation and cutover support. How much history comes across is scoped at the assessment, so the quote covers exactly what moves.
More systems, more legal entities, more history or a date that cannot move make a job larger. The assessment measures each of these before the price is fixed.
Questions
Before a migration starts.
How clean does our data need to be?
It does not need to be clean. Cleansing is a stage of the work. Every record is counted, defects are listed with row numbers, and anything we would have to guess comes back to you as a question.
How much history comes across?
You decide, and it is written down before the work starts. A migration covers master data, opening balances and open orders; how much history comes across is scoped at the assessment.
How do we know the numbers match?
Counts and control totals are tied back to the source. Where they do not tie, the gap is named and listed.
Do we need a parallel run?
Sometimes. The assessment says whether one is worth it for you. Either way, the old system stays readable until you sign off.
ERPNext or Odoo?
That is one of the answers the Systems Assessment gives, from how your business runs.
Our project has already stalled.
Then start with the rescue page. We read what is there before anything moves.
Can you connect it afterwards?
Yes. Connecting the ERP to your store, bank, CRM or Microsoft 365 is integration work.
Where will it run?
On hosting you choose, or hosted and looked after by us.
Do you set up the whole ERP?
No. We move the data, rescue stalled projects and add what the ERP is missing. We don’t sell full ERP setup or end-user training.
Next step
Bring the data you have.
Book a call, or start with the Systems Assessment.