Acumatica 2026 R2: Why Classic UI Users Should Start Planning Now 

Posted on: October 1, 2026 | By: Jackson Morris | Acumatica

Most release recaps summarize what’s new. This one addresses what’s urgent — because the move to 2026 R2 comes with a deadline unrelated to when your organization planned to upgrade. 

Acumatica’s own patch-policy update points to an early-October 2026 target for the release. As of now, 2026 R2 has not yet reached general availability, so the guidance below reflects what Acumatica has confirmed to date, not a finalized release note. 

 

 

Two Deadlines, One Outcome 

There are two independent reasons Classic UI has become a real risk, and either one alone is sufficient to warrant action. 

 

Acumatica is ending support for it. Acumatica has confirmed that Classic UI will be deprecated with the 2026 R2 release. Customers who upgrade, and new customers implementing 2026 R2, will no longer have the ability to turn off Modern UI. 

Chrome and Edge are removing XSLT support on November 17, 2026. Classic UI relies on XSLT to render. Once that support is removed, Classic UI screens may stop displaying correctly, regardless of Acumatica version. This is confirmed directly by Acumatica’s own community communications on the topic. 

In short: the browser deadline applies whether or not a 2026 R2 upgrade has been scheduled. It is the true forcing function, and it lands shortly after the expected R2 release window. 

 

What a Migration Involves 

For organizations with meaningful Classic UI customizations, this is a genuine project — updating custom screens to the modern framework, re-validating security and personalization settings, and testing for behavioral differences. It is not a brief undertaking, which is why deferring it to a future upgrade cycle is not a sound plan for anyone with significant Classic UI usage. The assessment should happen now, independent of upgrade timing. 

 

What’s Gained by Acting Now 

This is not purely a defensive move. Modern UI is also the gateway to the AI capabilities Acumatica has confirmed — AI Studio and AI Assistant (AcuChat) are both Modern UI only. Migrating now means being positioned to use these capabilities as they roll out, not simply avoiding a disruption in November. 

There is also a lighter-weight path worth noting: many Classic UI customizations do not require a full rebuild. Acumatica’s no-code UI Configuration tools can often handle field visibility, required-field logic, and simple custom actions in minutes, without development work. 

 

Begin the Assessment Before the Deadline Forces the Issue 

For any organization with a meaningful Classic UI footprint, the question is not whether to move to Modern UI — it is whether the necessary work is identified before November 17, or discovered after something fails in front of users. 

Logan Consulting conducts Classic UI readiness assessments designed to surface exactly this kind of hidden risk. If your current standing is unclear, contact Logan Consulting today, ahead of your next upgrade planning cycle. 

---

---