ERP vendor update cadences compared: what Epicor, IFS, Sage, Acumatica and Odoo releases mean for your regression testing

If you run Epicor, IFS, Sage, Acumatica or Odoo, you probably spent the implementation worrying about go-live. The thing you will live with for the next ten years is the vendor’s release calendar. Every one of these vendors now ships on a fixed rhythm, and in every case the vendor runs the upgrade while the customer proves that its own processes still work. This guide compares the calendars, shows what each vendor gives you to test with, and ends with a regression routine that works on any of them.

Why the calendar matters more than the go-live

Most ERP programs are not wrecked by technology. In Panorama Consulting’s 2026 ERP Report, more than a quarter of organizations said their project ran over budget and almost a quarter said it ran over schedule; the most common reason for schedule overruns was organizational issues such as governance and process redesign^[20]. The same report warns that SaaS ERP brings frequent updates and evolving functionality that need clear ownership, and that after go-live it is common to find nobody owns security roles or change requests^[20]. Release testing is one of those ownerless jobs unless you assign it.

The calendars, side by side

IFS Cloud: two releases and twelve service updates a year

IFS describes its model as twice-yearly releases with monthly service updates^[1], and 26R1 is the current release on its releases page^[2]. The useful part for testers is Release Update Studio. In a June 2026 answer on the IFS Community, IFS staff explained that requesting a release update creates parallel branches of your baseline and solution in the Build Place, while production and non-production environments stay untouched until you create and deploy a delivery. They also noted that if you change the target service update, or add customizations after running the Impact Assessment, the assessment should be run again^[3]. Treat the Impact Assessment output as the start of your regression scope, not the end of it.

Epicor Kinetic: the cloud calendar is becoming the only calendar

Epicor announced in January 2026 that the final on-premises Kinetic feature release will be 2028.1, tentatively in January 2028, with Active Support to the end of 2029; new features after that go to Epicor Cloud only^[4]. Kinetic releases are named by year and release, such as 2025.2 in October 2025, which Epicor paired with an upgrade preparation webinar^[5]. Users on the EpiUsers forum reported the 2026.1 cloud upgrade hitting Pilot on June 4–6, 2026 and production on July 10–12^[6], and discussed an Epicor webinar on moving Kinetic cloud to monthly releases, without agreement on whether monthly updates would carry new features or only fixes^[7]. Those are user reports, so confirm your own dates on EpicWeb. The practical point stands either way: the gap between Pilot and production is your regression window, and your BPMs, Application Studio layers, BAQ reports and DMT import templates are what you are testing in it.

Acumatica: a predictable six-month lag

Acumatica 2026 R1 became available in March 2026 and 2026 R2 in October 2026^[9],[10]. Under the Always Current program for SaaS customers, upgrades happen about six months after a major release so a service pack is available, with roughly 90 days’ notice and reminders at 60 and 30 days. Acumatica says major upgrades need sandbox testing, customization validation and user training, and lets customers on some editions upgrade once a year in a chosen half-year window^[11]. Its customization platform checks each customization project for compatibility with the new version when you publish it, and the vendor advises doing that on a fresh instance of the target version before upgrading production^[12].

Sage Intacct: four releases a year, and no opting out

Sage Intacct releases quarterly, updates every customer automatically and offers no version choice; 2026 Release 2 arrived on May 8 and Release 1 on February 13^[13]. Preview companies open about three weeks before each release for customers enrolled in the Preview Program, and are deleted when the preview ends. Sandboxes are copies of production but cannot be refreshed more than four times per subscription period, and several features, including Fixed Assets, Collections and Advanced Audit Trail, are not available in them^[14]. Sage’s own pre-release checklist tells customers to review permissions and roles before each release^[13], and its help warns that import templates are updated with new releases and an older template might not work^[15].

Sage X3: you choose, within 24 months

Sage X3 Version 12 moved to bi-annual releases in November 2022, expected around May and November. Each release gets 24 months of maintenance: six months Current, twelve Standard and six Extended^[16]. That makes X3 the most customer-controlled calendar here, which also means the discipline is yours: plan at least one upgrade a year and a full regression cycle with it.

Odoo: a major version every year and a hard deadline

Odoo supports each major version for three years. Odoo 20.0 was released in September 2026, Odoo 19.0 in September 2025, and Odoo 17.0 left standard support in September 2026. On Odoo Online, SaaS versions arrive every two to three months^[17]. A database on a major version must upgrade every two years, and one on a SaaS version must upgrade a few weeks after the next is released; if no action is taken by the due date, Odoo triggers the upgrade. Custom modules must be ported before the database can be upgraded^[18].

Odoo’s upgraded test database is a good tool with one catch: it is neutralized. Scheduled actions are disabled, outgoing mail goes to a fake server, payment providers and carriers are set to test mode, and bank synchronization is off^[18]. If your business depends on any of those, they need explicit tests of their own. Odoo publishes a basic checklist and an end-to-end example (buy, receive, sell, ship, invoice, credit note, reports) that is a sensible starting suite^[18].

What changes between vendors, and what does not

The windows differ: about three weeks on Intacct, about 90 days of notice on Acumatica, up to 24 months on X3. The tools differ: an Impact Assessment on IFS, compatibility validation on Acumatica, a neutralized test database on Odoo. What does not differ is what breaks. Vendors test their standard product before they ship it. They do not test your customizations, your ISV add-ons, your integrations, your report layouts, your import templates or your role design. That list is your mandatory regression scope for every release, on every platform.

Data imports deserve a special mention because they are easy to forget. Epicor’s Data Migration Tool ships more than 60 import templates and validates data against business logic^[8]; Odoo’s import screen has a Test button that validates the file before importing^[19]. Both are useful, and both run through logic that can change in a release. Re-validate every recurring import after each update.

A regression routine that works on any of these calendars

Then do the arithmetic. If your regression cycle takes longer than the window your vendor gives you, you have three options: reduce scope by risk, add people for every release, or automate the critical path. On a quarterly calendar with a three-week preview, only the last one scales.

Finally, report honestly. When Birmingham City Council went live on Oracle in April 2022, its auditors later found that testing was incomplete and the steering committee had been told there were no open defects except intermittent issues; the potential bill for the program reached about £130 million against an original estimate of around £20 million^[21]. A release sign-off should say what was not tested as clearly as what passed.