

Every sales leader knows this scene: end of quarter, a forecast full of ghosts. Stale opportunities linger in Salesforce, padding pipeline reports and confusing every revenue meeting. Reps promise to clean things up “later,” but later never comes.Learning how to delete an opportunity in Salesforce isn’t about button clicks; it’s about data trust. When dead deals stay open, marketing campaigns misfire, capacity plans skew, and your Google Sheets summaries stop matching what’s really happening on the floor.This is where delegation matters. Instead of asking your highest-paid closers to hunt down old records, you can:Have an AI computer agent read a curated Google Sheets list, open each Salesforce opportunity, confirm status, and delete it with an audit trail. In 400–500 clicks a human would dread, the agent simply executes. You get cleaner forecasts, faster decisions, and a team focused on winning deals—not tidying databases.
### 1. Manual ways to delete opportunities in SalesforceBefore we automate anything, you need to be rock-solid on the native Salesforce paths. These are the playbooks your AI agent will eventually follow.#### 1.1 Delete a single opportunity from the record page1. Log in to Salesforce and go to the **Opportunities** tab from the top navigation bar.2. Use the search bar or list views to find the specific opportunity.3. Click the **Opportunity Name** to open the record.4. In Lightning Experience, click the **Delete** button in the top-right corner of the record (in Classic, look for the **Delete** button near the top).5. Confirm in the pop-up dialog. Salesforce moves the record to the **Recycle Bin**.Official overview of Opportunities: https://help.salesforce.com/s/ (search for “Opportunities”).#### 1.2 Delete from the Opportunities list view1. Navigate to **Opportunities**.2. Choose a relevant list view (e.g., **My Closed Opportunities**, **Stale Deals > 90 days**).3. Hover over the row you want to delete.4. Click the **down arrow** at the right of the row and choose **Delete**, or use the **Del** link if it appears.5. Confirm deletion in the pop-up.This is ideal when you’re eyeballing one-off bad records, but it doesn’t scale.#### 1.3 Bulk-delete via list view (multi-select)1. From **Opportunities**, open or create a list view filtered for deals you plan to delete (e.g., **Stage = Closed Lost** AND **Last Activity Date < LAST_YEAR**).2. Click the **checkbox** column in the header to select all, or tick specific deals.3. Click **Delete** (or **Delete Selected**) from the list view actions.4. Confirm. All selected opportunities move to the **Recycle Bin**.Pros: Fast for dozens of records. Cons: Easy to make mistakes if filters are sloppy—always double-check your criteria.#### 1.4 Delete from the Account or Contact related list1. Open an **Account** or **Contact** record.2. Scroll to the **Opportunities** related list.3. Click the **Del** link next to the opportunity you want to remove.4. Confirm deletion.This is useful when cleaning a specific customer’s history before handover.#### 1.5 Restore from the Recycle Bin (safety net)1. Click the **App Launcher** (grid icon) and search for **Recycle Bin**, or click **Recycle Bin** from your profile menu (depending on your org setup).2. Filter for **Opportunities**.3. Select the records you want to restore.4. Click **Undelete**.Salesforce also restores most related items (tasks, events, notes) when an opportunity is undeleted.Learn more about deletion and recovery: start at https://help.salesforce.com/s/ and search “Recycle Bin”.---### 2. No-code automation methods (less clicking, more rules)Once you’ve mastered the manual path, you can start reducing human touches.#### 2.1 Salesforce Flow for auto-cleanup**Salesforce Flow** (Setup → **Flows**) lets you set rules like “auto-delete lost deals older than 18 months.”High-level steps:1. Go to **Setup → Process Automation → Flows**.2. Create a **Scheduled Flow** that runs nightly.3. Add a **Get Records** element for **Opportunity** with filters: - **Stage = Closed Lost** - **Last Modified Date <= TODAY() - 540** (18 months) or your timing.4. Loop through the collection.5. For each record, add a **Delete Records** element.6. Test in a **sandbox** first with a very small sample and logging.Pros: Native, no external tools, repeatable. Cons: Less transparent to non-admins, easy to misconfigure.Docs hub for Flow: https://help.salesforce.com/s/ (search “Salesforce Flow Basics”).#### 2.2 Google Sheets as a human-approval layerYou don’t have to delete directly from Salesforce. Many RevOps teams prefer an approval spreadsheet.1. Export candidate opportunities from Salesforce (via **Reports → Export**) into **Google Sheets**, or connect via **Data Connector for Salesforce** (official add-on: https://workspace.google.com/marketplace/app/data_connector_for_salesforce/568123958505).2. Add columns like **Owner Approval (Y/N)**, **Reason**, **Keep?**.3. Share the sheet with sales managers to mark which deals should be removed.4. Use **filters** and **conditional formatting** in Sheets to highlight records approved for deletion.5. Once approved, your admin or ops person manually deletes those opportunities in Salesforce using the steps in Section 1.Pros: Clear audit trail, easy collaboration. Cons: Still manual at the final step.#### 2.3 iPaaS tools (Zapier/Make) with Google SheetsNo-code platforms can bridge Google Sheets and Salesforce.Conceptual flow:1. Trigger: A new row in a specific **Google Sheets** tab marked `Delete = TRUE`.2. Look up the **Opportunity ID** or an external ID in Salesforce.3. Call **Delete Record** action on the Opportunity.4. Log the result (success/failure) back in Sheets.You’ll need:- A Salesforce connection (with API access).- A strict mapping between the Sheets row and the Salesforce Opportunity (ID is best).Pros: Good for admins comfortable with no-code tools. Cons: Still rule-based; doesn’t “think” like a user, limited for complex exceptions.---### 3. AI agent workflows at scale (Simular-style automation)Now the fun part: letting an AI computer agent handle the clicks just like a human—only faster and without complaining.Imagine this weekly story:- Your RevOps leader curates a **Google Sheets** tab of opportunities to retire: IDs, links, reasons, manager sign-off.- A Simular AI agent runs every Friday night.- It opens your browser, logs into **Salesforce**, cross-checks each row, and deletes the right records while you sleep.#### 3.1 Agent reads Sheets, cleans SalesforceWorkflow:1. Configure a **Simular Pro** agent on your Mac (see https://www.simular.ai/simular-pro).2. Give it access to: - Your browser where Salesforce runs. - The Google Sheet containing opportunities to delete.3. High-level task description you’d provide: - Open the Google Sheet `Stale_Opportunities_To_Delete`. - For each row where `Delete = TRUE`, open the Salesforce link or search by Opportunity ID. - Verify Stage and dates match the row (to prevent mismatches). - Click **Delete**, confirm in the dialog. - Log the result (Deleted / Skipped) into a `Status` column in Sheets.4. Run the agent in “dry run” mode first, watching every step (Simular’s transparent execution lets you inspect and tweak actions).**Pros**- Mimics a real user across browser and Sheets.- No need for APIs or custom integrations.- Transparent logs: every click and delete is inspectable.**Cons**- Requires careful onboarding and clear instructions.- You still need governance around which records the agent is allowed to touch.#### 3.2 Agent as a production job with webhooksOnce you trust the workflow, move it into your production rhythm.1. Use a webhook or scheduler in your existing pipeline (or a cron job) to trigger the Simular agent nightly.2. The agent: - Opens the latest **Google Sheets** view of deals marked for deletion. - Cleans Salesforce using the same steps. - Writes a summary sheet: number deleted, skipped, or failed.3. Your RevOps team reviews the summary on Monday instead of spending hours of manual cleanup.**Pros**- Production-grade reliability across thousands of steps.- Perfect for agencies managing many client orgs or fast-scaling sales teams.**Cons**- Requires initial setup time.- You should still keep safeguards (e.g., only delete if Stage = Closed Lost and older than X days).#### 3.3 Agent as safety-first assistantYou can also flip the script: instead of auto-deleting, the agent prepares everything and lets a human click once.1. The agent compiles a new Google Sheet from Salesforce listing suggested deletions (based on rules you define).2. Sales leaders review and approve.3. A second agent run performs the actual deletes only on `Approved = TRUE` rows.This gives you:- AI speed for discovery and preparation.- Human judgment at final decision points.By starting with the manual methods, layering no-code tools, and then handing the keystrokes to an AI computer agent, you turn “how to delete an opportunity in Salesforce” from a chore into a controlled, scalable workflow that your team barely has to think about.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
When you delete an opportunity in Salesforce, you’re not just removing a single row; you’re potentially wiping out a cluster of related records. By default, Salesforce deletes many child records that hang off the opportunity, such as tasks, events, quotes, quote line items, quote PDFs, competitor strengths and weaknesses, contact roles, and stage history. However, **Accounts and Contacts themselves are not deleted** when you delete an opportunity linked to them.The deleted opportunity and its deletable related records are moved into the **Recycle Bin**, where they can usually be restored for a limited period (subject to your org’s retention rules and storage limits). If you restore the opportunity from the Recycle Bin, Salesforce will restore many of those related records as well.Actionably, this means you should:- Review related data before deletion (especially quotes and tasks).- Use filters and reports to ensure you’re targeting the correct records.- Test bulk deletions in a sandbox before running them in production.
Whether a user can delete or restore opportunities in Salesforce depends on **profiles, permission sets, sharing rules, and role hierarchy**. To delete an opportunity, a user typically needs:- **Read** and **Delete** object permissions for Opportunity.- Access to that specific record via sharing (they must own it, be above the owner in the role hierarchy, or be granted access through sharing rules/teams).Restoring from the **Recycle Bin** usually requires that the user either deleted the record themselves or has admin-level permissions that allow viewing and restoring records deleted by others.Practically:- Standard reps often should **not** have bulk delete rights—reserve that for admins or RevOps.- Use a dedicated administrative profile or permission set for anyone who will manage cleanup.- When training an AI agent to perform deletions, run it under a **service user** with controlled permissions so that its access is auditable and intentionally scoped.Always review your org’s security model in **Setup → Profiles** and **Permission Sets** before enabling large-scale delete operations.
The safest way to bulk-delete old opportunities is to combine filters, exports, and a staged process that includes human review.1. **Define clear criteria.** For example: Stage = Closed Lost, Last Modified Date < 18 months ago, no open tasks.2. **Build a Salesforce report** or list view capturing only records that match those criteria. Include fields like Opportunity Name, Owner, Stage, Amount, Close Date, and Last Activity.3. **Export the list** to a CSV and load it into Google Sheets. Ask managers to review and mark which deals are safe to remove, adding a `Delete = TRUE/FALSE` column.4. Once approved, either: - Use **list view multi-select deletion** for manageable volumes, or - Use a **no-code tool or AI agent** to process the approved list.5. **Back up data** before large runs. That can be through Salesforce Data Export or a third-party backup.6. Start with a **small pilot batch** to verify nothing unexpected is being removed.By combining filters, exports, and approvals, you drastically reduce the chance of deleting live or strategically valuable deals.
Yes, Google Sheets is an excellent control center for managing delete lists before anything happens in Salesforce. Many teams prefer a spreadsheet because it’s familiar, shareable, and offers a clear audit trail.A practical workflow:1. **Export candidate opportunities** from Salesforce (via a report) into a CSV, then open it in Google Sheets; or use the official **Data Connector for Salesforce** add-on from Google Workspace Marketplace to sync data directly.2. Add decision columns such as `Delete?`, `Approved By`, `Reason`, `Keep Until`, etc.3. Share the sheet with sales managers and RevOps. Ask them to review and set `Delete? = TRUE` only when they’re confident.4. Use **filters** or a separate tab to isolate rows with `Delete? = TRUE`.5. From there, either: - Delete those opportunities manually in Salesforce using the IDs, or - Let a no-code integration or AI agent read the sheet and perform the deletes.This pattern keeps Salesforce clean while making approvals transparent and reversible (you can always adjust the sheet before the automation runs).
An AI agent is ideal when you’re repeatedly cleaning large volumes of opportunities and don’t want humans stuck in low-value clicking. Instead of building brittle integrations, an AI computer agent operates like a power user: it reads your Google Sheets approval list, logs into Salesforce, cross-checks each opportunity, clicks **Delete**, confirms dialogs, and logs the result.You should consider an AI agent when:- You regularly clean hundreds or thousands of stale deals.- You manage multiple Salesforce orgs (e.g., as an agency) and want a reusable workflow.- You value **transparent execution**—seeing every step and being able to pause, edit, or replay.Guardrails to put in place:- Run the agent under a **restricted service account** in Salesforce.- Start with a **small test sheet** and watch every action.- Always require approvals in Google Sheets (e.g., `Delete = TRUE` and manager sign-off) before the agent is allowed to touch records.Used this way, an AI agent doesn’t replace ops or sales leadership; it removes the drudgery so they can focus on better pipeline strategy and cleaner forecasting.