NewsHub | BusinessHub Client Blog

MYOB Acumatica 2026.1: What to Expect from the Upgrade Process

Written by Andrea Drobnik | Sep 23, 2026, 5:17:12 AM

MYOB Acumatica upgrades twice a year, and 2026.1 is the next one rolling out between October and December 2026. Here's what actually happens behind the scenes, and what you need to do to get ready.

The Upgrade Process

Your site is promoted to the latest release version 45 days before your scheduled upgrade month, and the upgrade itself runs overnight — roughly 10pm to 4am NZT on your assigned date. If anything goes wrong, a rollback is targeted for 6am NZT the next day, so there's a safety net built into the process. If you're subscribed to notifications, admin users get in-app alerts 30 days before the upgrade and again 7 days after.

Pre-Upgrade Review

The real preparation work happens in your EAP sandbox — a pre-upgraded copy of your live site provisioned specifically so you can test before the real thing happens. Use it to run your custom workflows, inquiries and reports, and to trial the Modern UI transition. Note that bank files, bank feeds, super batches, emails, and STP reporting aren't part of sandbox testing, so don't rely on the sandbox for those.

A few practical tips:

  1. Confirm your upgrade date doesn't clash with pay runs, batch processes, audits or other key events. Log a Service Request if your upgrade date isn't suitable.

  2. Check that your customisations republish successfully in the sandbox.  BusinessHub's Release Readiness Program helps our Premium Success clients with getting their sandbox ready for testing.

  3. Involve your end users in testing, especially around customised screens, reports and workflows.  This will help them learn about new features, like the Modern User Interface, at the same time as reviewing a pre-upgraded version of your site.

  4. Make sure STP reporting and email processing are suspended in the sandbox so they don't fire unexpectedly.  

  5. If you find an issue, log a Service Request straight away.

  6. It's also worth notifying your ISVs ahead of time so they can prepare updated customisation packages and confirm their endpoints are current.

If your upgrade date genuinely doesn't work, you can opt out or reschedule — but it requires 14 days' notice, is limited to one opt-out per year, and is reserved for material issues found through early testing. The release notes have the full technical detail; this is just the high-level view.

Ready to make sure this upgrade goes smoothly and delivers real value?