At Rootstock, we’re committed to helping you get the most out of your investment—whether that means improving inventory visibility, enabling richer financial insights, or rolling out new features that help your teams operate more efficiently. One of the best ways to maintain that momentum is through regular Rootstock package upgrades.

Upgrading may not always feel urgent, but each upgrade ensures your organization benefits from the latest enhancements, compatibility improvements, and important defect fixes. A consistent upgrade cadence also leads to smoother transitions for end users by minimizing the size and impact of each change.

Why Upgrades Matter

Every Rootstock upgrade brings meaningful improvements to your org. Customers can expect:

Improved Features

  • New functionality, enhanced user interfaces, and performance gains driven by continuous code improvements.

Elevated Compatibility

  • Reduced risk related to deprecated APIs, obsolete fields, Salesforce platform limitations, and other dependencies that evolve over time.

Defect Alleviation

  • Timely fixes for known issues—including problems your team may not have encountered yet.

A steady upgrade rhythm not only brings these benefits faster but also reduces organizational disruption. 

Clarifying the Upgrade Process

Once you decide it’s time to upgrade, communication and planning are critical. A well-structured approach helps drive user adoption and reduces friction post-upgrade. We recommend all customers:

  • Review Rootstock release notes to understand upcoming changes
  • Create a testing plan with schedules, verification steps, and expected user experience updates
  • Assign clear responsibilities to each department involved

Plan for What Matters Most

Because Rootstock touches so many operational areas, testing should focus on the business processes most essential to your operations. These might include:

  • Financials: GL postings, AP/AR, reporting
  • Supply Chain: MRP, procurement, work orders 
  • Order-to-Cash: quoting, fulfillment, invoicing 
  • Integrations: taxation, financial systems, WMS, PLM, ecommerce, EDI 
  • Customizations: triggers, flows, validation rules, Apex, objects, LWCs 
  • Security & Access: permission sets and application setting

Step One: Upgrading Your Sandbox

Your Sandbox is your safe environment to validate changes, run test scenarios, and train users. If you have multiple sandboxes, dedicating one specifically for upgrade testing is ideal. If you only work with one, setting expectations ahead of time is even more important.

While not strictly required, a Sandbox refresh is recommended before upgrading. A refresh mirrors your Production environment, giving you a realistic testing bed. Before refreshing, ensure all departments, partners, and your Rootstock Technical Account Manager are aligned—any un-migrated work may be lost.

After refreshing, remember to: 

  • Update user email addresses (Salesforce appends “.invalid”) 
  • Reset settings like email deliverability and integration endpoints 
  • Restore any needed custom setting definitions 

To initiate the upgrade, comment on your ongoing App Upgrade Case with the Sandbox org name, org ID, and the packages you wish to upgrade. If you require specific versions or timing, include that as well. 

Once the Sandbox upgrade is complete, execute your test plan and gather feedback. This may lead to further refinements, updated expectations, or follow-up with your Technical Account Manager.

Step Two: Upgrading Production

After validating everything in Sandbox, it’s time to schedule your Production upgrade. Many customers choose deployment windows that minimize operational impact, such as overnight hours. 

Submit your Production upgrade request through the same App Upgrade Case, noting the Production org details. The deployment team will confirm the update and communicate any questions. 

A few important reminders:

  • Rootstock does not perform upgrades over weekends (IST) to ensure proper support 
  • There is no rollback mechanism, so Sandbox validation is essential

Monitor and Validate After Go-Live

Once Production has been upgraded:

  • Document any configuration or customization updates 
  • Confirm integrations and scheduled jobs are running correctly 
  • Encourage users to report issues promptly 
  • Host a brief internal review to capture lessons learned 

To stay ahead of future releases, join the Build Release Announcements group in the Rootstock Success Community. You can also attend (or watch the recordings of) our quarterly release “Learning Hour” sessions.

We’re Here to Help! 

Upgrading regularly—and following a thoughtful testing plan—leads to faster innovation with less disruption. If you’d like support preparing for your next Rootstock upgrade, reach out to your Rootstock Customer Success team. We’re always here to help your business succeed.