Simplicity Idea Tech

A legacy .NET CRM, moved onto Odoo

Operations moved to the new system in February 2026 while the old system still had to produce a month-end report that tallied with the new one.

Send your requirements

A written reply within two working days.

Record of past work measured figures

Migration scope, one past project

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

What made it hard

Collections in one month were consumed by shipments in the next, so both systems had to agree across the month boundary.

Collections in one month, the month boundary, then shipments in the next month that consume them ONE MONTHCollections THE NEXT MONTHShipments Month boundary Consumed by
Explanatory diagram — not a system screen or client record

Decisions we owned

Month-end reports compared entry for entry, every gap explained.

The month-end report was generated on both systems while they ran in parallel, and every difference was traced to its cause.

Month-end comparison sample

Sample data: each report shows the same entry in Legacy .NET and in Odoo
ReportLegacy .NETMatchOdoo
Report ASample value A=Sample value A
Report BSample value B=Sample value B
Report CSample value C=Sample value C

Sample data, not a client record

Reporting engine

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

Guide: fixing a gap in a month-end report

Reply if any question.

Tell us what you run today.

Send your requirements

A written reply within two working days.