Mass Delete Records
Mass Delete Records is the Salesforce Setup feature that lets administrators delete records in bulk from a small list of supported objects: Accounts, Leads, Contacts, Activities (Tasks and Events), Cases, Solutions, Products, and a few others.
Definition
Mass Delete Records is the Salesforce Setup feature that lets administrators delete records in bulk from a small list of supported objects: Accounts, Leads, Contacts, Activities (Tasks and Events), Cases, Solutions, Products, and a few others. The tool runs through a guided UI where the admin selects the object, sets filter criteria, previews matching records, and confirms deletion. Each operation caps at 250 records per run, making the tool useful for targeted cleanup rather than large data purges.
For deletions exceeding 250 records or on unsupported objects, Data Loader is the standard alternative. Mass Delete Records lives in Setup precisely because it is a sensitive operation requiring the administrator privilege; it cannot be run as a regular user even with Delete object permission. The 250-record cap is a safety mechanism: even an administrator clicking through the wizard cannot wipe out tens of thousands of records in one operation. For large cleanup, the admin must explicitly choose Data Loader or another bulk path.
How Mass Delete Records works
Supported objects
Mass Delete supports a fixed list: Accounts, Leads, Contacts, Activities (Tasks and Events combined), Cases, Solutions, Products. Custom objects are not supported through this tool; for custom objects, use Data Loader or a scheduled Apex batch. The list reflects historical Salesforce design; the supported objects are the ones where bulk admin deletion is most commonly needed.
The 250-record cap
Each run caps at 250 records. This is intentional safety: even an admin cannot accidentally wipe huge volumes in one click. For larger deletions, multiple runs or Data Loader are required. The cap also limits the impact of a single mistake; recovering 250 deletions from the Recycle Bin is feasible, while recovering 50,000 is not.
Filter criteria
The tool lets administrators filter the deletion candidates with simple criteria: field equals value, contains, starts with. Complex filters (subqueries, multi-object logic) are not supported; for those, use the Data Loader extract-and-delete pattern. The filter is the safety mechanism for targeting specific records; build it carefully.
Preview before delete
The wizard shows a preview of records matching the filter before deletion. Verify the preview matches expectations; the preview is the last opportunity to catch a filter mistake. If the count is unexpected or sample records look wrong, cancel and refine the filter.
Recycle Bin recovery
Deleted records go to the Recycle Bin and remain recoverable for 15 days. Recovery is straightforward through the standard Recycle Bin UI. After 15 days, records are permanently purged. For high-stakes deletions, schedule a verification window during the recoverable period to confirm no critical records were lost.
Triggers and automation
Mass Delete fires triggers, validation rules, and process automation just like a normal DML. If your org has Apex triggers on the target object, they run for every deleted record. Validation rules block deletion if they fail (rare but possible for delete-time rules). Plan around any heavy automation; bulk delete operations can hit governor limits.
Data Loader alternative
For deletions exceeding 250 records, on unsupported objects, or requiring complex filters, Data Loader is the standard alternative. Extract records matching the criteria (Data Loader Extract), then delete by Id (Data Loader Delete). The two-step process is slower but supports any volume and any object. Data Loader Hard Delete bypasses the Recycle Bin; use with extreme caution.
Run a Mass Delete safely
Running Mass Delete safely is about precise filtering and a verification window. The steps below cover both halves.
- Confirm Mass Delete is the right tool
For under 250 records on supported objects, Mass Delete fits. Larger or unsupported needs Data Loader.
- Identify the target records
Define exactly which records to delete. Document the criteria and expected count.
- Open Mass Delete
Setup > Data > Mass Delete Records. Choose the object type.
- Set filter criteria
Define the filter matching your target records. Keep it precise; broad filters risk over-deletion.
- Preview results
Click Search. Review the preview list. Confirm count matches expectations and sample records are correct.
- Execute deletion
Check the boxes for records to delete (Select All if preview is fully correct). Click Delete. Confirm.
- Verify and watch for recovery period
Confirm successful deletion. Set a calendar reminder for 14 days to investigate any restore requests before the Recycle Bin window expires.
Object selection. Limited to supported types.
Field-equals or field-contains conditions. Simple compared to Data Loader.
Records matching the filter, shown before deletion confirms.
Granular check-box selection within the preview.
15-day recovery window after deletion.
- 250-record cap. Plan multiple runs for larger needs, or switch to Data Loader.
- Only specific objects supported. Custom objects need Data Loader.
- Triggers and validation rules fire on Mass Delete. Heavy automation can hit governor limits.
- Preview is the last safety check. Verify count matches expectations before confirming.
- Recycle Bin recovery is 15 days only. After that, records are permanently purged.
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. Why is understanding Mass Delete Records important for Salesforce admins?
Q2. Can a Salesforce admin configure Mass Delete Records without writing code?
Q3. In which area of Salesforce would you typically find Mass Delete Records?
Discussion
Loading discussion…