Odoo 20 arrived in September 2026, and its most consequential changes are not in any one app. According to the release notes, AI agents can now create and update records, including from an uploaded file, and they can be summoned by automated and scheduled actions. The same release lets you connect to your database through the Model Context Protocol.
Those are useful abilities. They also move AI from something that answers questions to something that changes business data, which calls for a different kind of preparation.
What changed
- Agents can write. They can create and update records, not only read and summarise.
- Agents can run unattended. Automated and scheduled actions can summon them without someone typing a prompt.
- Outside AI can connect. Odoo’s MCP documentation describes the database acting as a server, with server actions exposed as tools. OAuth is the recommended authentication for internal users, and portal users authenticate with an API key.
- AI has a metered cost. The release notes state that all AI features now require IAP credits.
Seven things to decide before upgrading
- Which records may an agent write to? List them by model. Anything not on the list stays read-only.
- Who does an agent act as? Give each automation its own limited user. A shared administrator key turns one mistake into a company-wide one.
- Which server actions will you expose over MCP? Each exposed action is a capability you hand to an outside client, so expose few and review them like code.
- What needs a person’s approval? Anything hard to reverse, such as posting entries or sending messages to customers, should begin as a draft.
- What will the credits cost? Estimate tasks per month and run a measured pilot. Scheduled agents can consume credits with nobody watching.
- How will you review what happened? The release notes say agent conversations are stored for up to 30 days after the last message. If you need longer for audit purposes, plan for it.
- What about text inside documents? An agent that reads uploaded files can meet instructions planted in them. Test this before granting write access.
Test the upgrade on a copy first
None of this replaces the ordinary upgrade work. Run the upgrade on a copy of your database and check every custom module against it. Then look at workflow changes, too: the accounting notes alone include renamed payment statuses and a requirement that bank-affecting entries originate from bank transactions. Finance staff should see those before go-live, not after.
Our suggestion
Treat the upgrade and the agents as two projects. Stabilise the upgrade first, then introduce one agent at read-only level, on one process, with a person checking its output. Raise its permissions when the evidence supports it. Our agentic AI page sets out the permission levels we use.
Sources: Odoo 20 release notes; Odoo 20.0 documentation, AI MCP server. Check both against your edition and hosting type, since details can change.