Case: a legacy .NET CRM, moved onto Odoo

The migration

We owned the custom Odoo 19 module, and the move of the records and reports onto it.

45+entities
60+reports
1,000+master records

Sample data, not a client record

Collection order

CO-00042

OperatorSample Operator

SiteSite A

DriverDriver 01

VehicleVehicle 01

DocumentsCO-00042

collection-note.pdf
transport-document.pdf
certificate.pdf
photo-01.jpg

A sample collection order with the documents that belong to it, listed on the order itself.

The month-end match

Month-end compliance reports matched exactly while both systems ran in parallel.

Month-end comparison

Sample data, not a client record

ReportLegacy .NETOdoo

Report ALegacy .NETSample value AOdooSample value A

Report BLegacy .NETSample value BOdooSample value B

Report CLegacy .NETSample value COdooSample value C

Report DLegacy .NETSample value DOdooSample value D

Report ELegacy .NETSample value EOdooSample value E

A sample month-end sheet: each report from the legacy .NET system beside the same report from Odoo, entry for entry. It shows the comparison; every entry is a placeholder, and there are no amounts.

Reporting engine

A Windows-only reporting engine was ported to Linux and validated.

Tell us what you run today.

Describe the system or spreadsheet you use today, which records or documents cause difficulty, and what has to change. Include the deadline and any connections to other systems that the work would need to cover.

Email your requirements

A written reply within two working days.