Start with active customer sites, identifiable equipment and unresolved service obligations. Map each unit to its location and owner before importing service history, and preserve source references for open quotes and unbilled work. Reconcile outstanding customer balances separately from operational history so an old visit cannot accidentally create a new receivable.
Understand the decision
Legacy dispatch software may identify equipment by free-text descriptions rather than stable serial or asset references. Two similar rooftop units at one building must remain distinguishable, while a renamed property manager should not split the building's history into unrelated customer records after migration.
Work through the requirements
- Resolve ambiguous equipment identities first.
- Map active obligations to customer sites.
- Reconcile open work and receivables.
| Record or decision | Why it matters |
|---|---|
| Equipment mapping | Links source units to target identities. |
| Open-work ledger | Lists visits still requiring action. |
| Balance reconciliation | Explains customer-level financial differences. |
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
Importing every historical note before resolving equipment identity creates a searchable collection of ambiguity. Prioritize the records needed for upcoming work, preserve an approved archive and investigate every unmatched active unit before cutover.
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 HVAC contractors 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: field service materials and warehouse configuration ↗Odoo 19: helpdesk after-sales workflows ↗Odoo 19: sales quotations and invoicing methods ↗