Click Job history on the data backup job from which you want to restore:
​

Choose the date of the org snapshot from which you'd like to restore.
​

Verify the state of the snapshot data before you restore from it. To do this, click the View details option.
​

Once you've confirmed the snapshot data is in a suitable state, click on the row for the snapshot you'd like to restore from to expand it out.
​

Then click on Use snapshot.
​

Click Restore snapshot data to restore to the same org, or click Replicate to deploy the data to another org:

If you opted to replicate the snapshot, then select the target org to which this data will be restored, and choose the date of the snapshot being used to restore from:
​

​

Click Replicate data.

You'll now run through a data deployment in Gearset's data loader, with the source of the deployment being the snapshot from the data backup job and the target being the org to which you're restoring.

The steps to follow are listed below, for more in-depth information about how the data loader works, see our support documents here.
​

In the column on the left side, select which objects you'd like to restore the records for by checking the box next to their name. You can search and filter for objects.

When a parent object is expanded, which you can do by clicking on it, Gearset checks for and lists any dependencies that can then be included within your data subset.
​
Gearset will then traverse the dependency graph to determine any further indirect dependencies necessary to deploy records from the selected objects.
​
For each object, you can enter optional filtering by field values to control exactly which records are restored. For example, if you want to restore a single specific record, you can filter by its Salesforce record ID as in the screenshot below:
​

Once you've chosen which objects you wish to restore, and have set any desired field-level filtering, click Next.
​

Choose how you want to match existing records, which related objects to include, and then customize their field mapping for upserting.
​
​Note: You can either create new record, Upsert records or Update existing records.
​

Choose whether you'd like the data deployment to continue if it hits an error deploying a record.
​
If you choose to continue deploying remaining records, the remaining deployment steps will continue to execute if a deployment step fails, ignoring the errors encountered and deploying as many of the records as possible.
​
Or, if you want the deployment to stop in the event of an execution step error, select the Stop deploying remaining records option:
​

Click NEXT to move to the pre-deployment summary.
​
Gearset will create and list out the steps we’re about to take in your data deployment.
​
You'll be able to see the object records to be deployed and the actions Gearset will take to retrieve them, such as fetching, including, creating, and upserting, as well as the field count and any applied filters:

Click on DEPLOY DATA to deploy the selected data to the target org.
​
When the deployment is running, each stage will mark as completed and show you how many records have been processed in each step:
​ 

Once it has completed, the deployment will be stored in your data deployment history in the app.
​
Learn more about data deployment history here.
​

Verify that the records have been restored to your org as expected.