Migrate active appointments with their current phase, operative deliverable revisions, unresolved decisions and reviewed financial position. Reconcile prior invoices and outstanding consultant commitments separately from task progress. Preserve stable project and document references so historical issues remain accessible without being mistaken for the latest instruction or a new deliverable obligation.
Understand the decision
Older project folders may use different numbering conventions from the current practice, and a project's commercial phase may not match its technical progress. The migration should establish an agreed opening snapshot and retain the source relationships needed to understand why a deliverable or fee remains outstanding.
Work through the requirements
- Map project and document identifiers.
- Identify current issues and unresolved decisions.
- Reconcile billing and consultant commitments.
| Record or decision | Why it matters |
|---|---|
| Project opening snapshot | Explains phase and remaining obligations. |
| Document cross-reference | Preserves revision identity and source access. |
| Commercial reconciliation | Shows billed amounts and outstanding commitments. |
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 folder names as project status can confuse document organization with actual completion. Agree the operative revision and outstanding decisions with project leads, then reconcile financial records through a separate reviewed process before launch.
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 Architecture and design practices 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 ↗