Acumatica 2026 R2 Migration – Frequently Asked Questions
Honest answers for Acumatica and vertical-edition administrators ahead of the expected
~October 2026 release. Companion to the main guide,
Preparing for the Acumatica 2026 R2 Forced Migration – A Readiness Checklist.
Written June 2026, while 2026 R2 is announced but not yet shipped – re-verify dated
claims at R2 GA.
Is Acumatica 2026 R2 a mandatory upgrade?
Nobody forces the upgrade onto your tenant, and pre-R2 versions keep running. But
for any site that depends on Classic UI, SQL Server 2019, or legacy APIs
(screen-based SOAP / OData v3), three independent clocks make “stay put” a plan
that fails on its own: R2 removes the ability to run Classic UI; Acumatica’s May
2026 patch-policy change means fixes now ship mainly with new versions; and Chrome
removes XSLT on November 17, 2026, breaking Classic UI screens in Chromium
browsers regardless of your version. Effectively mandatory is the honest summary.
When is Acumatica 2026 R2 released?
Early October 2026 – expected, not GA-announced. The date comes from
Acumatica’s own community post updating the patch release policy (effective May
2026). As of June 2026 there is no published 2026 R2 feature list – only the date
and the announced breaking changes. Plan against “~October 2026” and treat anything
more precise as unconfirmed.
What breaks in Acumatica 2026 R2?
Three announced changes:
- Classic UI is removed. The ability to turn off Modern UI goes away; Classic
remains supported only on pre-R2 versions. - SQL Server 2019 support is dropped. SQL Server 2022 or the newly supported
SQL Server 2025 is required. - The legacy screen-based SOAP API is removed and OData v3 is sunsetting, with
contract-based REST and OData v4 as the path forward.
Each has its own dated Acumatica community announcement – which is why a readiness
pass is scopeable now, months before the release ships.
Can I keep using Classic UI after 2026 R2?
Not on R2 – and possibly not in your browser even before then. Classic remains
supported only on pre-R2 versions, so keeping Classic means freezing your version.
And separately, Chrome’s XSLT removal on November 17, 2026 breaks Classic UI
screens in Chromium browsers (Chrome, Edge) on that date even if you never upgrade.
Acumatica has announced Classic-UI compatibility patches – for 2025 R2 scheduled
June 30, 2026, and for 2025 R1 scheduled July 3, 2026 – and no fix for 2024 R2
or earlier: on those versions the interim workaround is Firefox or a pinned old
browser build, and the vendor path is an upgrade to 2025 R1+.
Do I need to upgrade SQL Server before taking 2026 R2?
If you are on SQL Server 2019, yes – and it is a gating prerequisite, not a
parallel task. SQL 2019 still runs under 2026 R1, but Acumatica has said
DB-caused issues on 2019 won’t receive fixes, and R2 requires SQL Server 2022 or
2025. For hosted/SaaS sites the prerequisite still exists – the question is who
owns it; confirm with your host that the platform under your tenant won’t be on
SQL 2019 at R2. If you don’t know your SQL Server version, finding out is
checklist item one.
How do I know if my integrations are affected?
Inventory, don’t assume. Every integration touching the site should be classified
by the API it actually uses: screen-based SOAP and OData v3 URLs are
distinguishable from contract-based REST and OData v4 paths, and packaged-connector
vendors can answer for their products. Anything on a legacy surface needs a
migration plan before R2 – the dangerous failure mode is the integration that
keeps working right up until the upgrade, then breaks in production. Treat “nobody
knows what this integration uses” as a blocking finding.
What does the May 2026 patch-policy change mean if I stay on an old version?
Scheduled patches ended effective May 2026; fixes now arrive as critical-only
on-demand patches otherwise delivered with the next version (2025 R1’s final
scheduled patch landed by May 26, 2026). The consequence: the further behind you
sit, the more your open issues wait on a version upgrade you haven’t planned.
Staying put stopped being free.
Does the “Convert to Modern UI” tool do the migration for me?
No – it does the conversion, not the migration. The tool converts custom .aspx
screens to the Modern UI’s .ts/.html pattern, and business logic generally
survives. But partner field reports describe control-ID mismatches, broken
grid-to-grid dependency logic, redundant properties, and inaccurate layouts in the
converter’s output – hours of cleanup for simple screens, days for complex ones –
and customizations living in extension files must be re-created manually. Budget
for the cleanup, not just the conversion, and validate third-party customization
packages for Modern UI while the Classic escape hatch still exists.
How long does 2026 R2 readiness actually take?
Practitioners report 6–8 week regression test cycles with heavy customer
involvement for Acumatica upgrades – before counting the remediation the audit
surfaces (a SQL Server move if you’re on 2019, per-screen Modern UI rebuild,
integration API migration). Counting backward from an expected ~October 2026
release and the November 17 browser deadline, the planning window for most sites
is now, not at GA.
Does the 2026 R2 migration affect vertical editions built on Acumatica’s platform?
Yes, with a verification step. A vertical edition is built on Acumatica’s xRP platform
and inherits the platform pressures – the Classic UI deprecation, the SQL Server
2019 drop, and the browser deadline. But a vertical edition ships on its own release
cadence, delivered as a managed upgrade service, so which Acumatica base version your
build tracks determines when each platform deadline lands for your site. As of June
2026 there is no public vertical-edition-specific 2026 R2 adoption timeline – confirm
against your vendor’s own release notes. The one exception is the Chrome XSLT date: it
is browser-driven and applies to any Classic screens rendered in Chromium on November
17, 2026, regardless of vendor timelines.
Should I plan for the AI Assistant in the same pass?
Only with expectations set correctly. As of June 2026 the AI Assistant is in early
access, slated for GA at 2026 R2. It is read-only (it answers, it does not
act), it answers only over the Generic Inquiries an administrator exposes to
it, and it is metered (pre-GA ~5,000 AI Units/month ≈ 100 questions, post-GA
pricing not yet disclosed). Don’t architect workflows around it before pricing is
known – but if the organization intends to use it, a GI design review is a small,
concrete add-on to the same readiness pass, because the Assistant is only ever as
useful as the GIs underneath it.
What happens to my reports and Report Designer at upgrade time?
Every major upgrade is a re-validation event for the reporting estate. Report
Designer is version-matched to the site build, so a staged rollout (test on R2,
production on R1) can mean maintaining two installs – and practitioner reports of
upgrade instability specifically include reports needing unexpected rework, so
critical reports belong in the regression pass. If your site is SSO-only
(Entra ID / Okta / ADFS / FedRAMP), you also have a separate, standing Report
Designer problem the upgrade won’t fix – see
Acumatica Report Designer Doesn’t Work With SSO – Here’s Why, and How to Fix It.
What does a professional readiness review add over the checklist?
The checklist tells you what to check; a hands-on review produces the verified
answers for your site: the actual SQL Server version, the actual custom-screen
inventory with complexity tiers, the integration-by-integration API audit, and a
sequenced remediation plan with the regression window booked against the calendar.
It converts unknowns into findings – and unknowns are where upgrade projects fail.
How do I get started?
If your site still runs Classic-UI customizations, SQL Server 2019, or
integrations you can’t confidently classify, the next step is a per-site readiness
consultation – a bounded conversation that turns the checklist into verified findings
and a sequenced plan.
Contact
Bring your 2026 R2 questions to a consultation – what’s actually mandatory, what breaks, and how to sequence it for your site.
Or email [email protected].