Quota
A Quota in Salesforce is the target sales amount or volume assigned to a user or territory for a specific forecast period (monthly, quarterly, or annually).
Definition
A Quota in Salesforce is the target sales amount or volume assigned to a user or territory for a specific forecast period (monthly, quarterly, or annually). Quotas drive the Forecasting feature: each user's pipeline and closed opportunities are measured against their quota, and the resulting attainment percentage shows in Forecast dashboards and reports. Quotas are stored on the ForecastingQuota object, with one record per user, period, and forecast type.
Quotas are not the same as sales goals at the company or team level. The platform's Quota system is per-user, time-bound, and forecast-type-aware. A sales manager might have separate quotas for Revenue, Quantity, and Custom Number forecast types in the same quarter. Quotas can be loaded through the Data Loader, the Forecasting Quota API, or the Collaborative Forecasts UI for managers managing their own teams. Importing quotas at scale (hundreds of reps across multiple periods) is a Data Loader job; managing 5 to 20 reps can be done through the UI.
How Quotas drive Salesforce Forecasting
The ForecastingQuota object
Each Quota record on ForecastingQuota has fields for the User, the Start Date (which determines the period), the Quota Amount, the Quota Quantity, the Forecast Type (Revenue, Quantity, Custom), and the Currency. The platform creates one record per user per period per forecast type. A salesperson with monthly Revenue quotas for the year has 12 ForecastingQuota records for Revenue alone. If the org also uses Quantity forecasting, that doubles to 24 records per user. Bulk loading these is the only practical approach for any team with more than a few reps.
Loading quotas through Data Loader
The standard path for quota loads is a CSV through Data Loader. The CSV has columns for UserId (or username), StartDate (matching the forecast period), QuotaAmount, QuotaQuantity, ForecastingTypeId, and CurrencyIsoCode. The CSV is uploaded as an Upsert against the ForecastingQuota object with an external ID composed from User + StartDate + ForecastingType. Repeated loads in the same period update existing records rather than creating duplicates. Most enterprise sales operations teams run this load monthly or quarterly as part of the sales planning cycle.
Quota by user vs quota by territory
Two quota models exist. User-based quotas assign the target to a specific salesperson. Territory-based quotas assign the target to a Territory in Enterprise Territory Management. Territory quotas roll up to the territory's assigned users. The choice depends on the org's sales model. A flat sales team with one rep per region uses user-based quotas. A complex enterprise with overlay reps, channel partners, and account teams uses territory-based quotas to model the shared accountability. Switching between models mid-year is painful; pick early.
Forecast Types and quota alignment
The Collaborative Forecasts feature supports multiple Forecast Types per org: Opportunity Revenue, Opportunity Quantity, Opportunity Splits, Custom Number, Custom Currency, Product Family. Each forecast type can have its own quotas. A team forecasting both Revenue and Margin needs separate quotas for each, loaded separately, and reported separately. The Forecast Settings page in Setup is where the active Forecast Types are configured. Adding a new Forecast Type does not auto-populate quotas; the next quota load needs to include the new type.
Quota attainment and the Forecast UI
With quotas loaded, the Collaborative Forecasts UI shows each user's pipeline against their quota: Closed, Commit, Best Case, Pipeline. Attainment percentage (Closed / Quota) appears as a column. Managers see their direct reports' attainment as a roll-up. Aggregation rules (sum, weighted, custom) are configured per Forecast Type. The Forecast UI is the primary consumption surface; reports and dashboards built on Forecast objects supplement it for executive views.
Adjustments and the manager override
Quotas can be edited by managers through Collaborative Forecasts. A manager can adjust their direct report's quota up or down with explicit attribution. The platform tracks the original quota, the adjusted quota, and the manager who made the adjustment. This is the mechanism for mid-period quota changes (promotions, departures, scope adjustments). Most companies discourage frequent adjustments because they distort historical attainment metrics. The audit trail is what keeps the practice honest.
API and integration patterns
ForecastingQuota is queryable through SOQL and writable through DML, the REST API, and Bulk API. The standard integration pattern is: sales planning system (Anaplan, Xactly, Salesforce Sales Performance Management) holds the master quota plan, an integration pushes the plan into Salesforce monthly. The integration is straightforward: an upsert against ForecastingQuota keyed on User + StartDate + ForecastingType. The complexity is on the planning side, not the Salesforce side. Once the data lands, the Forecast UI does the rest.
Loading and managing Quotas in Salesforce
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.
Trust & references
Straight from the source - Salesforce's reference material on Quota.
- Quotas in ForecastsSalesforce Help
- Load Quotas Through Data LoaderSalesforce Help
- ForecastingQuota ObjectSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Quota in Sales Cloud?
Q2. What do quotas measure?
Q3. What makes a good quota?
Discussion
Loading discussion…