Upgrading to Odoo 20: The Seven AI Settings to Check the Morning After

After an upgrade to Odoo 20 (released 24 September 2026), check seven AI settings before the first working day: the daily AI Fields scheduled action (active by default), IAP credits, the AI provider, server actions with Use in AI ticked, tools marked Available in MCP, users’ MCP API keys, and which agents hold the Create or Update Records skills. The test database never runs the crons.

At a glance

• Who it is for: Australian businesses on Odoo 19 Enterprise with an upgrade to Odoo 20 scheduled or just completed, on Odoo Online, Odoo.sh or on-premise, and the person who owns the morning-after checklist.
• Problem it solves: the upgrade itself is Odoo’s job. What arrives switched on, who holds which key and what will run overnight without anyone in the room is yours, and none of it shows up on the test database.
• Platforms: Odoo 20 Enterprise with the AI application. MYOB Acumatica is not in scope; its AI features are administered inside the product and we cover them in our MYOB Acumatica AI post.
• Trigger: the morning after the production upgrade, before staff log in, then again a week later once the first scheduled runs have happened.
• Inputs read: Settings > Technical > Automation > Scheduled Actions, the IAP services page, Settings > Technical > Server Actions, each AI agent’s skills and sources, and each user’s API keys.
• What the checklist produces: a one-page record of what is on, what is off, who holds which key and when it expires, filed in your AI agent register.
• Approval gate: the operations or finance manager signs each line. Nothing AI-related runs on a schedule in production until a named person has decided it should.
• Audit trail: the signed checklist plus Odoo’s own scheduled action logs and automation chats.
• Typical cycle time: 60 to 90 minutes for a database with one or two agents; longer if staff experimented with AI server actions on Odoo 19.
• What it never does: change the upgrade plan, touch custom module code, or decide for the business what the agents may write. It records and asks.
• Typical cost: no licence cost; every Odoo 20 AI feature consumes IAP credits per the Odoo 20 release notes, so the budget line is credits. We include this checklist in an upgrade engagement; as a stand-alone review it sits well under the $5,000 ex GST pilot figure on our AI agents for ERP in Australia hub.
• Typical timeline: one morning, then a 30-minute recheck after the first week.
• Last verified: 5 October 2026 against the Odoo 20 release notes, the 20.0 upgrade documentation, the 20.0 AI fields, AI agents, AI server actions, MCP server and automation rules documentation, and the 20.0 in-app purchase documentation.

We have been through the Odoo 20 AI documentation twice now, once for the built-in MCP server and once for agents summoned by scheduled actions. This post is the short, practical layer underneath both: the list we work through on the first morning after a client’s database comes back from Odoo’s upgrade service. It assumes the upgrade went fine. Our Odoo version upgrade guide covers the upgrade itself, and the Odoo 20 release post covers what changed for Australian sites generally.

Why doesn’t the test database catch any of this?

Because Odoo’s upgrade process neutralises it. The 20.0 upgrade documentation says that in an upgraded test database, scheduled actions are disabled, outgoing mail servers are archived and replaced with a fake one, and bank synchronisation is off. That is the right design for a test copy. It also means the two things most likely to surprise you on Odoo 20, the daily AI Fields cron and any agent an automation rule summons, have never run against your data by the time you sign off the test.

So the test database proves the upgrade. It does not prove the AI. Treat the first production week as the AI pilot it actually is: crons off until a person has looked at each one, then on one at a time.

What should you check the morning after an Odoo 20 upgrade?

Seven settings, in the order we check them. The table is the checklist; the sections after it say why each line matters.

The AI Fields cron

The AI fields documentation is plain: a scheduled action runs once a day to fill text and property AI fields that are empty, and it is active by default. If the only AI field in your database writes product descriptions, let it run. If someone added an AI property field to a model that feeds a report, a quote or a customer document, that field will be recomputed overnight, from a prompt, with credits spent, and nobody will have approved the words. Find every AI field first (Studio and property fields are the two places they are added), then decide.

Credits

Odoo 19 sites did not all budget for AI. On Odoo 20, the release notes say all AI features need credits bought via IAP. The in-app purchase documentation describes the balance page under Settings > Contacts > Odoo IAP > View My Services and the email alert for low credits. Set the alert, name the recipient, and put the monthly figure in your running-cost line; our AI agent running costs post has the method.

The provider

The release notes describe automatic model selection once an AI provider is chosen. As at 5 October 2026 Odoo’s own AI API keys page in the 20.0 documentation is marked under construction, so we are not going to tell you which providers appear in your settings or what keys they need; look at the screen and record what it says. What you can decide today is the privacy question: finance and customer records will be sent to that provider when an agent or an AI field runs, so check where it processes data against your obligations under the Australian Privacy Principles, in particular the cross-border disclosure principle, and write the answer down.

