Home

>

On AI

Acumatica upgrades, with confidence in everything that works and everything that is changing.

We bring the project management and the pre-built templates. We run every test first. Then your people run them. By cutover, nobody is guessing.

You have an upgrade date. Do you have a plan?

Your VAR has scheduled the upgrade. What they own is the technical lift: the sandbox refresh, the customization republish, the cutover. What nobody owns is everything around it:

01

Which integrations touch Acumatica, and who tests each one.

02

Which customizations still matter and which can finally go

03

What your people actually do every day, written down well enough to test.

04

What is new in the release that you are already paying for.

05

Who signs off, on what, by when.

That gap is where upgrades go wrong. It is also the whole of what we do.

Why Acumatica upgrades go wrong

The platform itself upgrades cleanly. The problems are around it. Customizations written against screens that have changed. Integrations nobody inventoried. Scheduled reports and automations tied to something that was removed. Processes that were never documented, so nobody tests them until a customer calls. Twice-a-year releases mean this comes around faster than most teams are ready for.

How we run an upgrade

Inventory

We build the list most companies do not have: every integration, every customization, every scheduled report and automation, every process that matters. You cannot upgrade safely if you cannot list what is connected.

Verdicts

Every customization gets one: keep, retire, or replace with a native feature. Upgrades are the best moment to shed old weight.

The test plan

Our pre-built templates cover order to cash, procure to pay, record to report, inventory, production, projects and integrations. We tailor them to your processes, in your words.

We run it first

In your sandbox, on the new version, we run every test ourselves. We find what breaks before your team spends an hour on it. Purchasing tied to the penny in one rehearsal.

Then your people run it

Each process owner runs their own tests from the same templates and signs off. They see what changed on their screens before it changes in production. This is where confidence comes from.

What is new

We read the release notes so you do not have to, and give a plain verdict on each feature that matters to you: turn on, test first, or ignore.

Cutover

An off-hours runbook coordinated with your VAR. Named owners, a go or no-go checkpoint, and a rollback plan.

Hypercare

We stay through the first close on the new version.

What is in the template kit

01

Integration inventory

02

Customization register with keep, retire or replace verdicts

03

Regression test scripts by process

04

Sign-off tracker by process owner

05

Release feature review, with verdicts

06

Cutover runbook and go or no-go checklist

07

Hypercare log

You keep all of it. The second upgrade is faster than the first, and you may not need us for the third.

Project management is the product

Most upgrade pain is coordination, not technology. The VAR, the EDI vendor, the 3PL, the bank, the AP platform and your own process owners each hold a piece. We hold the plan: one schedule, one tracker, a weekly checkpoint, and one party accountable for whether you are on track, not just on schedule.

From the record

The report nobody would have missed until a customer asked. A rehearsal caught a removed screen that would have silently stopped five scheduled report sends. No error. They would simply have stopped.
The list that did not exist. One client had no list of what was integrated to the ERP. The integration inventory became the first deliverable, and then the regression scope.
Twelve processes, twelve tickets. One upgrade ran with a sandbox window, a regression ticket per process and an off-hours cutover coordinated with the VAR. Another used a 28-item validation plan organized by order to cash, procure to pay, record to report and new features.
Every customization given a verdict. Keep or retire, decided before the upgrade instead of discovered after it.

How AI speeds this up

Release notes run to hundreds of pages. We use AI to read them against your inventory and flag what touches your processes, your customizations and your integrations. Test scripts are drafted from your own SOPs and working sessions. A person reviews everything before it reaches you.

Common questions

Does my VAR not do this? Your VAR does the technical upgrade. Testing your business processes is your responsibility under most agreements. We make that manageable.
How long does it take? Most of the elapsed time is your team's testing window. Plan 8 to 12 weeks from sandbox to cutover. Acumatica provides an upgrade sandbox for 90 days, so that is usually the window. The plan is built to finish inside it, with time left to retest.
Can we skip a version? Often yes. We will tell you what skipping costs you in support and in features, and what it saves.
We are several versions behind. Is that a problem? It is a bigger test plan, not a different one.
When should we not upgrade? During close, during peak season, or before the sandbox rehearsal is signed off.

Release guides

Acumatica 2026 R1. Live and ready for you to start usign now.

Acumatica 2026 R2. Coming. What is new, what to turn on, what to test first, and what we saw break in real upgrades.
Acumatica 2027 R1. Coming. A full feature-by-feature guide by module, with a verdict on each.
Each guide will be a living page: a dated change log at the bottom, updated as we take clients through the release.

Related

Integrations · Governance · Field Notes

Want a straight read on AI for your business?

Book a 20-minute call