> For the complete documentation index, see [llms.txt](https://learn.capstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.capstorm.com/copystorm-restore/common-tasks/populating-a-developer-sandbox-with-production-data.md).

# Populating a Developer Sandbox With Production Data

CopyStorm/Restore makes populating a Developer Sandbox with production data a painless operation. This article provides a guide for how to do this for your operation.

## Prerequisites

* A CopyStorm backup of your production Salesforce data.
* A Salesforce developer Sandbox.

## Step 1: Determine What Type of Records Should Drive the Restore

This step will determine the type and volume of data that will be restored to the Sandbox. This step is both important and non-optional due to fairly severe size restrictions on Developer Sandboxes. It is highly unlikely that you will be able to import your entire production data set.

The choice of what types of records to restore depends on what you plan to do with the Sandbox. Records are often selected based on criteria like:

* Choose 500 random Accounts.
* Choose 100 Contacts that have open Cases.
* Choose the top 100 Opportunities in the current quarter.
* Choose all Accounts from the list of Ids in the file ABC.txt.
* Choose all Contacts from a list of Ids pasted into CopyStorm/Restore.
* Choose 100 Accounts that have at least one record in my custom object.
* Choose 250 random My\_Custom\_Object\_\_c records.

To learn more about selecting records see the reference manual selection on [Record Selectors](/copystorm-restore/reference/restore-set-editor-tab/records-to-restore-editor.md).

## Step 2: Watch This Video Tutorial

In this video we will select 100 random Accounts along with any related Contacts and Opportunities. The data will be restored to an empty Salesforce Developer Sandbox.

{% embed url="<https://www.youtube.com/watch?v=O0ZtL65LYHo>" %}


---

# 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://learn.capstorm.com/copystorm-restore/common-tasks/populating-a-developer-sandbox-with-production-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.