Late in 2025, a user running Odoo 19 with n8n, a popular automation tool, opened an issue on n8n's GitHub page. Nothing had broken. The automations ran and the records synced. The problem was a warning Odoo wrote to its log every time n8n connected, which ended by asking whoever saw it to "report the problem to the client making the request."
Most business owners will never read a line like that. It lives in a system log, and usually only IT looks there. But if you're an owner or planner getting ready for Odoo 20, it's worth understanding, because it's about something upgrade plans tend to leave out: the other tools that connect to Odoo from outside it.
Will Your Connected Tools Still Work After an Odoo 20 Upgrade?
Most of them will, but the clock has started. A lot of outside tools connect to Odoo using an older method that Odoo is retiring in stages. Odoo's documentation says Odoo 20 removes the first piece, which is the part some tools use to back up, copy or manage whole databases from outside Odoo. The piece nearly every connection depends on, reading and updating records like orders, stock levels and products, still works in Odoo 20 and 21. It's due to be switched off in Odoo 22, which is expected in fall 2028. For businesses on Odoo Online, the expected date is earlier, in winter 2027. The replacement is a newer connection method Odoo introduced with version 19.
Some articles say the old method is already gone in Odoo 20. That was the original plan, and the warning in the n8n case said so too, but Odoo has since pushed the date back. If you're reading upgrade advice, check it against Odoo's current documentation.
For most manufacturers, that means everyday connections will carry on after the upgrade. Tools that back up or copy the database from outside Odoo may stop, so ask your IT team or partner about them before go-live. Some businesses use exactly that kind of tool to make the test copy an upgrade needs.
Why Should This Change How I Plan an Odoo 20 Upgrade?
Most upgrade plans are built around one date, the weekend the live system moves to the new version, and testing, training and sign-off are all counted back from it. The connection schedule doesn't fit on that calendar. Since everyday connections keep working through Odoo 20 and 21, nothing forces anyone to deal with them this year, and that's the risk. The bill comes due at the upgrade after next, when updating every connection lands in the same project as a new version's changes. Connections run to their own timetable, and the cheapest time to update them is while you're already testing for Odoo 20.
On Odoo Online the timetable is tighter. Online moves through Odoo's in-between releases, and its cutoff is expected in winter 2027, only a little over a year away. If you've been weighing whether to wait for Odoo 20 or move sooner, add this to the list. The longer you stay on an older version, the longer the old connections stay too, right up until the upgrade that ends them.
Updating a connection during Odoo 20 testing means it's checked once, by people who are already running order-to-delivery scenarios. Leave it, and it will likely need a separate round of testing in 2027 or 2028, likely in the middle of another upgrade. Our article on what manufacturers should retest after an Odoo 20 upgrade goes through that testing in detail. The suggestion here is simply to fold the connection work into it.
Which Connections in a Manufacturing Business are Likely to Be Affected?
Mostly the ones out at the edges of the plant, where whoever plans the upgrade is least likely to see them. In a manufacturing business, the tools talking to Odoo usually go well beyond the online store and the accounting export. Think of a label printer that pulls lot numbers when a pallet is finished, or a scale that records quantities against a work order. There might be a shop floor tablet app built years before Odoo's own shop floor tools existed, an export that sends bills of materials over from engineering, or the spreadsheet a planner opens every morning to pull up the day's manufacturing orders. If you plan production, you probably use a couple of these without thinking about them.
Plenty of these were set up in a hurry by someone who's since left, and they've worked well enough that nobody has touched them since. The older method was the standard way to connect to Odoo for years, so it's what most of them were built on.
So this is a planning job first and a technical job second. Nobody can schedule an update for a connection that isn't on a list.
Why Does This Matter More For Canadian Manufacturers Right Now?
Because many of them are adding customers, suppliers and logistics partners at the same time, and new partners usually mean new connections. The federal government's 2026 economic update points to an Export Development Canada survey from March 2026, where 65% of exporters said they planned to move into new markets within two years. The same update describes firms shifting toward non-U.S. suppliers for their inputs as tariffs reshape supply chains.
For a manufacturer, a new market brings its own systems with it. There's the distributor's ordering portal, the freight forwarder's booking platform, the customs broker who wants shipment data in a particular format, and the new supplier sending shipping notices. A lot of those links will be set up quickly to win or keep a customer, by whoever has time that month.
The two years in that survey overlap closely with the time left before the old method shuts off. Hook up a new European distributor the old way in 2027, and you could be rebuilding that link a year or so later. Using the newer method from the start is usually cheaper, because otherwise you pay for the same connection twice, and the second time is on a deadline.
What Should Owners and Planners Ask For in an Odoo 20 Plan?
Every connection needs to be on a list, with an owner and a date, and the work should sit inside the testing you've already planned. When you talk to your IT team or partner, ask for:
- A list of every connection. That means every system, device, script and spreadsheet that reads from or updates Odoo, including the ones IT never set up. If you're already on Odoo 19, its system log flags many of them, so you won't be starting from scratch.
- A named owner for each one. This should be someone who knows what the connection does, who set it up and who can change it. Connections nobody owns are the ones that tend to fail without anyone noticing.
- A straight answer on backups and test copies. Find out whether any tool backs up or copies your database from outside Odoo. Those are the ones Odoo 20 affects directly, so they need sorting before go-live.
- A separate key for each connection. The newer method signs in with access keys. If every connection has its own, it's easier to see what each one is doing and to switch one off without disrupting the others.
- Connection updates booked into Odoo 20 testing. You're already paying for test scenarios, sign-off and a fallback plan, and updates done alongside them only need testing once.
- New partners connected the new way. Any link to a new customer, supplier or carrier should use the newer method from day one. Check your Odoo plan too, since Odoo's documentation says outside access to your data is only available on Custom plans.
What Does a Complete Odoo 20 Upgrade Plan Look Like?
It covers Odoo and everything plugged into it, and it accepts that the two run on different timetables. For manufacturers, upgrade planning has mostly been about protecting the go-live weekend and getting manufacturing orders, stock and accounting across in one piece. That's still the hard part. But those warnings already sitting in Odoo 19 logs are a reminder that a plant runs on more than the software being upgraded. With Odoo 20, Odoo has put in writing when the old way of connecting ends. Plans that use that now get to decide when the connection work happens. Plans that don't will find the date has already been set.