Fixed price · read-only · delivered in days

Know what’s broken — and what upgrading will cost — before you sign anything.

Two productized engagements, run by the maintainer of odoo-mcp with the same open-source tooling — read-only, no module installed, evidence-first. Every number in the report comes from a tool call against your database, not from a slide deck.

01 /

Two packages. Fixed price. No scope creep.

Before AI · before migration

AI-Ready Data Audit

48-hour turnaround · any Odoo 16–19 · CE & EE
$490 $690
intro price — first 10 engagements

Messy data is why AI pilots answer confidently and wrongly, and why migrations blow their budgets. Find out exactly how messy — per model, with record IDs — before you spend $15k+ on remediation.

  • Duplicate scan across partners, products, and the models you pick
  • Missing required fields & orphaned references, counted and listed
  • Format anomalies — emails, VAT/tax IDs, phone numbers
  • Ranked remediation worklist your team (or any partner) can execute
  • HTML report + 30-min walkthrough call
Book the audit — $490
Before you commit to an upgrade quote

Migration Pre-flight

5 business days · 16→17→18→19 paths · CE & EE
$990 $1,500
intro price — first 10 engagements

Odoo now surcharges +25% on versions older than three releases, and upgrade quotes without an audit are guesses. This is the audit: what breaks, what it costs, in a report you can hand to any implementation partner.

  • Addon source scan of your custom modules against the target version
  • Upgrade risk report — every blocking issue and warning, with file references
  • Action taxonomy per finding: no_action · needs_review · needs_script
  • Data-quality gate (the full audit on the left, included)
  • JSON-2 readiness check — XML-RPC call sites flagged before Odoo 22 removes them
  • Scoped effort estimate + 60-min walkthrough call
Book the pre-flight — $990
02 /

How an engagement runs.

15-minute intro call

Scope the models (audit) or addons + target version (pre-flight). You create a read-only user + API key — we send instructions, it takes five minutes.

We run the tooling — nothing gets installed

The audit runs over XML-RPC/JSON-2 with the open-source odoo-mcp server: field-level ACL on, write gate off, every call logged. Your database is never modified.

Report + walkthrough

You get the HTML report, the raw worklist (CSV), and a walkthrough call. Every finding cites the records or files behind it.

Credentials deleted

We revoke and delete the access after delivery and confirm it in writing. Want fixes executed too? That’s a separate, gated engagement — never bundled silently.

03 /

Read-only by design, not by promise.

The same guarantees the open-source server enforces:

  • Write gate stays off — create/write/unlink are blocked at the server layer, not by policy
  • Field-level ACL — sensitive columns (salaries, bank accounts) excluded before anything reaches an LLM
  • JSONL audit log of every call, shared with you at delivery
  • Read-only credentials recommended and verified at kickoff
  • No data retention — working copies and access deleted after the engagement
  • Open-source tooling — audit the code that audits you: github.com/tuanle96/mcp-odoo
≡

Run an agency? White-label these reports for your own clients — you sell the engagement at your rate, we run the tooling, your logo on the deliverable. Or skip the middleman entirely: the same reports arrive automatically every week with Odoo MCP Cloud. Mention “partner” when you book and we’ll talk margins.

04 /

Fair questions.

Our Odoo is on-prem behind a VPN. Can you still audit it?
Three options: temporary IP-allowlisted access, a VPN account for the engagement window, or — if nothing may leave the network — you run the open-source tooling yourself with our runbook and we analyze the exported reports. Same deliverable, same price.
What exactly can you see with the credentials?
Whatever the read-only user you create can see — Odoo’s own record rules still apply — minus the fields we exclude via field-level ACL before any tool result is processed. The audit log we hand over shows every single call made.
What if the audit finds nothing significant?
If the report contains nothing actionable — no duplicates worth merging, no upgrade blockers, no data risks — you get a full refund. It hasn’t happened yet on a database older than a year.
Do you also do the migration / the cleanup?
By design, no — the report is written so any implementation partner (including your existing one) can execute it, which keeps the audit honest: we have no incentive to inflate findings. Supervised remediation of specific worklist items can be scoped separately.
How do I pay?
Card checkout link (or invoice for companies) after the intro call — you pay only when the scope is confirmed. 50% refund if we miss the deadline.