Migrate active bookings, future cohorts, participant relationships and unresolved changes with a defined cutover date. Reconcile prepaid fees, prior invoices and delivery still owed separately from attendance history. Preserve approved source evidence for completion records where required, without assuming that importing an attendance row establishes a qualification or accreditation outcome.
Understand the decision
A provider may change systems between customer payment and course delivery, or while a postponed cohort awaits a new date. Historical records can mix the participant and corporate payer. Resolve those relationships before import so future communications, commercial balances and remaining delivery obligations remain accurate.
Work through the requirements
- Map booking, cohort and participant identities.
- Reconcile paid and undelivered commitments.
- Review required historical evidence and access.
| Record or decision | Why it matters |
|---|---|
| Cohort cross-reference | Preserves session and participant relationships. |
| Obligation reconciliation | Explains paid but undelivered training. |
| Evidence register | Identifies approved historical completion sources. |
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
Loading attendance history first can distract from undelivered paid bookings and unresolved postponements. Reconcile active obligations and role relationships before importing reference history, and validate any completion evidence through the provider's approved learning and reporting process.
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 Training providers 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: sales quotations and invoicing methods ↗Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