Resolve vehicle identity and customer relationships before importing historical service records. Separate open jobs, approved estimates, unpaid invoices and reference-only history, and reconcile each category at the same cutover point. Preserve the original source identifiers so repeated imports or changes of ownership do not create duplicate vehicles or silently transfer financial responsibility.
Understand the decision
Legacy workshop records may contain inconsistent vehicle identifiers, changed registration details and more than one customer associated with the same vehicle. The target model must explain those relationships deliberately. Review sensitive historical notes and determine which information is needed for current operations before making it broadly accessible.
Work through the requirements
- Resolve ambiguous vehicle identifiers.
- Map customer relationships and open work.
- Reconcile unpaid and previously billed amounts.
| Record or decision | Why it matters |
|---|---|
| Vehicle cross-reference | Preserves source and target asset identity. |
| Open-job reconciliation | Accounts for unfinished approved work. |
| Customer balance mapping | Keeps financial responsibility correctly assigned. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Using a registration label alone as permanent vehicle identity can merge or split history incorrectly. Agree the identification rule, review ambiguous active vehicles and retain a source cross-reference before relying on migrated records for service decisions.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Automotive repair businesses in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: processing repair orders ↗Odoo 19: sales quotations and invoicing methods ↗Odoo 19: timesheet configuration and recording ↗