Acumatica Upgrade Checklist - 10 Steps Before You Upgrade

What to check before, during and after an Acumatica version upgrade, so customizations, integrations and reports still work on Monday morning. Written by the developers who run these upgrades.

Get a Free Health Check Instead

Classic UI cannot be enabled in 2026 R2. Any customization that exists only as a Classic screen has to be migrated to Modern UI before the upgrade, not after. Use the Modern UI readiness checklist alongside this one.

Step 1 - Confirm your version path

  • Record your current version and build number (Help, About).
  • Decide the target version and list every major version between them.
  • Check the upgrade window your Acumatica license and hosting arrangement allow, and book it with your partner early.

Step 2 - Read the release notes for every version you cross

  • Collect release notes and upgrade guides for each version in your path, not just the target.
  • Flag removed or changed features you rely on, renamed screens, and changes to default workflows.
  • Note new features that could replace a customization you are paying to maintain.

Step 3 - Inventory and validate customization projects

  • Export the list of customization projects (Customization Projects screen) with their publish status and owner.
  • Confirm the source for each project is in source control, not only in production.
  • Validate each project against the target version in a sandbox. Fix compile errors and deprecated API warnings before go-live week.
  • Look for code that writes directly to the database or overrides base methods without calling the base. Those break most often.

Step 4 - Clear Classic UI dependencies

  • List custom screens that only render in Classic UI.
  • For a 2026 R2 or later target, migrate them to Modern UI first. See Modern UI migration.

Step 5 - Confirm ISV compatibility

  • List every installed ISV solution and its version.
  • Get each vendor's written confirmation that a release exists for your target version.
  • Flag add-ons with no compatible release. They can block the whole upgrade.

Step 6 - Check integrations and API endpoints

  • List every system that connects to Acumatica, which endpoint and endpoint version it calls, and which user it logs in as.
  • Confirm the endpoint versions in use are still available on the target version, and plan moves where they are not.
  • Point each integration at the upgraded sandbox and run a real order, payment or sync end to end.
  • Make sure integration users are not personal accounts that might be disabled.

Step 7 - Test reports, generic inquiries and dashboards

  • List the reports and generic inquiries finance and operations use every week.
  • Run each in the upgraded sandbox and compare totals with production.
  • Check custom Report Designer reports and printed forms (invoices, packing slips, checks).

Step 8 - Upgrade a sandbox copy first

  • Upgrade a recent copy of production, not an old test tenant.
  • Record how long the upgrade and republish take. That is your downtime estimate.
  • Keep a list of every fix you make so the production run repeats them in order.

Step 9 - Run user acceptance testing

  • Give each department a short script of the transactions they run daily.
  • Get written sign-off per department, not one blanket approval.
  • Brief users on visible changes: new screens, moved fields, Modern UI navigation.

Step 10 - Plan cutover and rollback

  • Pick a window outside month-end and peak shipping days.
  • Pause integrations and scheduled processes before the upgrade, and restart them in a known order after.
  • Take a snapshot you can restore, and decide in advance who calls a rollback and by what time.
  • Check integrations, key reports and a sample of transactions within the first hour after go-live.

Our free Acumatica health check reviews your customizations, integrations and ISV add-ons against your target version and sends you a written list of what will break. If you want us to run the upgrade, we quote it at a fixed price.

Get a Free Health Check β†’