Keep the scenario
The pilot product, data, roles, steps, results and gaps become an acceptance-testing baseline, not a forgotten demonstration.
Version the solution
List Odoo image, edition, modules, commits, settings, dependencies, secrets to recreate and applicable licenses.
Document the data
Sources, mappings, identifiers, cleaning rules, rejections, reconciliations and archives must be reproducible.
Hand over the decisions
Accepted assumptions, exclusions, risks, trade-offs and debt must remain visible to avoid contradictory promises.
Assign responsibilities
The client, Omnifloo, the integrator, the hosting provider and third parties know who designs, carries out, validates and supports each task.
Set stage gates
The partner takes over the delivery package after reviewing the file; production starts only after acceptance testing, a tested recovery procedure and a signed decision.
Going further: our hour-by-hour cutover plan and our RACI matrix specify who decides at each gate.