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 requirementsA 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.
Decisions we owned
- The new system’s opening balance was anchored to the old system’s January closing.
- Master records were matched only on an exact place identifier, and new records were created rather than risk a misrouted order.
- Month-ends on the old system stopped at its last real month; later months were never regenerated on it.
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
| Report | Legacy .NET | Match | Odoo |
|---|---|---|---|
| Report A | Sample value A | = | Sample value A |
| Report B | Sample value B | = | Sample value B |
| Report C | Sample value C | = | Sample value C |
Sample data, not a client record
Reporting engine
A Windows-only reporting engine was ported to Linux and validated.
Reply if any question.
Tell us what you run today.
Send your requirementsA written reply within two working days.