OneStream Upgrade

Hey Mikki​ ,

Short answer to your first question that you probably already anticipated - "it depends".  Factors that can impact the upgrade process:

• Version you are upgrading from
• Extent of Solution Exchange solutions installed
• Extent and complexity of business rules / dashboards in use
• Span of integration points and types thereto (already on SIC, OIS or not, etc.)
• Number of applications to migrated

Non OneStream related factors:

• IT standards and protocols to adhere to
• Availability of resources (including BAU black out periods)
• Org readiness - already have pre defined test plans, test scripts, resolution protocols, etc.
• Degree of change management/ communications required

Re: performance improvements - suggestions:

• If performance improvements is something important, be sure to capture baseline metrics in the current environment (s) before the upgrade 
• Common performance benchmark use cases include Month 12 Top Entity Force Consolidate, executing the slowest CubeView(s) and/or Dashboards(s), loading the longest running import job, retrieving the most common data pulls via Spreadsheet and Excel, -- essentially, focus on the area(s) that can have the greatest impact on user experience due to system performance deterioration
• Recommend to do these "off hours" to minimize impact by other users

Re: extent of user testing

• Always helpful to involve your key power users and cover the most frequently used and critical functions in testing
• Otherwise, eye of beholder.
• The version you are upgrading from also dictates impact of visible change to users - Modern Browser Experience is automatically enabled after a certain version so can throw off users - should be proactively managed and eased in since the UI/UX is different (and is not yet at full parity with Windows App version)
• Excel Add-In by and large need to match platform version but you can't have two versions running concurrently on the same machine

Overall XP:

• OneStream upgrade team has been great and proactively helpful in all the times we have gone through the bigger upgrades so far (e.g., pre 8.2 to 8.2+) - almost feels like a workout routine at this point for my team 😊

Lessons learned:

• Always plan ahead and engage OneStream team sooner to map our the upgrade plan that best suits your circumstances - but also remember you have tasks outside of their lists that only you / your org will know and can do.
• Anticipate it will take longer than planned
• Ensure a clear rollback strategy is in place and agreed upon by all stakeholders (e.g., in the remote chance that critical showstoppers cannot be resolved, you can defer final cutover)
• Freeze all development during the upgrade if practical - remember that upgrade of your application(s) might happen twice - once at the start to assess impact and extent of post upgrade changes to be made, and another time towards cut over
• Secure commitment (time and focus) from key resources - internal, OneStream, OneStream partner if applicable, etc 
• Ensure there is adequate post upgrade end user support

Cheers,

A.