Loading…
Loading…
Every Odoo version removes or merges modules. NonaGuard maintains a version-aware deprecation database spanning Odoo 15 through 19, so you know exactly what to fix before upgrading — and what to bill your client for.
A single deprecated module can halt an entire migration. Odoo 16 removed procurement_jit. Odoo 17 merged web_unsplash. Odoo 19 deprecated base_import_module. If these remain installed, upgrade scripts fail or silently skip critical data migrations.
Partners who discover this in staging lose weeks. Partners who scan first scope remediation upfront and protect their margin.
12+ tracked deprecations including account_cancel, procurement_jit, sale_management.
15+ tracked including pad, pos_cache, payment_ogone, web_grid.
7+ tracked including base_setup, web_unsplash, google_recaptcha.
8+ tracked including mail_tracking, partner_autocomplete, hw_blackbox_be.
5+ tracked including web_editor_legacy, base_import_module, digest.
NonaGuard connects via XML-RPC and lists all installed modules with versions and authors. Each module is checked against the deprecation registry for your current and target versions. You receive a severity-ranked report with replacement modules and migration notes.
NonaGuard combines Odoo official release notes, community deprecation trackers, and automated index updates. The registry is refreshed regularly via scheduled backend tasks.
Yes. Custom modules with manifest version numbers incompatible with your target Odoo version are flagged, along with modules depending on removed core APIs.
Absolutely — this is the primary use case. Run a scan on the client's production instance, export the PDF, and attach it to your upgrade proposal as technical scope.
Version-aware registry · Odoo 15–19 coverage