You are here:
Import Data from a Local Drive in the Archive App
Import offloaded Salesforce data stored in local CSV files to the Archive app staging area. Then manage the final data migration and set specific retention periods for your records by configuring an Archive import policy.
Before importing, make sure that your data files meet these requirements:
- Data Validation
- Each CSV file header includes at least 80% of the fields defined for that object in your current schema.
- File Format
- Make sure that each file is in CSV format.
- Each file contains records for only one Salesforce object type, such as Case.csv.
- The file name exactly matches the object's API name.
- File Headers
- The first row is a header row.
- Headers contain the exact API names of the fields for that object, such as FirstName.
When your files are configured, upload your source data to the staging area.
- From the Archive home page, select the Import icon.
- Select a CSV file to upload, or drop it directly on the page.
- Click Import.
- When the process completes, click Done.
Create an Import Policy in the Archive App
After your offloaded data has been loaded successfully into the Archive app staging area, create and run a special import policy to move your staged data permanently into your archive.
Import policies are only available after data is loaded successfully into the staging area. Verify that the Import-data-load activity has completed successfully before proceeding with a new one.
- Go to the Policies tab.
- Select New.
- Select Archive from Imported Data.
-
Configure your import policy settings.
Important
To archive 1–2 million records daily, archive the entire object tree as a single process. In your Import Policy, select Archive All Related Records as the related object selection method. This option reduces processing overhead and optimizes S3 file creation.
Key Characteristics of an Import Policy
- The scheduler is turned off. Use the Run Now option.
- The policy automatically processes all staged records for the selected root object. Filters aren't available.
- The policy processes data from the staging area, not your live org, so there's no performance impact.
Relationship Archiving Settings
-
Setting Description Archive All Related Records This option automatically archives all child records connected to the root record via a lookup relationship. Don't Archive Related Records This option performs a targeted archive. The targeted archive includes only the primary records that match your query and their directly dependent child records in a cascade-delete relationship. All other related records, such as those in standard lookup relationships like Contacts on an Account, are excluded from Archive. Manually Select Relationships This option provides control to select exactly which direct child relationships are included during archiving. After selecting this option, a list of available child relationships appears, and you select the specific objects to be archived along with the root object.
Run and Monitor the Import Policy
- To start the final archiving process, click Run Now on the import policy.
-
Track the status in the Activities tab.
The process is logged with the action type Import-data-archive.
The system is required to complete the full Import-data-load and Import-data-archive cycle for the current dataset before a new import can begin. When the Import-data-archive activity is complete, your data is stored securely, and you can start a new import cycle.
Retention Policy
Select the criteria from these sources.
- Archived Date
- Created Date
- Last Modified Date
Select the amount of time that you want to retain the archived data. The minimum retention period is one month, and the maximum is 99 years and 11 months.
Creating a retention period of zero years and zero months means data is purged automatically within 24 hours.

