Data Classification Download
Data Classification Download is the Salesforce Setup utility that exports the org's current Data Classification metadata (per-field classifications like Sensitivity Level, Compliance Categorization, and Data Owner) as a CSV file.
Definition
Data Classification Download is the Salesforce Setup utility that exports the org's current Data Classification metadata (per-field classifications like Sensitivity Level, Compliance Categorization, and Data Owner) as a CSV file. Admins use the download to review classifications offline, share with compliance teams, validate against external data inventory systems, or feed into separate compliance tooling. The downloaded CSV contains one row per classified field with the field's object, API name, label, and the classification values currently assigned.
Data Classification Download exists because field-by-field classification review in Setup is slow. A large org with thousands of custom fields needs a bulk view to audit which fields are properly classified, which are missing classifications, and whether the classifications align with the org's data governance policy. The downloaded CSV is the analysis surface; the matching Data Classification Upload utility is how bulk classification changes flow back into the platform.
Why bulk download is essential for data classification at any meaningful scale
Where Data Classification Download lives
Setup, Data Classification Settings includes the Download button (and the matching Upload button). The download produces a CSV with one row per field that has any classification metadata, plus optionally one row per field regardless of classification status if the admin chooses Include All. The CSV columns include Object API Name, Field API Name, Field Label, Sensitivity Level, Compliance Categorization, Data Owner, Data Sensitivity Description, Last Modified Date, and Last Modified By.
The classification dimensions
Salesforce ships several classification dimensions admins can populate per field. Sensitivity Level captures the data sensitivity (Public, Internal, Confidential, Restricted). Compliance Categorization captures regulatory scope (PII, PCI, HIPAA, GDPR). Data Owner captures who owns the data definition (team or person). Data Sensitivity Description is a free-text field for additional context. Each dimension is independent; a field can be Confidential + PII + owned by Compliance Team. The combination is the metadata that drives downstream compliance tooling and risk assessment.
Use cases for the downloaded CSV
Three patterns recur. Compliance review: pull the CSV, filter for fields missing classification, assign classifications, upload back. Policy alignment: pull the CSV, validate that fields tagged PII have appropriate access controls (sharing rules, FLS), produce findings for remediation. External integration: pull the CSV, feed into a separate data catalog or governance tool (Collibra, Alation, custom inventory), align Salesforce's classification with the enterprise data inventory.
Coverage gaps and the missing-classification audit
Most orgs do not classify every field. The download surfaces gaps; fields that exist in the schema but have no classification are candidates for compliance review. The gap analysis: filter the CSV for rows without Sensitivity Level or Compliance Categorization, prioritize by object (customer-facing objects first), assign default classifications, upload back. Most first-time runs reveal that 60 to 80 percent of custom fields lack classification metadata; the bulk pattern is the only practical way to close the gap.
Standard vs custom fields and the scope decision
The download covers both standard and custom fields. Standard fields ship with Salesforce-default classifications in some cases (Email field on Contact is marked PII by default in some recent releases); custom fields ship with no classification by default. The org's data governance policy usually requires classification on every custom field and acceptance of Salesforce defaults on standard fields, with overrides where the org's interpretation differs (a custom industry might classify the Phone field as more sensitive than Salesforce's default).
Frequency, automation, and the audit cadence
Data Classification Download is not automated by default; admins run it on demand. For compliance-heavy orgs, the pattern is to run the download monthly or quarterly, diff against the previous download, identify new fields added without classification, follow up with the owning team to classify. Automating the run is possible via the Metadata API but most orgs do it manually; the monthly cadence is cheap enough that automation rarely pays off.
Integration with broader data governance
The downloaded classifications are most valuable when fed into broader data governance tooling. Enterprise data catalogs (Collibra, Alation, Atlan) ingest the CSV to align Salesforce field classifications with classifications across the rest of the data estate. Privacy management tools (OneTrust, Privacera) ingest the CSV to scope DSR (data subject rights) workflows. The download is the integration point; the value compounds when the classifications drive cross-system policy.
How to use Data Classification Download for compliance audit
The pattern: download monthly, identify gaps and drift, follow up with field owners, upload corrections. The cycle is the discipline that keeps Data Classification meaningful; without it, classifications go stale fast.
- Open Setup, Data Classification Settings
The page hosts both Download and Upload utilities for Data Classification metadata.
- Click Download to generate the CSV
Choose Include All (every field) or Classified Only (fields with at least one classification dimension populated). Include All is the right pick for compliance audit.
- Open the CSV in your analysis tool
Excel, Google Sheets, or a data tool. Filter, pivot, and analyze. Pivot by Sensitivity Level to see distribution; pivot by object to see per-object coverage.
- Identify gaps: fields without classification
Filter for rows where Sensitivity Level is empty or Compliance Categorization is empty. The list is the compliance-debt backlog.
- Assign default classifications for the gaps
Use a default (Internal sensitivity, no compliance categorization) or coordinate with field owners for accurate classification. Update the CSV in place.
- Upload the updated CSV via Data Classification Upload
The Upload utility ingests the corrected CSV. Classifications update on the matching fields without code deployment.
- Schedule the next monthly download
Diff against this month's download to identify drift. New fields added without classification are the most common drift signal.
Whether the CSV includes every field or only fields with at least one classification dimension populated.
Sensitivity Level, Compliance Categorization, Data Owner, Description. Each captures a different aspect.
Monthly or quarterly download for compliance-heavy orgs. Annual is too infrequent for actively-evolving schemas.
Excel, Sheets, or external data catalog. The tool consumes the CSV.
Data Classification Upload utility ingests the corrected CSV without code deployment.
- Download is not automated by default. Manual cadence is the standard pattern; automation requires Metadata API scripting.
- Include All produces large CSVs for big orgs (thousands of rows). Filter and pivot tools are required for analysis.
- Standard field defaults vary by release. Salesforce ships PII defaults on common fields; the defaults may not match the org's specific policy.
- Field owners are required for accurate classification. Defaults work as placeholders; accurate classification requires the owning team's input.
- Classifications go stale as fields are added or repurposed. The monthly cadence is the only reliable freshness mechanism.
Trust & references
Cross-checked against the following references.
- Data Classification referenceSalesforce
- Salesforce security overviewSalesforce
Straight from the source - Salesforce's reference material on Data Classification Download.
- Data ClassificationSalesforce Help
- Download Data ClassificationSalesforce Help
- Upload Data ClassificationSalesforce Help
Hands-on resources to go deeper on Data Classification Download.
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 the primary benefit of Data Classification Download for Salesforce administrators?
Q2. Can a Salesforce admin configure Data Classification Download without writing code?
Q3. Why is understanding Data Classification Download important for Salesforce admins?
Discussion
Loading discussion…