Reconcile the fleet’s physical locations, active customer-held assets, future bookings and financial positions before cutover. Preserve original booking and asset references so returns can be matched after launch. Distinguish historical charges from remaining obligations, and have responsible staff approve any uncertain asset identity, overdue status or future availability conflict rather than hiding it in an opening total.
Understand the decision
Some assets are with customers, others await inspection and several already have future reservations. The accounting system also holds deposits or unpaid amounts. Migration needs a coordinated opening view of assets, time commitments and money; an inventory count of the yard alone cannot represent the whole rental operation.
Work through the requirements
- Locate each relevant asset and active obligation
- Reconcile booking periods and financial references
- Rehearse a return and future pickup after import
| Record or decision | Why it matters |
|---|---|
| Fleet opening register | Shows identity location and readiness |
| Booking cutover bridge | Preserves active and future commitments |
| Customer balance review | Explains deposits charges and open amounts |
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
Do not import only assets physically in the yard or recreate active rentals as new bookings. Either shortcut can lose customer-held equipment, duplicate charges or promise an asset that is already committed to someone else after cutover.
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 Equipment rental 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.
Pick up and return rental products ↗Rental product type ↗Serial numbers ↗