> 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/dataloader-configuration.md).
# DataLoader Configuration
### DataLoader Configuration: Overview
“Dataloader Configuration” allows users to configure and define an External ID field that is used during data migration to prevent duplicate record creation. By mapping records based on a unique External ID, the system ensures that existing records are updated instead of creating duplicates.
Example:
\
If Account records are migrated from Sandbox to Production, and some records already exist in Production, configuring an External ID ensures that matching records are updated rather than duplicated. This maintains data integrity and consistency across environments.
This option is useful in the following scenarios:
* Preventing duplicate record creation during data migration.
* Synchronizing data between Salesforce orgs using a unique identifier.
* Performing Upsert operations safely.
* Maintaining data consistency across environments.
* Managing repeated data loads without creating redundant records.
***
### Creating a New DataLoader Configuration
1. Log in to your **ARM** account.
2. Navigate to the **DataLoader** module and select **DataLoader Configuration**.
3. Click on **New Configuration** to begin creating a data migration setup.
4. On the configuration screen:
* Enter a **Name** for the process.
* Choose the **Source Org** and **Destination Org**.
* Click **Login and Fetch Objects** to retrieve all source org objects.
5. Select the required **Objects** and their corresponding **Fields**. Use the **search filter** for quick lookup.
6. Click **Save** to store the configuration or **Save and Run** to execute the job immediately.
7. In the **Job Details** section:
* View the configured objects and field mappings.
* See success/failure status for each record.
* Use the **Search** icon to locate record IDs:
* Use the **Download** icon to export success/failure record logs:
***
#### More Options
1. **Edit:** Modify the configuration settings.
2. **Delete:** Remove the configuration.
3. **Clone:** Duplicate the configuration for reuse.
4. **Log:** Access detailed execution logs.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/dataloader-configuration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
