Map active sites, accepted service frequencies and the remaining billing period before importing recurring work. Preserve exclusions and open customer issues, then reconcile outstanding balances and already billed periods with finance. Historical visits should support service history without recreating tasks or charges that the previous system already treated as completed.
Understand the decision
A changeover may occur midway through monthly billing while one site has an unresolved missed visit and another has an approved extra clean. The opening schedule and financial position need the same boundary. Otherwise the business can duplicate service, overlook a remedy or bill a period twice.
Work through the requirements
- Map current site specification versions.
- Agree the billing cutover boundary.
- Reconcile open issues and extra work.
| Record or decision | Why it matters |
|---|---|
| Site mapping | Preserves location and instruction identity. |
| Period reconciliation | Explains billed and remaining service periods. |
| Open-issue register | Carries unresolved customer remedies forward. |
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
Copying recurring templates without a period-by-period review can create duplicate visits and charges. Reconcile active agreements with supervisors and finance, and keep the source reference for every open issue or disputed service period.
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 Cleaning service businesses 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: helpdesk after-sales workflows ↗