Migrating from Odoo 18 to Odoo 19: which OCA modules are available

When you merge duplicate contacts, this module automatically consolidates their linked user accounts: it keeps one login, archives the others, and combines their access rights.

Adds phone-number tools to Odoo: a Dial button next to phone fields, automatic international reformatting of stored numbers, and a wizard to clean up all existing numbers. It also lets Odoo find a partner from an incoming caller's number.

Lets administrators create different types of portal users by defining portal-type groups, so portal access can be tailored (for example vendors versus customers) using Odoo's normal group mechanism.

Stores every remote (external IP address) that connects to Odoo, with its hostname and whether it can be resolved on the network. It also blocks logins coming from remotes that cannot be identified.

When a report is generated from an email template, this module prevents it from being sent to a printer. It only affects automatic report generation triggered by mail templates.

This module provides the technical foundation to build and publish REST APIs for Odoo. It adds a REST API menu with a Swagger documentation page where developers can explore the available endpoints.

Adds API key security information to the automatically generated OpenAPI documentation of REST services, so developers see that an API-KEY header is required.

This module lets developers use Pydantic data models as input and output for REST API methods in Odoo, adding automatic validation and OpenAPI documentation. It does not add any screen or menu for end users.

Lets users search any record that uses Odoo chatter (like tasks, tickets or issues) by the content of its messages, notes and emails, not just by the record's own fields.

This base module lets administrators define alternative numbering sequences for documents, chosen automatically by matching rules on the document's own values. It does nothing on its own; other modules must enable it for each document type.

Lets you define reusable sequence templates and generate one numbered sequence per company in a single step, automatically filling in company details such as name or registry number into the prefix and suffix.

Technical module that lets Odoo store lists (not only dictionaries) in serialized fields. It changes how serialized field values are converted when read into memory, so lists are saved correctly.

This technical module adds a flag to mark actions as temporary and automatically deletes them one hour after creation. It does not add any visible screen or menu by itself.

Lets you store values that change over time (rates, thresholds, flags) and read the right value for any given date. Access is through a new Time Parameters menu under Technical settings.

Adds a Transaction ID field to sales orders and invoices so you can record the payment reference from a bank or payment provider. The value entered on a sales order is automatically copied to the invoice created from it.

This module provides a technical foundation for giving Odoo records clean, human-readable web addresses (URLs) instead of numeric IDs, and it automatically keeps old addresses working by redirecting them when they change.

Adds an "Effective permissions" button on the user form that opens a list showing, per model, whether the user can create, read, write or delete records and the record rules that restrict those operations.

Lets administrators clear the login password of one or more users from the Users list, so those users must sign in with another method (for example single sign-on).

Lets each user or the whole company override how dates, times, week start and number separators are displayed in Odoo, instead of being forced to use the language defaults.

Lets administrators group roles into profiles and lets users switch between their allowed profiles from the top bar, so the active roles (and therefore menus and permissions) change instantly.

Separates the user login from the email address in Odoo. The user form now shows a 'Login' label and a visible Email Address field, and the login page asks for a Login instead of an Email.

Lets administrators create and manage a library of predefined warning and blocking messages, so the same wording is reused consistently across Odoo.

Track customer business requirements from the first story to approval, with scenarios, gaps, test cases and a portal page where customers can follow progress.

Create a Business Requirement directly from a CRM opportunity and see all requirements linked to a lead. The opportunity form gets a Create Business Requirement button and a counter button listing its requirements.

Adds deliverable lines to business requirements so you can list the products and services a customer will receive, price them from a pricelist, and show them to the customer in the portal and on the printed report.

When a business requirement is approved, its deliverables can automatically become project tasks, either in a chosen project or in a brand-new project created for the requirement.

Adds a RICE scoring section to business requirements so you can rank requests by Reach x Impact x Confidence / Effort. The score is stored, shown in the form, list and kanban views, and can be used to filter and sort requirements.

Lets salespeople turn a Business Requirement into a quotation, using its deliverables as sales order lines, and links quotations back to the requirement.

