Stage and Forecast Category Change Management

Impacts of stage and forecast category changes: 

1. Projections - The model restarts its calculations from the time of the change since it is built off of stage history and those historicals have now changed.  The Projections will not be usable for 1 to 2 quarters depending on how long your sales cycle is. 
2. Deltas - Stage or Forecast Category history becomes not reportable going back prior to their change.  Implications of delta impacts:
   1. RevBI - Stage or category history reporting will not be accurate prior to the change being made.  For example, stage progression (number of days to move from Stage 1 to Stage 2) becomes unreportable prior to the change.  
   2. Trends - Stage or category change history is impacted.  For any opportunities that were at some point in one of those old stages or categories, that history is no longer reportable.  However, when performing the change management via scenario 1, we will not say all impacted opps are going from out of pipeline to pipeline vs. scenario 2 that will be the case from the point of the change and backwards in time from there.
   3. Rollups and Opportunity page deltas -  All deltas for the corresponding change (Category or Stage) will indicate a positive change.  

The above impacts can be reconciled by a stage history remapping process that takes approximately 4 weeks.  Please reach out to your CSM if you would like to proceed with this exercise. 

For SFDC stage and forecast category changes, there are 2 scenarios through which stages and forecast categories can be updated between BoostUp and SFDC:

1. SCENARIO ONE: Customer creates new stage or category value(s) with new name and API.
   Customer allows for both new and old values to be active at the same time in SFDC while we make our changes in BoostUp.  This method is preferred for BoostUp.
   
   The steps for this scenario are as follows:
   1. SFDC: Customer adds their new picklist value(s), configures them (set sequence, etc.), and have both stage sets live at the same time while we make configuration updates on our side.  
   2. Boostup side: Set configuration of the new stage set so that the old and new stages are live at the same time and save.  This will mean that the new and old stages will be visible in the UI for a period of time.  This will warrant a downtime for the BoostUp app for users while the changes are being completed. 
   3. SFDC – Customer finishes their SFDC configuration which includes deploying the new stages, deprecating the old ones, updating all of their opportunities, and updating any existing processes and automation that involve the stages or categories that were changed
      
      
      
2. SCENARIO TWO: Current value gets replaced with new value in one single process.
3. Client makes changes in SFDC without us making corresponding BoostUp changes during their process.  Makes stage change, updates opportunities, and all corresponding tools/automation. 
4. Boostup side: first, new stage or category value(s) gets added as an inactive value (if they’re not visible at first, try an opp table sync), meaning all of the deals that were moved from old to new value are considered as moving from inactive (out of pipeline) to active (in pipeline) if their new stage or category is an active one.  In boostup, CSM edits stage configuration accordingly and saves.  

*The difference between scenario two and scenario one is the definition behind the deltas that you see in UI.  In both scenarios, deltas are impacted, but the meaning behind the delta change in scenario one is you’re going from pipeline to pipeline.   In scenario two- your deltas are the same as scenario one but you’re going from non-pipeline to pipeline where stage or category changed.