01
Masters and opening position
Move agreed customers, suppliers, items, balances and stock. Make the historic archive searchable and define which open documents also need to move.
Plan / ERP buyer series
What should an ERP data-migration quote include?
Buy a migration with defined data objects, history depth, mapping rules, rehearsals and sign-off totals. An import file is only one deliverable. Your team also needs ownership of corrections, a cutover boundary and a readable archive. For EPC and cosmetics, preserve the project or batch relationships required to operate and audit the business.
Discuss my ERP scope See the buying checklist
No purchase commitment. Submitting an enquiry does not book a meeting.
Which path fits your situation?
02
Open transaction migration
Preserve active orders, partial receipts and outstanding invoices with their remaining quantities and values. Check dependencies between documents.
03
Selected history
Migrate historic transactions only where they support an identified business or retention requirement. Validate the relationships, not just row counts.
Put the decision in writing
Use the same requirements for every proposal. Record what is included, what needs validation and who owns unresolved work.
| Data area | Scope question | Acceptance test |
|---|---|---|
| Masters | Who owns duplicate removal and unit mapping? | Agreed identifiers and units resolve without duplicate records. |
| Stock | Are locations, lots, expiry and valuation included? | Quantities and values reconcile at the chosen cutover point. |
| Open documents | How are partial receipts and payments represented? | Remaining obligations match approved source reports. |
| History | Which periods and relationships must remain available? | Authorised users can answer the agreed sample queries. |
Swipe the table sideways to compare all columns.
Do a sample before agreeing the final effort
Provide representative anonymised exports with edge cases: duplicate contacts, inactive products, different units and amended documents. Ask the team to map them and explain rejected records. A quote based only on record count can miss the complexity of relationships and cleanup. Agree whether the business or the implementation team corrects each class of error.
Choose evidence that matters to your industry
For EPC, test active project allocations, supplier commitments and remaining quantities on site orders. For cosmetics, test ingredient lots, finished batches, units, expiry dates and quality status. A migration may preserve stock totals while losing the links needed to operate. Put these links into acceptance checks and do not assume a standard spreadsheet import will reconstruct them.
Rehearse the operating window
Agree when the source stops changing, how late transactions are captured and who validates the target. Time a rehearsal so the cutover plan reflects actual work. Record rollback criteria and the person authorised to decide. Keep the source archive available under the business’s retention policy; a successful import does not justify deleting the original records.
From comparison to a scoped proposal
Bring one workflow.
Ask better questions.
Braincuber offers Community-based custom ERP and Odoo Enterprise implementation. We will review fit, gaps and responsibilities before proposing delivery. Bring anonymised examples—not confidential records.
Request a scoped discussion
Questions before you commit
Can you promise every old transaction will migrate?
Not without reviewing source exports, relationships, volumes and requirements. Scope full history separately from masters and opening balances.
Who should clean the data?
The proposal should assign each task. Business owners usually need to resolve ambiguous records even when the implementation team prepares transformation scripts.
Is a matching row count enough?
No. Reconcile quantities, values and required document relationships. Rows can match while the operating meaning is wrong.
Sources and how to use this guide
Braincuber sells ERP implementation services. Product statements refer to the vendor sources below; the evaluation scenarios and recommendations are our analysis. Verify the current edition and commercial terms in your written quote. We have not assigned independent ratings, tested every configuration or invented customer results.
This is an original procurement checklist, not a claim about a particular software edition or a customer case study.