While the goal and purpose of archiving is to remove records and free up space in your org, there are times where those records need to be restored; this doc will walk you through the steps to restore archived files to an org.

Let's start with selecting our policy with the records we need. In my case, I'm looking to restore some records on the Contact object, so I'll navigate to the run with those records.

Once we click View latest policy run, we'll be able to choose which records we'd like to include. I'll select the 20 Contact records to restore.

There's an additional option to apply field filters to the results, if needed.
​

When you've completed your selections, click Restore records in the bottom right to proceed and choose a restoration method.

We offer two restoration methods to choose from when restoring records:

This method is best used if you need to restore records for an object, along with records on its dependent objects.

A common example of this would be to restore a deleted Account record. The cascading nature of the Salesforce's deletion logic means that all the Opportunities on the Account and the OpportunityLineItems (listed as Products on the Opportunity) will also be deleted. This will pick up and restore those objects in a single restoration retaining all the lookups and references between the records.

This is generally the most common restoration type that suits most use cases. Read more about this method of restoration here.

This method is best used when restoring multiple objects that are associated.

It works similarly to the sandbox seeding tool and allows many configurations.

It has less guidance than the other methods, and we would generally only recommend this for users with a good knowledge of their org's data model.

An example could be a mass data recovery where multiple objects have been corrupted or deleted or otherwise changed. Read more about this method of restoration here.

For the purpose of this guide, we'll go through the recommended method and restore records with dependent objects.

After selecting the restoration method, we'll be able to confirm and view those selections, and add any related records the we detect (in this case, there are some Case records associated with the Contact object via the ContactID field).

We'll proceed with the Contact records we initially chose and click Continue.

If the restoration encounters any errors, you'll be able to choose whether to:

And lastly, you'll be prompted to disable validation and duplicate rules, triggers, and flows.

This step is optional, but highly recommended to ensure a successful deployment. More information on this step can be found in this doc.

Once those components have been disabled, we'll be able to deploy the data back to the org.