A clean Forecasts rollout is a six-step setup project. Plan one to two weeks for configuration, plus a quarter for adoption.
- Enable Collaborative Forecasts
Setup, Forecasts Settings, check Enable Forecasts. The org-level setting activates the Forecasts tab and exposes the configuration nodes.
- Configure forecast types
Add at least one forecast type. Most orgs start with Opportunity Amount, then add Quantity or Splits as needed. Each type has its own grid.
- Build the forecast hierarchy
Setup, Forecasts Hierarchy. Enable each user, set a Forecast Manager per role, and verify the rollup math by spot-checking a rep and their manager.
- Load quotas
Upload quotas per user per period via Data Loader on ForecastingQuota. Salesforce expects one row per user-period-forecast-type combination.
- Train reps and managers
Reps need to know the Forecast Category override mechanic; managers need to know how to adjust totals and read the audit trail. Plan a one-hour walkthrough per role.
- Watch the first commit call
Run a manager-led commit call using the grid. Fix any hierarchy or quota gaps that surface in real time. Adoption sticks when the grid is the source of truth in the meeting.
- Collaborative Forecasts and Customizable Forecasts cannot run side by side. Migrating is one-way; export historical snapshots first.
- The hierarchy follows the role tree, not the User.ManagerId chain. Misaligned roles produce surprise rollups.
- Forecast Categories are tied to Stage via the Stage table, not directly. Changing a stage's category mid-quarter retroactively moves every open opportunity into a different forecast bucket.
- Quotas are stored in the corporate currency. Multi-currency orgs need to load each quota in the corporate value, not the rep's local currency.