Upgrading to Acumatica 2026 R2: what you gain and what to check first

AcuPower Blog  |  AcuPower

5 min read

An older Acumatica version can feel fine while you miss what has changed. Here is what 2026 R2 adds, how the Classic UI retirement affects you, and what to look at before you upgrade.

It feels fine. That’s the catch.

If your Acumatica system works, there’s little pressure to touch it. Your team knows the screens. Reports run. Nothing is on fire.

The cost of standing still is subtle: new features pass you by. The AI that Acumatica now builds into daily screens isn’t available to you. And one change will reach every user in the end: the Classic UI is being retired.

This article covers what has changed, what the retirement means, and what to look at before you move. For the full feature list, read our main article, everything new in Acumatica 2026 R2.

What has changed since your version

Take AI first. A 2023 release added document recognition for more branches and locations, and text suggestions based on past entries. Useful, but narrow. Since then, AI Studio has become part of the platform, and 2025 R2 added AI Studio automations that business users and partners can build without code. 2026 R2 goes further.

• AI Assistant: A chat window across the module screens. You ask in plain language and it answers from your live data. It can also build a Generic Inquiry for you.

   

• AI Studio: A low-code builder where administrators and developers create custom AI workflows, with a person approving the result.

   

• MCP server: Outside AI tools such as Claude and ChatGPT can query the inquiries your administrator approves, with sign-in, access rights and logging in place.

   

• Data warehouse tables: A slow inquiry loads stored results instead of rebuilding them every time someone opens it.

   

• Platform: PostgreSQL is supported in production, and a new API Monitoring tab shows request volume, errors and throttling for your integrations.

The other big change is the interface. The Modern UI was a developer preview in 2024 R1 and has been available to every customer since 2025 R2. Teams can adjust fields, tabs and layouts on each screen to fit how they work. In 2026 R2 it is the only interface.

The Classic UI is going

In 2026 R2, the Modern UI is the default and users can no longer switch back to the Classic UI. The option has gone from the installer, the system menu and the site preferences. What comes next is the date that matters. Screens that exist only in the Classic UI will no longer be available from 2027 R1.

For now, they still open in 2026 R2, with a warning that they’ll be deprecated. That covers Classic dashboards, pivot tables, wizard forms, the Layout Editor in the Customisation Editor, and custom forms that haven’t been converted. You can no longer create new Classic dashboards or pivot tables.

So 2026 R2 gives you time, and a clear job: find what is still on the Classic UI and move it before it disappears.

What to take into account before you upgrade

• Customisations and integrations. Anything built on top of Acumatica needs testing against 2026 R2 before it goes near production. Acumatica recommends testing on a new 2026 R2 instance first, because compatibility errors can appear when you publish a customisation project. Some code needs updating. Mobile app scripts must be adapted to the Modern UI, and projects with unadapted scripts can’t be published. Code that relied on old connector APIs that have since been removed needs a look too. The further back your version, the more change releases apply, so the review takes longer.

   

• Classic-only content. Dashboards, pivot tables, and custom screens that exist only in the Classic UI will no longer be available from 2027 R1. Better to find them now than after the upgrade.

   

• People and data. The Modern UI changes how screens look and where things sit, so give your team time to get used to it. The AI features answer from your data, so clean item records and consistent customer details matter more. Features such as the MCP server and data warehouse tables need an administrator to set them up, so decide who owns them.

What an upgrade involves

Acumatica publishes the procedure. You test your customisations on a new 2026 R2 instance. In production, you unpublish the customisation projects, upgrade the instance, replace the projects with the validated versions, and republish them. After the database upgrade, you rebuild the search index.

In practice, that means four stages: review what you have, test on a copy, upgrade, then validate and train. We don’t give timescales here because they depend on your customisations, integrations and data.

If you’re an AcuPower customer

You already work with us, so the first step is a conversation about where you are today, what you’d gain from 2026 R2 and what needs testing before you move. Bring any Classic-only screens, customisations and integrations you know about.

Contact Us – US & Canada

Contact Us – UK, Europe & South Africa

If you’re an Acumatica partner short on capacity

An upgrade needs business analysts and developers, the same people your implementations depend on. If they’re booked and your customers are asking for 2026 R2, we can deliver the upgrade for you.

Partner With Us – US & Canada

Partner With Us – UK, Europe & South Africa

If you use Acumatica through another partner

Your Acumatica partner is the right first call. Ask them about upgrading to 2026 R2, and take three points from this article into that conversation: what has changed since your version, the 2027 R1 date for Classic-only screens, and what needs testing. Reach out to your Acumatica partner.