Impact of the Retirement of Customizable Forecasting in Salesforce's Summer '20 Release

The Salesforce Summer ‘20 release includes the end-of-life for Customizable Forecasting. Summer ‘20 is planned for late-May for Sandbox upgrades, with Production upgrades beginning in mid-June. The majority of Veeva customers do not use Forecasting within Salesforce, and Veeva CRM is not affected by the retirement of Customizable Forecasting. However, Veeva customers are receiving end-of-life announcements for this module from Salesforce which recommend enabling the new Collaborative Forecasts Module instead. 

Before taking action, Veeva customers should understand their usage of Forecasting and the implications of enabling Collaborative Forecasts. For the majority of customers, the best course of action is to simply allow Customizable Forecasting to be retired without enabling Collaborative Forecasts.

Please do not enable Collaborative Forecasts, or request disablement of Customizable Forecasting unless you are able to migrate to TM2.0 at the same time. Either of these actions requires disabling TM1.0, which immediately triggers the need to migrate to TM2.0 for Veeva customers. This cannot be undone, and there is no option to restore an org to TM1.0 once it has been disabled. If you are not ready to move to TM2.0, disabling Customizable Forecasting or enabling Collaborative Forecasts will result in a prolonged production outage for end-users until all impacted elements of your production org are migrated to TM2.0.

Note: Allowing Customizable Forecasting to retire with Summer '20 will not disable TM1.0.

Veeva is recommending the following:

  1. For all customers, please review CRM integrations for impact due to org changes. When Customizable Forecasting is disabled, the following objects are removed from your CRM environment:

    1. ForecastItem
    2. ForecastItemHistory
    3. ForecastOverrideItem
    4. ForecastOverrideTree
    5. ForecastQuarterHistory
    6. ForecastRollup
    7. ForecastShare
    8. ForecastUserOppRollup
    9. QuantityForecast
    10. QuantityForecastHistory
    11. RevenueForecast
    12. RevenueForecastHistory
    13. OpportunityForecastPeriod
    14. LineItemOverride
    15. Note: If Customizable Forecasting is disabled by request, the User.ForecastEnabled field is removed from the environment immediately. If Customizable Forecasting is retired with Summer ’20, this field will remain in your environment until TM1.0 is disabled. To avoid impact, it is recommended that this field is not included in the metadata definition for integrations with the User object 

  2. If you do not use Customizable Forecasting and will not use Collaborative Forecasts (most common scenario):

    1. Simply allow Customizable Forecasting to expire in your CRM org after you have confirmed that system integrations are not impacted

  3. If you are not using Customizable Forecasting but plan to use Collaborative Forecasts:

    1. Allow Customizable Forecasting to expire in your CRM org after you have confirmed that system integrations are not impacted
    2. Migrate to TM2.0 before its retirement in Summer ‘21
    3. Enable Collaborative Forecasts after the TM2.0 migration is completed

  4. If you are using Customizable Forecasting and plan to switch to Collaborative Forecasts:

    1. TM2 Migration and Collaborative Forecasts enablement should happen at the same time. This is because Salesforce recommends enabling Collaborative Forecasts immediately after disabling Customizable Forecasting to prevent data loss
    2. To assure there is no gap between Customizable Forecasting disablement and Collaborative Forecasts enablement, TM2 Migration must happen before Summer ‘20 is released to your environment



Salesforce Summer '20 Release Dates

Veeva Resources for Salesforce TM2.0 Migration

Customizable Forecasting Overview

Collaborative Forecasts Overview

Considerations for Migrating from Customizable Forecasting to Collaborative Forecasts

Comments not allowed