THE DIRECT ANSWER

Agree an opening position for each project that separates accepted contract value, approved changes, prior billing, supplier commitments and remaining work. Reconcile these components with the source records and finance before migration. Retain accessible historical evidence without turning already fulfilled obligations into new tasks, purchases or charges during the import.

Understand the decision

A live project may have partially paid subcontract accounts, deliveries not yet invoiced and changes awaiting customer agreement. The migration needs an agreed cutover boundary so a document arriving late can be assigned to the correct system and reviewed without duplicating the underlying obligation.

Work through the requirements

  1. Freeze the agreed opening position.
  2. Reconcile purchases, receipts and prior billing.
  3. Assign treatment for late source documents.
Information to bring to the review
Record or decisionWhy it matters
Opening ledgerExplains commercial balances and commitments.
Document mappingConnects source and target references.
Cutover exceptionsTracks late or disputed opening items.
TRY THIS WITH YOUR TEAM

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.

0 of 3 marked

Watch for this failure

A single matching project balance can hide missing commitments and duplicate billing. Require a component-level reconciliation and a named owner for every unexplained opening item before the live project relies on the new ledger.

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 guide
FROM REQUIREMENTS TO A REAL SCOPE

Bring your workflow to the conversation.

Discuss requirements for General 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: project management ↗Odoo 19: project milestones ↗Odoo 19: sales quotations and invoicing methods ↗