Every year, the same thing happens. Businesses know their Odoo version is getting old, they agree the upgrade needs to happen, and then the year fills up with month-ends, audits, peak season and a hundred other priorities. Before long it's February again and nothing has moved.
For most South African businesses, the December shutdown is the one window in the year where an upgrade fits naturally. Fewer people are logged in, month-end is out of the way, and there's time to test properly without a sales team waiting on the system.
The catch is that the work that makes a December upgrade go smoothly has to start in November.
Why December works
An Odoo upgrade isn't just a technical job. Your team has to test it, learn what's changed and trust the new system before they rely on it. That's hard to do in the middle of a busy trading month.
December gives you:
Low system activity. With most staff on leave, fewer transactions are happening while the database is being moved.
A clean cut-off. November month-end is closed, so there's a natural point to upgrade from.
Breathing room in January. Most businesses ramp up slowly in January, which gives your team time to settle into the new version before things get busy.
A head start on year-end. Many South African companies close their financial year in February. Upgrading in December means you run year-end on the new version, instead of upgrading straight after closing a year on the old one.
Who should be planning now
If you're on Odoo 17
Standard support for Odoo 17 ended in September 2026, when Odoo 20 was released. Odoo only supports the three most recent major versions, which are now 18, 19 and 20.
Your system keeps working, but Odoo 17 no longer gets standard support. Based on how Odoo has applied its legacy surcharge so far, partners expect Odoo 17 subscriptions to start attracting it from around March 2027. Upgrading this summer means you avoid that entirely.
If you're on Odoo 16 or older
You're likely already paying for it. Since April 2026, Odoo has charged a 30% surcharge on Enterprise subscriptions running on legacy versions, for contracts renewed after 4 July 2025.
On a R300,000 annual subscription, that's R90,000 a year. An upgrade is a once-off cost, but the surcharge keeps coming every year until you move.
If you're on Odoo Online
Odoo Online databases are upgraded on Odoo's own schedule, and they aren't affected by the surcharge. This guide is mainly for businesses on Odoo.sh or self-hosted (on-premise) Odoo.
Which version should you upgrade to?
For most businesses, the answer is Odoo 20.
Upgrading to Odoo 19 now would only buy you support until September 2028, so you'd be back here in under two years. Odoo 20 is supported until late 2029 and includes the newest features, including AI agents that can create and update records, offline working on mobile, and simplified access rights.
Skipping versions is normal. Odoo's upgrade service can move a database across several versions in one go, so going from 16 straight to 20 doesn't mean four separate projects.
What changes in Odoo 20 that affects your upgrade
Most of Odoo 20 is improvements your team will simply notice and enjoy. But a few changes need attention during the upgrade itself, especially if your system has been customised.
Security and access rights
Odoo 20 removes record rules and replaces them with a domain set directly on each access right. If any of your custom modules include record rules, their security has to be reviewed and retested before go-live. This is the change most likely to cause trouble in a customised database.
Accounting structure
Account groups are replaced by parent accounts, and account codes become optional.
Asset models are replaced by depreciation models.
Payment statuses are renamed: what used to show as "In Process" is now "Paid", and what used to be "Paid" is now "Reconciled".
The separate Employee Expenses menu is gone. Approved expenses now create draft bills.
None of this is difficult, but any reports, filters or exports your finance team uses that rely on the old names or structure need to be checked.
Other things to check
Chatter tracking: tracking values have been removed and the tracking message is now generated on the fly. If you have custom reports built on tracking data, they need a look.
Icons in custom views: Font Awesome icons have been replaced by Material Symbols, which matters for anyone maintaining custom screens.
AI credits: all AI features in Odoo 20 now use IAP credits. If you plan to roll out AI agents, budget for credits from the start.
How a safe upgrade works
The golden rule: never upgrade your live database first.
Assess. List your installed apps, custom modules and integrations, and decide which customisations are still needed. Odoo 20 may now do some of them as standard.
Test upgrade. Upgrade a copy of your database to Odoo 20. Your live system keeps running as normal while this happens.
Fix and adapt. Update custom modules for Odoo 20, with special attention to security rules and anything that touches accounting.
User testing. Key users from each department work through their normal daily tasks on the test copy and report anything that looks wrong.
Training. Show your team what's changed, especially the renamed payment statuses and the expense flow.
Production upgrade. Upgrade the live database during the shutdown, then do a final check.
Support in January. Have support on standby as your team returns and starts working on the new version.
Steps 1 to 5 are where the real work happens, and they all need to happen before December.
Your November to January timeline
When |
What happens |
|---|---|
Early November |
Confirm your version, list customisations and integrations, book your upgrade slot |
Mid to late November |
Run the test upgrade and update custom modules |
Late November to early December |
User testing on the test copy, fix issues, train key users |
December shutdown |
Upgrade the live database and run final checks |
January |
Support as your team returns |
If you start in December instead of November, the testing gets squeezed, and that's when upgrades go wrong.
The bottom line
The December shutdown is the most practical upgrade window South African businesses get all year, but only if the preparation starts now. Whether you're on Odoo 17 and want to stay ahead of the surcharge, or on Odoo 16 and already paying it, a planned upgrade over the break is far less painful than a rushed one in March.
At AP-Systems, we've been an Odoo partner since 2013, with more than 70 implementations behind us. Our development team is fully in-house, so the people who review your custom code are the same people who support you afterwards.
Our December and January upgrade slots are limited. Book
your upgrade assessment today.