Map active clients, accepted deliverables, recurring commitments and unresolved approvals before importing historical project activity. Reconcile prior invoices, prepaid amounts and approved external costs with finance, keeping them separate from recorded effort. Preserve the current brief revision so imported tasks do not revive cancelled assets or create duplicate recurring charges.
Understand the decision
An agency may switch systems while a campaign is partly delivered and the next retainer period is approaching. Some creative work is complete but awaiting approval, and supplier invoices may arrive later. The opening snapshot must explain those states without equating all unfinished tasks with unbilled revenue.
Work through the requirements
- Identify active scope and pending approvals.
- Agree recurring-service and billing boundaries.
- Reconcile external commitments and prepaid amounts.
| Record or decision | Why it matters |
|---|---|
| Client opening snapshot | Shows deliverables and remaining obligations. |
| Recurring-period mapping | Prevents overlapping service and billing periods. |
| Supplier reconciliation | Explains committed and received external costs. |
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
Migrating only project task status loses the commercial context of agency work. Review approval, fee and supplier positions together, and keep source references available for any opening item that finance and delivery interpret differently.
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 Marketing agencies 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: timesheet configuration and recording ↗Odoo 19: sales quotations and invoicing methods ↗