Odoo
We implement, customise and upgrade Odoo for companies that run their operations on it. Custom work stays clean enough to upgrade, and every migration ends with a report showing what was moved and checked.
Models checked
214
Passed
213
To review
1
| Model | Records | Check |
|---|---|---|
| res.partner | 12,480 | |
| sale.order | 48,213 | |
| account.move | 96,550 | |
| stock.move | 210,902 / 210,904 | review |
| x_quality_check | tests 34/34 |
What we hear
We're two versions behind and afraid of what the upgrade will break.
Our previous partner left, and nobody understands the custom modules.
Screens take ten seconds to load and scheduled jobs fail overnight.
The store, the bank and the warehouse all need manual exports into Odoo.
What we do
Pick one, or let us handle all of it.
Sales, inventory, manufacturing, accounting and more, configured around how you work, with data migrated from your old system.
Modules written to Odoo's standards, with tests, so they survive the next version upgrade.
A test migration on a copy first, then the real one, with record counts and checks for every key table.
Shopify, marketplaces, payment gateways, logistics, banks and your own apps, with retries and alerts when something fails.
Agents and assistants that read and act on Odoo records under approval rules.
Slow screens, failing crons and broken reports fixed, then monitored under Kalvy Care.
Proof, not promises
Every delivery ends with evidence you can check yourself, not a slide that says it went well.
A typical project
Week 1
Inventory
Every module, customisation, report and integration listed, with data volumes per model.
Week 2
Test migration
A full run on a copy of your database, with record counts and failed checks in a report.
Weeks 3–5
Fix and retest
Custom modules ported with automated tests, then the test migration runs again until it's clean.
Cutover
Go live
Final migration over a weekend, the same checks re-run, and a rollback plan ready if needed.
Pricing
Fixed scope, fixed price, a clear result. A good way to start before a larger project.
Know what breaks before you upgrade: modules, customisations, data and reports.
Evidence · Migration test report with record counts and failed checks
A review of an Odoo or ERPNext system: performance, data quality, security and customisations.
Evidence · Health report with measured numbers, not opinions
Support, monitoring and small improvements for systems we built or took over.
Evidence · Monthly report: incidents, fixes, uptime and hours used
FAQ
Yes, both, on Odoo.sh, Odoo Online where possible, or your own servers.
Yes. We start with a health check so you know the state of the code and data before committing to more work.
It depends on modules and data size. The migration assessment gives you a fixed quote and timeline after a test run.
A 30-minute call with an engineer. You'll leave with a clear next step, even if it isn't us.