Loading quotas is straightforward once the Forecasting feature is enabled and Forecast Types are configured. The choices are Data Loader for bulk loads, the Collaborative Forecasts UI for small teams, or an API integration for ongoing automation.
- Enable Collaborative Forecasts and Forecast Types
Setup, Forecast Settings, Enable. Pick the active Forecast Types (Revenue, Quantity, Splits, Product Family, Custom). Quotas attach to specific Forecast Types, so this decision precedes quota loading.
- Confirm the forecast hierarchy
Setup, Forecasts Hierarchy. Confirm the manager/report relationships. Quotas roll up the hierarchy, so the hierarchy must be accurate before the load. A missing manager-rep link causes the rep's quota to not appear in the manager's view.
- Prepare the quota CSV
Build a CSV with columns: UserId, StartDate (first day of the forecast period), QuotaAmount, QuotaQuantity, ForecastingTypeId, CurrencyIsoCode. Validate every UserId resolves to an active user.
- Upload through Data Loader
Open Data Loader, Insert or Upsert against ForecastingQuota. Map the CSV columns to the object fields. Run the load. Confirm the result file shows success for every row.
- Verify in Collaborative Forecasts
Open the Forecast tab as a user with quotas loaded. Confirm the quota appears for the right period and Forecast Type. Cross-check the manager view shows the rollup correctly.
- Build an integration for ongoing loads
For monthly or quarterly refresh, build a scheduled job (MuleSoft, ETL, Salesforce CLI scripted) that upserts the latest quota plan. Avoid manual CSV loads at scale; they become an operational burden.
The sObject that stores quota records. One record per user per period per Forecast Type.
Revenue, Quantity, Opportunity Splits, Product Family, Custom Number, Custom Currency. Each can have its own quotas.
The manager-rep tree that determines how quotas roll up. Must be accurate before quotas are loaded.
Manager-initiated change to a direct report's quota mid-period, tracked with attribution and audit trail.
The standard bulk-load mechanism for quotas, using User + StartDate + ForecastingType as the external ID.
- Quotas attach to a specific Forecast Type. Loading Revenue quotas without enabling the Revenue Forecast Type creates orphaned records that never appear in the UI.
- The forecast hierarchy must be accurate before quota load. A missing manager-rep link breaks rollup silently, and managers see incomplete attainment views.
- Quotas are time-bound. A quota with the wrong Start Date (off by one day at the period boundary) lands in the wrong forecast period. Validate dates against the org's Fiscal Year settings.
- Manual UI quota entry is fine for 5 to 20 reps. Above that, Data Loader or an integration is the only practical path. Plan the load mechanism before agreeing to a quota-driven sales plan.
- Manager-initiated quota adjustments distort historical attainment metrics. Most companies discourage mid-period adjustments. The audit trail exists; the policy is what controls usage.