Skip to main content
Solved

Update Version Acumatica 25R2

  • May 13, 2026
  • 6 replies
  • 26 views

Forum|alt.badge.img

Hello everyone, so one of my client agree to update their Acumatica Version from 24R2 to version 25R2, but we were still on progress to update the environment (not yet go-live), is that possible to doing the upgrade?
Please lemme know about the procedure of this, I really appreciate thank you. 

Best answer by Naveen Boga

@dinda56  Yes, it is absolutely possible to upgrade from Acumatica ERP 24R2 to 25R2 even if the 24R2 environment is still in progress and not yet live. In fact, this is actually one of the safest times to do the upgrade because the system is not yet in production.

Here’s the recommended approach and procedure.

  • Take full database and customization backups
  • Clone the existing 24R2 environment
  • Install Acumatica ERP 25R2 on the cloned environment
  • Point the new site to the copied database
  • Run the database upgrade
  • Publish all customization packages
  • Fix any compilation/customization issues
  • Validate integrations, reports, workflows, and APIs
  • Perform UAT testing
  • Take backup of the actual 24R2 environment
  • Upgrade the actual environment to 25R2
  • Publish validated customizations
  • Perform smoke testing
  • Continue implementation and go live on 25R2

Important Tips

  • Do not skip the TEST upgrade,  even on a non-production environment
  • Check Acumatica's Release Notes for both 25R1 and 25R2 since you're jumping two versions — breaking changes in 25R1 also apply to you
  • Engage Acumatica Support if you hit database upgrade errors — do not try to manually fix schema issues
  • Since you mentioned customizations (we can see several active in your trace logs)  budget extra time for recompiling and testing each one

6 replies

Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • Answer
  • May 13, 2026

@dinda56  Yes, it is absolutely possible to upgrade from Acumatica ERP 24R2 to 25R2 even if the 24R2 environment is still in progress and not yet live. In fact, this is actually one of the safest times to do the upgrade because the system is not yet in production.

Here’s the recommended approach and procedure.

  • Take full database and customization backups
  • Clone the existing 24R2 environment
  • Install Acumatica ERP 25R2 on the cloned environment
  • Point the new site to the copied database
  • Run the database upgrade
  • Publish all customization packages
  • Fix any compilation/customization issues
  • Validate integrations, reports, workflows, and APIs
  • Perform UAT testing
  • Take backup of the actual 24R2 environment
  • Upgrade the actual environment to 25R2
  • Publish validated customizations
  • Perform smoke testing
  • Continue implementation and go live on 25R2

Important Tips

  • Do not skip the TEST upgrade,  even on a non-production environment
  • Check Acumatica's Release Notes for both 25R1 and 25R2 since you're jumping two versions — breaking changes in 25R1 also apply to you
  • Engage Acumatica Support if you hit database upgrade errors — do not try to manually fix schema issues
  • Since you mentioned customizations (we can see several active in your trace logs)  budget extra time for recompiling and testing each one

Forum|alt.badge.img
  • Author
  • Varsity I
  • May 13, 2026

Hi ​@Naveen Boga Thank you for your respond, so it’s safe right to doing the upgrade while we were doing environment. Thank you.


Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • May 13, 2026

@dinda56  Yes, it is generally safe to perform the upgrade while the environment is still under implementation and not yet live. In fact, this is usually the best time to upgrade because there will be less impact on users and business operations.

I would still recommend taking full backups and testing the customizations/integrations in a cloned environment before upgrading the actual environment.


Forum|alt.badge.img
  • Author
  • Varsity I
  • May 13, 2026

@Naveen Boga thank you for your explanation, btw you mention about “a cloned environment” is that same like a sandbox? because I created sandbox testing and already copied the data from 24R2 to the Testing Environment, fyi we uses Acumatica Saas, and for the procedure of the upgrade is also same like you share to me? 

Thank you.


Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • May 13, 2026

@dinda56   Yes, that is correct. In Acumatica SaaS, the sandbox/testing environment is essentially what I meant by a “cloned environment.” Since you already created a testing sandbox and copied the 24R2 data into it, that is the right approach.

And yes, the overall upgrade procedure is generally the same for SaaS as well. The main difference is that Acumatica manages the infrastructure and performs the actual version upgrade process on the SaaS instance.

Typically the process would be:

  1. Upgrade the Sandbox/Testing environment to 25R2
  2. Publish and validate all customizations
  3. Test integrations, reports, workflows, and business processes
  4. Perform UAT testing
  5. Once everything is validated, schedule the Production upgrade with Acumatica

Forum|alt.badge.img
  • Author
  • Varsity I
  • May 13, 2026

I see, thank you for your kindness it’s really helpfull ​@Naveen Boga