If you have just deleted a lead in Salesforce, you can usually get it back. Deleted leads sit in the Recycle Bin for 15 days, and restoring them is a few clicks. This guide walks through how to restore deleted leads in Salesforce across all four recovery paths, from the Recycle Bin to Data Loader to enterprise backups, plus what to do once the 15-day window has closed and the leads have been purged.

Salesforce provides those four recovery paths based on two factors: how much time has passed since deletion and how many records need restoration. Within the 15-day retention window, the Recycle Bin handles small batches through point-and-click restoration, while Data Loader manages bulk operations through scripted processes. After the retention window closes, recovery depends on weekly export files or continuous backup platforms that capture data outside Salesforce's native retention limits.

Each method carries distinct prerequisites, capabilities, and limitations. The Recycle Bin requires no special tools but caps storage at 25 times the org limit. Data Loader demands API access and technical knowledge but generates audit logs and handles thousands of records in a single operation. Weekly exports provide a free backup option but create gaps between snapshot intervals. Enterprise backup platforms eliminate those gaps through continuous monitoring but require dedicated subscriptions.

Can You Restore Deleted Leads in Salesforce?

Yes, in most cases, as long as you act within the retention window. When a lead is deleted, it is soft-deleted: it moves to the Recycle Bin and stays recoverable for 15 days. During that window you can restore a handful of leads from the Recycle Bin or run a bulk undelete with Data Loader. Once Salesforce purges the record, native undelete no longer applies, and recovery depends on a weekly export file or a backup platform that captured the data.

Two things can shorten that window. The Recycle Bin holds only up to 25 times your org's data storage, so in high-volume orgs older records can be purged before 15 days are up, with no warning. And a manual empty of the Recycle Bin or a hard delete through the API removes records immediately. The table below maps each situation to the right recovery method, and the sections that follow give the exact steps for each. For bulk work, Data Loader is the tool of choice.

Method 1: Recycle Bin Restore

The Recycle Bin is the fastest route back from an accidental deletion, best for quick, small-volume recovery within the retention window. In Lightning Experience, open the App Launcher, search for Recycle Bin (or choose View All, then Recycle Bin), and open it. In Salesforce Classic, click the Recycle Bin link in the left sidebar of the Home page.

Salesforce shows two views. My Recycle Bin displays only the items the current user deleted. All Recycle Bin requires the Modify All Data permission and displays every deleted record across the organization. Most administrators need the All Recycle Bin view to recover leads deleted by other team members, so check which view you are in before you search.

Filter by object type or keyword, mark the Lead records to recover, and click Restore. The leads return with their attachments and related activities intact, and their original owner, status, and history remain unchanged.

Knowing the boundaries of the Recycle Bin helps you plan alternative recovery paths before you need them. Storage constraints and retention policies can force early deletion of records teams may still need.

Key limitations:

• Retention period of 15 days by default. It can be extended to 30 days only in Salesforce Classic, using the Extended Recycle Bin Retention feature, which is activated through Salesforce Support. Lightning Experience does not offer a configurable retention setting.
• Storage capacity capped at 25 times the org limit, and records can be purged early once that cap is reached.
• Manually emptying the Recycle Bin, or a hard delete through the API, causes immediate permanent deletion.

After restoring records, move to the Post-Recovery Checklist to confirm data integrity. When thousands of leads must be recovered at once, or you need detailed audit logs of the recovery, Data Loader provides scripted control the Recycle Bin interface cannot match.

Method 2: Data Loader Bulk Undelete

Data Loader handles high-volume lead recovery within the retention window through repeatable, logged operations. When thousands of leads disappear at once or automation logs must capture every change, Data Loader offers a controlled, repeatable recovery path. This command-line tool connects directly to Salesforce APIs and processes records in batches, making it suitable for volume scenarios where the standard interface becomes impractical. The undelete operation specifically targets soft-deleted records that still exist in the system but are marked for removal.

Step 1: Export Deleted Records

Begin by extracting all deleted leads from Salesforce to review and filter them before restoration. Launch Data Loader and sign in with a profile that includes API Enabled and Modify All Data permissions. Choose Export All, which retrieves both active and deleted records. Build a SOQL query that targets deleted leads:

SELECT Id, Name, Company, Status FROM Lead WHERE IsDeleted = TRUE

