> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/data-migrator/templates/template-designer/creating-a-template.md).
# Creating a Template
##  Overview
This article explains how to create a template in Data Migrator using the Template designer. After creating a template, you can add objects by following the instructions in the article below.
* [Adding Objects to a Template](/data-migrator/templates/template-designer/adding-objects-to-a-template.md)
{% hint style="info" %}
#### Root Object
The **Root** object represents the Salesforce object that you want to start your template from. You can reference the [Salesforce Developers Portal](https://developer.salesforce.com/docs/platform/data-models/guide/get-started.html) to see which objects are considered root objects. For example, the **Account** object is a root object in [Salesforce Sales Cloud](https://developer.salesforce.com/docs/platform/data-models/guide/sales-cloud-overview.html), whereas the **Case** object is considered the root object in [Salesforce Service Cloud](https://developer.salesforce.com/docs/platform/data-models/guide/service-cloud-overview.html).
{% endhint %}
## Create Template
{% stepper %}
{% step %}
### Create Template and Select Organization
1. Click **Templates** from the left sidebar menu.
2. Click **Create Template**.
3. Click the **Select organization** dropdown menu.
4. Select the organization to build the template for.
5. Click **Continue**.
{% endstep %}
{% step %}
### Select Root Object
{% hint style="info" %}
#### What is the Root Object
The root object represents the top object in Salesforce that you want to start your template from. You can reference the [Salesforce Developers Portal](https://developer.salesforce.com/docs/platform/data-models/guide/get-started.html) to see which objects are considered root objects. For example, the Account object is a root object in [Salesforce Sales Cloud](https://developer.salesforce.com/docs/platform/data-models/guide/sales-cloud-overview.html), whereas the Case object is considered the root object in [Salesforce Service Cloud](https://developer.salesforce.com/docs/platform/data-models/guide/service-cloud-overview.html).
{% endhint %}
{% hint style="info" %}
These instructions use the **Account** object as the root, for example.
{% endhint %}
1. Click the **Choose root object** dropdown menu.
2. Enter the name of the object in the search box to help find it.
3. Click the object you want to use as your root object.
4. Click **Continue** to proceed to the next step.
{% endstep %}
{% step %}
### Name and Save Template
Once the root object is added, you can name the template.
1. Click the **Template name...** above the template canvas.
2. Enter a descriptive name for the template.
3. Click **Save template** to save your changes.
{% endstep %}
{% step %}
### Add Related Objects
Once the template is created and your root object chosen, you can add objects to the template. See the following article for instructions on adding objects.
* [Adding Objects to a Template](/data-migrator/templates/template-designer/adding-objects-to-a-template.md)
{% endstep %}
{% endstepper %}
---
# 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://docs.flosum.com/data-migrator/templates/template-designer/creating-a-template.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.
