> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/single-dataloader/delete-salesforce-data.md).

# Delete Salesforce Data

The following articles describe using **Single DataLoader** to delete data from Salesforce. To delete data, you need a CSV file containing the IDs of the objects to delete. Follow the steps below:

1. Log in to your ARM account.
2. Hover your mouse over the **`DataLoader`** module and choose the **`DataLoader`** option.
3. Click **`Delete`** on the right side of the screen.

<figure><img src="/files/xsPDoU6edOnBQHGn6HoE" alt="Delete option on Dataloader page"><figcaption></figcaption></figure>

4. Choose your [**`Salesforce Org`**](broken://pages/9pLgfInGvztETx4cXCc2) and select your org environment (**`Production or Development Edition`**, **`Sandbox`**, or **`Pre-Release`**).
5. The corresponding **`URL`** and **`Username`** are auto-generated based on the selection.
6. Click **`Login and Fetch Objects`** to load all objects from your Salesforce Org.

<figure><img src="/files/e9SYBW2ph4csoW5zTlIk" alt="Login and Fetch Objects screen"><figcaption></figcaption></figure>

7. Select the object (e.g., **`Account`**, **`Contact`**, **`Lead`**). Use **`search`** and **`filter`** options to find standard/custom objects.
8. Click **`Next`**.

<figure><img src="/files/72rXlzxg5KlzVV43yUYh" alt="Object selection screen in Dataloader"><figcaption></figcaption></figure>

9. Upload your **CSV** file by clicking **`Upload`**.

<figure><img src="/files/iSkDhSmzdSfXBg446Ejl" alt="CSV upload screen"><figcaption></figcaption></figure>

10. Confirm the number of impacted records in the popup. Click **`OK`**.

<figure><img src="/files/bU10yhtUKMMrymbtRcD3" alt="Notification showing impacted records"><figcaption></figcaption></figure>

11. Prepare field mappings to match your CSV fields with Salesforce fields.
12. Use **`Automap`** to auto-match fields by name.

<figure><img src="/files/7eM6BU4XDTomsNCZkzfl" alt="Automap field mapping UI"><figcaption></figcaption></figure>

13. View the number of mapped vs. total fields below the Automap checkbox.
14. Use **`search`** to locate fields and **`Filter`** to narrow down:
    * **All** – Displays all fields.
    * **Mapped** – Only mapped fields.
    * **Unmapped** – Only unmapped fields.
15. Ensure all required fields are mapped, then click **`Next`**.
16. On the **`Process Summary`** screen:

<figure><img src="/files/zH8Oht7sDSwph5NWUrqG" alt="Dataloader Process Summary screen"><figcaption></figcaption></figure>

* Name the process/job.
* Select or create a **Category**.
* Review the Object, Type (**Delete**), and impacted Records.

17. Schedule tasks as **Daily**, **Weekly**, or **On-demand**.
18. Click **`Save`** to save and run later.
19. Your job appears at the top in the **`DataLoader Summary`** screen.
20. Click **`Run`** to execute the job manually.

<figure><img src="/files/6LHwYCqWDOrH0Z0nMO9s" alt="Run button in Dataloader Summary"><figcaption></figcaption></figure>

21. Choose criteria for running the DataLoader job:

| Configurations | Descriptions                                                                     |
| -------------- | -------------------------------------------------------------------------------- |
| **Batch Size** | Used when Bulk API is not selected. Ideal for small-volume real-time processing. |
| **Use UTF-8**  | Use UTF-8 encoding unless data contains non-English alphabets.                   |

22. Click **`Run`**.

<figure><img src="/files/27BrvMqVwdqge57cesOW" alt="Run confirmation screen" width="563"><figcaption></figcaption></figure>

23. The **`Results of Last Run`** section shows live updates of successful and failed record deletions. You can view/download records in CSV format.

<figure><img src="/files/mOJ66ArCM7Xp5bECGJI2" alt="Run results summary showing deleted records"><figcaption></figcaption></figure>

24. The number of impacted records is updated dynamically in the **Records** section.

***

### More Options <a href="#more-options" id="more-options"></a>

<figure><img src="/files/DFxwclVgnrCYvT4LMjAs" alt="More options menu"><figcaption></figcaption></figure>

1. **Edit** – Modify job details.
2. **Abort** – Stop a running process.
3. **Schedule** – Set job run schedule.
4. **Delete** – Delete the configured job.
5. **Log** – View execution logs.
6. **VR/WFR** – Review and re-enable validation/workflow rules. See [Validation/ Workflow Rules](/product-guides/arm/arm-features/dataloader/validation-workflow-rules.md).

<figure><img src="/files/ltIEjeKECIhaQY431Hqx" alt="Validation/Workflow Rules list UI"><figcaption></figcaption></figure>

<figure><img src="/files/SIy0majZbjwWzCqZ71vB" alt="Sample validation rule execution log"><figcaption></figcaption></figure>

7. **Clone** – Duplicate a process. You can upload a new CSV and select another Salesforce Org.

<figure><img src="/files/wuaOlf8l1b2IpPkFeH6o" alt="Cloning an existing dataloader process"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/single-dataloader/delete-salesforce-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.