Save the results as a CSV file, then remove any rows that should remain deleted. With a clean export file in hand, the next step reverses the deletion flags and restores the leads to active status.

Step 2: Execute the Undelete Operation

Upload the cleaned CSV file and run the undelete operation to restore leads to active status. Once a clean export file contains only the leads to restore, the next phase involves mapping that data back into Salesforce through the undelete operation. This step reverses the deletion flag on each record and triggers any associated workflows or validation rules. Careful preparation during this phase prevents errors that could delay recovery or leave gaps in the restored dataset.

Map each column to the correct Lead field. In Data Loader, select the Undelete operation, upload the file, and run the job.

Watch API consumption because every batch counts toward the daily limit. Keep batch size at fifty thousand records or fewer to prevent timeouts. Data Loader enforces every validation rule and trigger, so temporarily disable automations that could reject valid data during the restore process.

After the job completes, inspect the success and error logs. Address mapping mistakes, permission gaps, or picklist mismatches, then reprocess failed rows. When errors appear in the logs, systematic troubleshooting resolves the most common issues quickly.

Troubleshoot Common Errors

Error logs identify the specific problems that prevent successful restoration so teams can address them and retry failed records. Even well-prepared Data Loader operations hit errors from field-level security, validation rules, deleted parent records, or API limits. Understanding the most common patterns helps you resolve issues quickly and complete the restore without extended delays.

• API limit errors: Split files into batches of fifty thousand records or fewer to stay within the daily API allocation.
• Field mapping failures: Verify that source column headers match destination field API names exactly, including proper capitalization.
• Permission errors: Confirm the user profile includes both Modify All Data and API Enabled permissions.
• File size warnings: When the CSV file exceeds one hundred fifty megabytes, split the data into multiple smaller files before processing.
• Deleted parent or lookup records: If a lead points to a related record that was also deleted, such as a campaign or a since-deactivated owner, the undelete can fail or restore the lead without its relationship. Restore or recreate the parent record first, then re-run the lead undelete.
• Validation rules blocking the restore: Undelete runs active validation and required-field rules, so a lead that was valid when created can be rejected if the rules changed since. Temporarily deactivate the blocking rule or automation, restore the records, then re-enable it.

This method restores bulk-deleted leads without changing record IDs and generates logs that satisfy audit requirements. Once the retention window closes and the undelete operation no longer applies, recovery shifts to reconstructing leads from backup sources.

Method 3: Weekly Export Reconstruction

Once Salesforce purges records, the Recycle Bin and Data Loader undelete functions no longer apply, and recovery shifts to your own backup files. Before you start, be clear about what this method is: it does not restore your original leads, it recreates them from a CSV snapshot.

That distinction matters. A true restore (the Recycle Bin or a Data Loader undelete) brings back the exact records with their history intact. Reconstruction inserts new records built from an older export, so anything that changed between the export date and the deletion is lost, and attachments, campaign memberships, and field history do not come back with the object data. Recovery from a weekly export is a fallback, not an equivalent, and it works only if an export that predates the deletion exists.

With those limits understood, here is how to locate, clean, and load exported lead data.

Step 1: Locate and extract the export. Salesforce's Data Export service delivers a compressed archive of CSV files on a weekly or monthly schedule. Find the most recent export that predates the deletion event, unzip the package, and open Lead.csv.

Step 2: Identify missing records. Compare the file against current lead data to isolate the missing records. A spreadsheet VLOOKUP or a simple diff utility identifies gaps quickly. Clean the dataset by removing obsolete columns and verifying mandatory fields such as LastName and Company.

Step 3: Prepare for reconstruction. Retain the original Id column. With the Id present, Data Loader's Insert operation can recreate records with their original identifiers, preserving lookups and relationships.

Step 4: Load the cleaned file. Load the cleaned CSV through Data Loader using the Insert operation. Map fields carefully and process the batch. Remember that weekly exports capture only object data; attachments, campaign memberships, and field history require separate restoration.

Because the export runs on a fixed schedule, any activity between the export date and the deletion date is at risk of loss. For organizations that need complete data fidelity and point-in-time recovery without gaps, enterprise backup platforms offer continuous protection beyond what scheduled exports can provide.

Method 4: Enterprise Backup Platform Restore

Enterprise backup platforms restore purged leads with point-in-time precision and complete relationship integrity. Unlike scheduled exports that capture snapshots at fixed intervals, continuous backup solutions track every change as it occurs in Salesforce. This approach eliminates gaps in recovery coverage and provides the flexibility to restore data from any moment in time, not just from the most recent export cycle.

