Data Classification Upload
Data Classification Upload is the Salesforce Setup utility that ingests a CSV of per-field classification metadata and applies the changes to the org's field definitions in bulk.
Definition
Data Classification Upload is the Salesforce Setup utility that ingests a CSV of per-field classification metadata and applies the changes to the org's field definitions in bulk. Admins typically use Upload after downloading the current classification state via Data Classification Download, editing the CSV offline to add missing classifications or update existing ones, and uploading the corrected file. The Upload applies Sensitivity Level, Compliance Categorization, Data Owner, and Data Sensitivity Description values from the CSV to the matching fields without code deployment.
Data Classification Upload exists because per-field classification through Object Manager is impractical past a few dozen fields. A regulated org with thousands of custom fields needs the bulk path; the Upload utility provides it. The Download/Upload pair forms the complete bulk audit workflow: download current state, fix gaps and drift offline, upload corrections. The pattern is the only practical way to maintain accurate classifications at organizational scale.
Why bulk upload is the only practical classification path past trivial scale
Where Data Classification Upload lives in setup
Setup, Data Classification Settings includes the Upload button (paired with Download). The Upload accepts a CSV in the same schema the Download produces: Object API Name, Field API Name, plus columns for each enabled classification dimension. Rows in the uploaded CSV update the matching field metadata. Rows whose Object/Field combination does not match an existing field produce errors and are skipped; rows that match are applied. The Upload runs synchronously for small files and queues for large files.
The Download-Edit-Upload cycle
The intended workflow is round-trip. Download produces the current state. Admin opens the CSV in a spreadsheet tool, filters for rows missing classification or with stale classification, updates the values. Upload ingests the corrected CSV; the platform applies the changes. The cycle is what makes Data Classification maintainable; without it, classification updates per field is too slow for any org with more than a few dozen custom fields.
CSV schema and the match requirements
The Upload CSV must include Object API Name and Field API Name to identify each row's target field. Classification dimension columns (Sensitivity Level, Compliance Categorization, Data Owner, Data Sensitivity Description) hold the values to apply. Empty values in the CSV typically clear the corresponding classification on the field (or leave it untouched depending on Upload mode). Extra columns are ignored. Misspelled API names produce errors; case sensitivity is enforced on object and field identifiers.
Validation, errors, and the result file
The Upload validates each row before applying. Invalid value (a Sensitivity Level value not in the org's value set), missing required column, or unmatched Object/Field combination produces an error logged in the result file. The result file lists per-row success or failure with error messages. Successful rows applied; failed rows skipped. Admins download the result file, fix errors in the source CSV, re-upload the corrected subset. The cycle is similar to Bulk Data Load Jobs; partial-success-with-error-log is the standard pattern.
Upload modes: update vs replace
Upload supports modes that control how empty CSV values interact with existing classifications. Update mode leaves existing values untouched if the CSV cell is empty; only non-empty CSV values apply. Replace mode clears existing values if the CSV cell is empty. Most audit workflows use Update mode (the CSV has corrections, leaving rows that did not change alone); Replace mode is for full-rewrite scenarios. The mode choice is the difference between additive edits and authoritative restatements; pick deliberately.
Volume, throughput, and large-org considerations
Upload throughput is sufficient for most org-scale bulk updates; a few thousand rows applies in minutes. For very large orgs with tens of thousands of fields, the Upload may need to be batched into multiple files. Salesforce throttles to prevent the Upload from monopolizing the org; bulk-upload spikes during normal business hours may compete with user-facing requests. Schedule large uploads for off-hours when feasible.
Audit trail and the compliance evidence
Upload-applied classification changes write to the Field History on FieldDefinition (when tracking is enabled) and to the SetupAuditTrail standard log. Auditors asking "who changed the PII classification on Account.SSN__c on January 15" get an answer from the audit trail. The audit evidence is one of the compliance benefits of using the Upload utility (versus direct API metadata changes that may not log the same way). Maintain the audit trail retention per the org's compliance policy.
How to use Data Classification Upload for bulk classification updates
The pattern: download, edit offline, upload, verify result file, fix errors and re-upload. The cycle is fast for small updates (under 100 rows) and manageable for bulk audit work (thousands of rows). Always test in sandbox before applying to production.
- Download current classification state via Data Classification Download
The CSV is the starting point. Save with a timestamped filename so the audit cycle is traceable.
- Edit the CSV offline
Add missing classifications, update stale ones, coordinate with field owners on accurate values. Save the corrected CSV.
- Validate the CSV schema before upload
Confirm column headers match the expected schema, Object API Name and Field API Name spelling is correct, classification values match the org's value sets.
- Upload in sandbox first
Test on a sandbox with similar field schema. Verify the result file shows expected successes and errors.
- Upload in production
Setup, Data Classification Settings, Upload. Pick the CSV. Pick the Upload mode (Update for additive, Replace for authoritative). Submit.
- Review the result file
The Upload produces a per-row success/failure CSV. Save it as evidence of the change. Identify failed rows for correction.
- Fix errors and re-upload the corrected subset
Build a corrected CSV with only the failed rows. Re-upload. Iterate until all rows succeed or the failures are documented as intentional non-updates.
Update (leave empty cells untouched) or Replace (clear classifications for empty cells). Pick deliberately.
Object API Name, Field API Name, plus columns per enabled classification dimension. Match the Download schema.
Errors on invalid values, missing required columns, unmatched fields. Some orgs configure stricter validation than defaults.
Per-Upload row count. Smaller batches make error recovery faster; larger batches reduce ceremony.
Large uploads benefit from off-hours timing to avoid competing with user-facing requests.
- Misspelled API names produce errors. Object and field identifiers are case-sensitive; pull the correct spelling from the Download CSV.
- Replace mode clears classifications for empty CSV cells. Use Update mode unless the CSV is authoritative; otherwise the upload destroys existing classifications.
- Invalid classification values (a Sensitivity Level not in the org's value set) produce errors. Validate values against the org's policy before upload.
- Large uploads compete with user-facing requests. Schedule for off-hours on big orgs.
- Sandbox first is non-optional for production-affecting bulk updates. The sandbox dress rehearsal catches schema issues at the right time.
Trust & references
Cross-checked against the following references.
- Data Classification Upload referenceSalesforce
- Salesforce security overviewSalesforce
Straight from the source - Salesforce's reference material on Data Classification Upload.
- Upload Data ClassificationSalesforce Help
- Download Data ClassificationSalesforce Help
- Data Classification OverviewSalesforce Help
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. In which area of Salesforce would you typically find Data Classification Upload?
Q2. Can a Salesforce admin configure Data Classification Upload without writing code?
Q3. What is the primary benefit of Data Classification Upload for Salesforce administrators?
Discussion
Loading discussion…