Assurance, dated deadline
Odoo RPC Integration Migration Audit
The XML-RPC and JSON-RPC endpoints are going away. Nearly every Odoo integration written in the last decade goes through them. This audit produces the list of what breaks, before it breaks.
See the scopeThe deadline
Odoo's documentation schedules the removal of the XML-RPC and JSON-RPC endpoints in Odoo 20, autumn 2026. That is Odoo's published date, not our estimate.
Those two protocols are how nearly everything has talked to Odoo for the past decade. Your Zapier, Make and n8n scenarios. Your BI dashboards. Your warehouse scanners. The Python script a former colleague wrote to sync orders that nobody maintains any more.
The problem is not the technical migration, which is tractable. The problem is that almost nobody owns an inventory of their integration surface. You cannot plan the replacement of something you have never listed, and the forgotten integrations are exactly the ones that fail silently.
This audit is part of Independent Odoo Assurance: fixed scope, fixed fee, written deliverable.
What we inventory
Every caller, not only the ones you remember. Server logs surface the integrations nobody documented.
Callers in the logs
Server log analysis to find every real RPC client, including the ones nobody remembers setting up.
Automation platforms
Zapier, Make and n8n scenarios, with the Odoo models they read and write and how often they call.
BI and warehouses
Reporting connectors and extract jobs pulling Odoo data on a schedule.
Internal scripts
In-house code, cron jobs and one-off tools that talk to Odoo without anyone calling them integrations.
Accounts and auth
Which user each caller authenticates as, which API keys it uses, and what access that actually grants.
Hardware and floor
Warehouse scanners, scales, kiosks and any device querying Odoo directly.
What we need from you
Server logs
Ideally 30 days, to catch the monthly and period-end integrations a 7-day window would miss.
Read-only access
A read user, or an export of the configuration and the API key list.
Platform access
Read access to your Zapier, Make or n8n accounts, so scenarios are read rather than guessed at.
What you already know
The integrations you are aware of. We compare that against what the logs actually show.
How it runs
Two weeks from access to delivery.
Days 1 to 2
Access and collection
Read access set up, logs collected, and your list of known integrations gathered.
Days 3 to 7
Discovery
Log and platform analysis to build the real inventory, including the callers nobody documented.
Days 6 to 9
Replacement assessment
For each caller: what it becomes after the cutover, the estimated effort, and whether it should simply be retired.
Day 10
Report and walkthrough
The inventory, a replacement plan prioritised by risk, and a session with your technical and business stakeholders.
What you get
The integration inventory
Every caller, the user it authenticates as, the models it reads and writes, its frequency and its business owner.
Exposure register
What breaks at cutover, ranked by business impact rather than by call volume.
Replacement plan
The replacement path per caller, sized in effort, including the integrations that should be retired rather than migrated.
A schedule against the deadline
A cutover order that lands before the published date, starting with whatever has the longest lead time.
The plan is executable by your team, your current integrator, or us. The report does not lose its value if you pick somebody else.
Backed by real migrations
Numbers like yours, validated on real migrations
These are three engagements where the projection actually turned into operational reality on Odoo, and the full case studies live on the migration service page.
- ManufacturingV12 → V17
Industrial Manufacturer, Texas
12custom modules carried over, zero data lost
- DistributionV14 → V18
Wholesale Distributor, Quebec
30%faster page loads once the upgrade shipped
- Professional ServicesCE → Enterprise
Consulting Firm, Brussels
0hproduction downtime during cutover
Start with the inventory
Twenty minutes to pin down your Odoo version and the integrations you know about. You leave with a scope and a firm price.
Frequently asked questions
01
How do we know if this affects us?
If anything outside Odoo reads or writes Odoo data automatically, it probably does. Zapier, Make, n8n, BI connectors, warehouse scanners and in-house scripts nearly all use XML-RPC or JSON-RPC. The question is not whether you have any, it is how many you have forgotten.
02
Can we not just wait for the upgrade?
You can, but the inventory is the work that has to exist before anything can be planned. Teams that discover their integrations during the upgrade discover them in production, broken. Making the list early costs less than finding it late.
03
Do you do the replacement work too?
Yes if you want us to, but the plan is written to be executable by somebody else. The audit fee is fixed before we start and does not depend on who performs the remediation.
04
How long does it take?
Two weeks from access to walkthrough. The limiting factor is log depth: 30 days of history produces a materially more complete inventory than 7.
05
What if we are on Odoo Online?
The question still applies. Odoo Online removes your hosting burden, not your integrations. Your automation scenarios and BI connectors use the same endpoints and go away with them.