Migrate active engagement scope, accepted milestones, unresolved obligations and the reviewed financial position together. Reconcile prior billing, approved changes, subcontract commitments and unbilled effort using an agreed cutover boundary. Preserve technical references without importing every closed issue as live work or treating all recorded development hours as recognized revenue.
Understand the decision
A project can be deployed but awaiting customer acceptance, or accepted while a limited support obligation remains. Legacy time codes may mix project and support activity. The opening snapshot should explain those distinctions so project managers and finance do not draw different conclusions from the same imported status.
Work through the requirements
- Map project and support time categories.
- Reconcile accepted milestones and prior invoices.
- Carry unresolved obligations with named owners.
| Record or decision | Why it matters |
|---|---|
| Engagement snapshot | Explains commercial and delivery status at cutover. |
| Time-code mapping | Connects legacy effort categories to reviewed scope. |
| Opening reconciliation | Shows billed amounts and unresolved 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
Using deployment date as the universal cutover status can conceal acceptance and support obligations. Reconcile the engagement terms with technical evidence and finance records before the imported project position becomes authoritative for reporting or billing.
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 Software consultancies 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: project management ↗Odoo 19: project milestones ↗Odoo 19: timesheet configuration and recording ↗