Server actions with Use in AI, and tools in MCP

A tool is a server action with Use in AI ticked, and the AI server actions documentation says a called tool executes unconditionally unless the code itself prevents it. Anyone who experimented with AI server actions on Odoo 19 has left those ticks in place, and they came through the upgrade. List them, read the code, and either un-tick the ones that write or rebuild them so they stop at a draft or an activity, the pattern in our approval-gate build note.

The MCP server documentation says the database exposes five tools to external clients by default (retrieve initial context, get models, get fields, search, read group) and hides the rest, including Create Records and Update Records, until an administrator ticks Available in MCP. Confirm that is still the state of your database. The Readonly Tool checkbox does not hide a tool; it only tells the client the tool is safe to call without asking. Do not tick it on anything that writes.

Keys and agents

MCP keys are created by each user under My Preferences > Security, with an MCP scope and an expiry the user chooses. Every connected assistant has a person at the other end of a key, so the question is who. Ask every user who has connected an assistant, record the expiry, and make listing the key in the register a condition of keeping it.

Then open each agent in the AI app. Odoo 20 renamed topics to skills, and the AI agents documentation says an agent with no skills can only provide information and cannot change the database. The preconfigured skills include Create Records and Update Records. An agent that was information-only on 19 is still information-only on 20, but check, because a skill is one click to add and the agent will use it.

A worked example: the Monday after a Queensland wholesaler’s upgrade

Picture a Queensland building-products wholesaler on Odoo.sh whose database comes back from the upgrade service on a Saturday. On the Monday, before the sales desk opens, the list is run with the operations manager. The AI Fields cron is active, and the database has two AI fields: a Studio field writing website descriptions for new products, which stays, and a property field on quotations that someone added in August to draft a “delivery notes” paragraph. That one is deactivated until the sales manager approves the prompt, because the paragraph prints on the customer’s quote.

Three server actions carry Use in AI over from Odoo 19. Two read data. The third updates the expected delivery date on a sale order from an AI prompt, with no check in the code. The operations manager un-ticks it on the spot, and it goes on the rebuild list as a draft-and-activity tool. MCP exposure is at the default five tools. Two staff created MCP keys with no expiry during the 19 experiments; both are recreated with a six-month expiry and added to the register. Credits: the account has a small balance left from Documents digitisation, so a monthly figure and a low-credit alert to the finance manager are set before anyone asks an agent anything. Ninety minutes, seven lines signed, and the first scheduled run happens on the Tuesday with someone watching the automation chat. That is the shape of the morning we build into every Odoo 20 upgrade we scope.

The upgrade is the part people worry about and the part Odoo has largely solved. The morning after is where the surprises are, because the test copy switched the crons off and nobody switched their judgement back on. Ninety minutes with the list is cheap insurance.

Bill Alvarez, Practice Manager, Auboros

What else changes about AI governance on Odoo 20?

Two things worth a line in the register. Conversations with agents are stored for up to 30 days after the last message, per the release notes, so anything a staff member pastes into an agent chat, including customer details, lives in the database for a month; your retention and de-identification practice under the Privacy Act should say so. And the automation rules cron, Automation Rules: check and execute, runs every four hours by default and must be run manually once when a time-based rule is created, or the rule can fire on historical records. On 19 that caught the odd follow-up email. On 20 the same rule can summon an agent.

We like Odoo 20. The AI additions are useful, and the permission model is tidier than most of the third-party agent tooling we get asked about. The point of the list is the same point every post in this pillar makes: a person decides what runs, a person approves what writes, and the record says who. That is how our AI agents for ERP in Australia are built, and the upgrade morning is the cheapest moment to put it in place.

Goes well with

• Odoo 20 agents in automated and scheduled actions: what can now run overnight, and where the person goes back in.
• Odoo 20’s built-in MCP server and who it runs as: the key, scope and exposure questions in full.
• How the Odoo version upgrade process works in Australia: the upgrade itself, the free upgrade service and when to schedule it.

Upgrading to Odoo 20 and not sure what will run on day one?

Auboros is an Odoo partner in Brisbane that runs AI agents over Odoo for businesses across Queensland and the rest of Australia, and we work through this list as part of every Odoo 20 upgrade. If your upgrade is booked or just landed, book a free consultation and we’ll go through the seven settings with you. No obligation, and if everything is already off and recorded, we’ll say so.