Moves the Description field of the calendar event form onto its own dedicated tab, giving users much more room to write long or detailed event descriptions.

Adds a Company field to calendar events so each event belongs to a specific company. Users only see events of companies they are allowed to access, plus events with no company.

Colorize calendar events automatically based on the color of their first event category, and let administrators set a color on each event type.

This module adds a wizard that lets you export your Odoo calendar events to a single .ics file, which you can then import into other calendar applications.

Lets users import .ics calendar files into Odoo Calendar, creating or updating events and optionally removing previously imported events that are no longer in the file.

Lets administrators store carrier account credentials (account and password) in server configuration files instead of typing them in Odoo, so production and test servers can use different carrier logins.

Lets administrators define reusable "field swap" rules that change a field value on selected records and automatically propagate the same value to related records. Each rule can be protected by constraints and restricted to certain user groups.

Adds a new 'Formula' commission type so you can calculate agent commissions with a custom formula instead of fixed percentages.

Lets you record sanitary registry numbers for your company and assign them per product category and warehouse, and print them on reports.

Adds a hidden 'Connectors' tab to product and product variant forms, ready to be filled in by other connector modules.

Adds Elasticsearch as a search engine backend in Odoo, letting you configure the connection and manage indexes that are exported to an Elasticsearch server.

Adds ready-made import types so you can load products, variants, attributes, categories, packaging and supplier info into Odoo from CSV files using the Connector Importer framework.

Adds a new CSV import source that reads files from an SFTP server, and can automatically move each processed file to a success or error folder depending on the import result.

Connect Odoo to external search engines by defining backends, indexes and per-record bindings, then recompute, export and delete index data in the background. It is a base framework: the actual search engine connection is provided by other addons.

Adds Typesense as a search engine backend in Odoo, so users can configure a Typesense server and export indexed data to it.

Lets you assign a brand to a contract and automatically carries that brand over to the invoices generated from it, so branded contracts and their billing stay consistent.

Adds a forecast of future contract invoices, showing expected amounts and invoice dates per contract line, and lets you view them in a pivot, graph or list report.

Adds the brand to contract forecasts, so each forecast line shows the brand of its contract and updates automatically when the contract's brand changes.

This module makes contract forecasts refresh automatically when you change how a contract line calculates its quantity, so the forecast stays in line with the new quantity rule.

Adds a "Manually Invoiced" option on contracts so they are skipped by automatic invoice generation and can instead be invoiced on demand from Accounting. A company setting turns the feature on or off.

Lets you hide the detail lines, subtotals and line amounts of sections on contracts, their printed reports, the customer portal and the invoices generated from them.

Lets you mark contract lines as deferred so they are not invoiced while their start date is unknown, then activate them later with a start and end date. A company setting can defer new contract lines automatically.

When a contract line is deferred, this module blocks the successor, stop and cancel actions on it and greys it out in the contract lines list, so users cannot act on a line that has been postponed.

Lets you attach a direct debit mandate to a contract so that invoices created from that contract automatically carry the mandate. The mandate field only appears when the contract's payment method requires a mandate.

Limits the payment modes you can pick on a contract to those allowed for the contract's brand. The allowed list is taken from the brand configuration and applied automatically on the contract form.

Lets you revise contract line prices by applying a percentage change or a fixed new price, creating a new line and closing the old one the day before the new start date.

When enabled, contract invoicing and contract line renewals are split into background jobs instead of being processed all at once, and a new button lets you enqueue invoice creation from the manual invoice wizard.

Lets contracts generate sales orders instead of invoices on their recurring schedule, with an option to confirm those orders automatically. Users can also see how many sales orders a contract has produced and open them from the contract form.

Lets you add pending sales orders to a recurring contract invoice when they share the same analytic account, either merged into the contract invoice or as separate invoices.

When a sale order with a banking mandate is turned into a contract, the mandate is automatically carried over to the contract.

Lets you choose a different payment mode for contracts generated from sale orders than the one used for invoices, controlled by a company-level setting.

When a contract is created from a sale order, the transmit method chosen on the sale order (email, post, portal, etc.) is automatically copied to the contract.