Enterprise backup platforms like Flosum Backup & Archive capture full and incremental backups of both data and metadata. The application layer operates inside Salesforce for a seamless admin experience, while backup data is stored in a secure, scalable environment designed for large volumes. This design keeps production performance high while maintaining enterprise-grade security that meets SOC 2, HIPAA, and GDPR requirements.

The operational benefits extend beyond simple data recovery:

• Granular restores at field, record, or object level
• Composite backup model that records only deltas
• Role-based access controls with detailed audit trails
• Flexible deployment (hosted, customer cloud, or on-premise)

To restore purged leads, open Flosum Backup & Archive from the Salesforce App Launcher. Filter backups by date, user, or object, then preview the specific backup containing the deleted leads. Select a single record or an entire batch, click Restore, and Flosum replays the data, relationships, and field history into production.

Review the success log, then rerun assignment rules or workflows as needed. Regardless of which recovery method was used, systematic post-recovery validation ensures that restored leads function properly in the production environment.

Post-Recovery Checklist

Verify data integrity and resume business processes immediately after any restore operation to prevent downstream issues. Restoration alone does not guarantee the org returns to its pre-deletion state: validation rules may have changed, workflows may have updated, and related records may have been modified in the interim. Use the checklist below as a quick pass, then work through the detailed steps that follow.

Verify Data Accuracy

Confirm that restored records contain correct values and that all related data returned intact. The first priority after any restore operation involves confirming that the right records returned with the right data. Missing fields, incorrect values, or gaps in related records create downstream problems that multiply as sales teams interact with the restored leads. A structured verification process catches these issues immediately, when they are easiest to fix.

• Compare record counts: Run a report filtered by Created Date or Last Modified Date to confirm the total matches the expected restore batch.
• Confirm critical fields: Spot-check Lead Status, Owner, and key custom fields, especially picklists with strict validation.
• Verify related data: Open sample restored leads to confirm tasks, notes, and attachments are present.
• Test visibility: Log in as a standard sales user and confirm leads appear in views, reports, and search results.

With data accuracy confirmed, turn attention to the automated processes that depend on those leads.

Resume Business Processes

Once the data passes accuracy checks, shift focus to the business processes that depend on those leads. Assignment rules, lead queues, and conversion logic often rely on record events that did not fire while the lead was missing. Re-run those rules manually or with a one-time batch job. Review active workflows, Process Builder flows, and Apex triggers for errors, then resume any paused automations.

With business processes running smoothly, the final step involves coordinating with the teams affected by the deletion and recovery.

Communicate with Stakeholders

Recovery operations affect multiple teams. Each team needs clear information about what changed and what actions they should take:

• Sales representatives need to know which leads returned to their queues and whether any ownership assignments changed during the deletion window.
• Marketing teams need confirmation that campaign members are back in place before launching new outreach.
• Operations teams need to verify that integrations resumed properly and that no duplicate records were created during the gap.

Provide affected sales representatives with a report listing every lead restored, including ownership changes. If duplicates emerged while original records were gone, coordinate with the data stewardship team to merge them before the next campaign launch.

For forty-eight hours after restoration, monitor error logs, integration queues, and key pipeline dashboards. Early anomalies often signal hidden data issues that slipped through initial checks. Once validation confirms successful restoration, pipeline data is secure and the recovery operation is complete.

Protect Pipeline Data from Lead Loss

Every recovery method above is reactive: it starts after leads are already gone, and each one is a race against the 15-day clock. The only way to remove that cliff is to protect the data before it disappears. Weekly exports and manual reconstruction can work when data loss is rare and a few hours of rebuilding is acceptable, but they leave gaps between snapshots and lose attachments, history, and relationships.

Continuous backup closes those gaps. When lead data ties directly to revenue, when compliance requires complete audit trails, or when a complex, integrated org raises the cost of a single failed recovery, an enterprise backup platform pays for itself the first time it prevents permanent loss. Flosum Backup & Archive captures continuous, field-level backups of Salesforce data and metadata, so restoring deleted leads becomes a controlled, point-in-time operation instead of a scramble.

Request a demo with Flosum to see how field-level recovery and automated backups eliminate the risk of permanent lead loss.

Frequently Asked Questions