What is Always Current?
The Acumatica Always Current is a program for SaaS customers that keeps you on the latest supported version of Acumatica—so you're always secure, supported, and ready for what's next.
Instead of big, infrequent upgrades that require significant planning and carry more risk, Always Current delivers continuous innovation through a predictable release rhythm. You focus on running your business; Acumatica handles keeping you current.
Note: Always Current is only available for SaaS customers. Private cloud (PCS) customers are not eligible.
How It Works
Acumatica releases two major versions each year
Major Releases (Twice a Year)
- R1: Late September or early October
- R2: Late March or early April
- Major releases include new features, performance improvements, and platform enhancements
- Always Current upgrades happen approximately 6 months after major version release—this allows the version to stabilize through patches and gives time for a Service Pack to become available.
- Starting in 2026 when Always Current upgrades you to a new major release, you'll automatically receive the latest service pack available for that version.
- You'll receive approximately 90 days' notice before your scheduled upgrade, plus follow-up reminders at 60 and 30 days
- Major version upgrades require preparation: Sandbox testing, customization validation, and user training
Eligibility and Upgrade Options
Your upgrade frequency depends on your Acumatica edition:
| Edition | Upgrade Options |
| Small Business / Essentials | Upgrade twice per year on your scheduled dates |
| Advanced / Select | Upgrade once or twice per year—annual upgraders choose Jan–Jun or Jul–Dec window |
| Prime / Enterprise (April 2024+) | Upgrade once or twice per year—annual upgraders choose their window |
Need more flexibility? Ask your partner about Acumatica Flex, which allows you to select an upgrade date before your current version reaches end-of-life. Flex is ideal for customers using non-certified ISVs or customizations that need additional preparation time.
Can I change my upgrade option? Yes. Contact your partner to discuss changing your upgrade frequency or timing. A services fee may apply.
Example Timeline: 2025 R1 / R2*
| Date | Event | Description |
| March 2025 | 2025 R1 General Availability | Major version released. Request a sandbox for testing. |
| June–July 2025 | Service Pack for 2025 R1 | Bundled fixes are available. |
| September 2025 | Always Current Upgrades to 2025 R1 | Customers upgraded to the latest service pack of 2026 R1. |
| September 2025 | 2025 R2 General Availability | Next major version released. Begin testing with a sandbox. |
| December 2025–January 2026 | Service Pack for 2025 R2 | Bundled fixes are available. |
| March 2026 | Always Current Upgrades to 2025 R2 | Customers upgraded to latest service pack of 2026 R2. |
*All dates are approximate and subject to change.
Why Staying Current Matters
The Benefits
- Reduced cost and risk — No more expensive, high-risk "big bang" upgrades when you fall multiple versions behind
- Immediate access to new features — Get the latest capabilities as they're released
- Timely security fixes — Stay protected with automatic patches
- Predictable maintenance — Know when updates are coming and plan accordingly
- Supported version — Always remain on a version that Acumatica actively supports
Staying Informed
Where to Find Information
Start with the Customer Portal—that's where you subscribe to IT & SaaS Notices. No subscription, no emails. Make sure the right people are signed up, and those contacts stay current.
Additional sources:
- Acumatica Community — Release and maintenance updates are posted here
- Your Partner — Many partners summarize what's relevant for your specific environment
What We Send and When
| Notification | Timing |
| Upgrade notice | 90 days before (plus 60-day and 30-day reminders) |
| Release announcements | Posted to Community when new versions are available |
Remember: Always Current only works if the right people see the right notices. Make sure you and your partner know who's watching which channel.
Customizations
Customizations are where most technical upgrade pain actually comes from. It's rarely the core product—it's custom code and add-ons that weren't tested or weren't ready.
Know What to Expect
- Patches do not unpublish customizations — Your environment keeps running as-is
- Major upgrades do unpublish customizations — They must be republished, usually by your partner
- Always follow the Upgrade Guide for your specific version
Protect Your Work
- Test in a sandbox before you upgrade—never let production be the first place you see how your customizations behave
- Keep documentation current for every customization and integration: what it does, who owns it, and any dependencies
- Take Acumatica snapshots before any upgrade—that's your safety net
Plan Ahead
- Know your developer — Whether it's a partner, an ISV, or someone on your team, know who built each customization
- Prefer validated ISV solutions — Validated ISVs have already been tested against Acumatica's upgrade process
- Follow Acumatica's customization guidelines for both new and existing work
Questions to Ask Your Partner
Before your next upgrade, have these conversations:
- Why am I not getting notifications? If you're not seeing upgrade or patch communications, something's broken in the chain.
- Do you have our complete customization inventory? Not what you had at implementation—what you have today. Every customization, every ISV package, every integration.
- When will the sandbox be ready for us to test? Not when will they test—when will it be ready for you. Sixty days out is the target.
- Do you have a testing plan? Ask to see it. If there isn't one, that's a red flag.
- What's your plan if a customization fails during testing? You want to know your partner has a process for this—not figuring it out in the moment.
90-Day Readiness Checklist
| Timeline | Actions |
| 90 Days Before | Review release notes & Upgrade Guide · Identify breaking changes with partner · Build shared testing checklist |
| 60 Days Before | Partner prepares sandbox · Test core workflows & integrations · Run at least one period-end |
| 30 Days Before | Partner validates customizations/ISVs · Resolution plan for known issues · User training begins |
| 2 Weeks Before | Final sandbox validation · Confirm cutover timing & roles · Know your rollback options |
| Upgrade Day | Communicate downtime · Upgrade → Monitor · Partner on standby |
| Post Upgrade | Monitor & support users · Capture lessons learned · Finalize customization republishing |
Frequently Asked Questions
Q: Will upgrades affect my customizations?
A: Yes. Upgrades unpublish customizations, which must be republished by your partner.
Q: Can I delay my scheduled upgrade?
A: Contact your partner to discuss options. Requests should be submitted well in advance of your scheduled date.
Q: How do I know if I'm enrolled in Always Current?
A: Review your Customer Order Form, Contract, or contact your partner.
Q: Which ISVs are Always Current compatible?
A: ISVs in the Acumatica Developer Network Level 2 program must support Always Current. Check the Acumatica Marketplace for certified ISV solutions.
Questions? Reach out to your Acumatica Partner or Customer Success Manager.