> 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/adding-objects-to-a-template.md).
# Adding Objects to a Template
##  Overview
This article explains how to add a related object to your root object in the Template designer. Objects are related to each other in a parent-child relationship. Review the section on object connections in the following article to learn more about the object relationships.
* [Overview of Templates](/data-migrator/templates/template-designer/overview-of-templates.md#object-connections)
After adding objects to a template, see the following article to learn how to add fields to objects.
* [Adding Fields to Objects](/data-migrator/templates/template-designer/adding-fields-to-objects.md)
{% hint style="info" %}
Objects can be added to any object, not just the root, allowing for customizable templates to meet specific migration requirements.
{% endhint %}
{% hint style="warning" %}
#### Preserving Relationships
To preserve the link between parent and child records during migration, migrated child records must include the **Relationship Field** that connects them to their parent. This applies to both Master-Detail and Lookup relationships. To learn more about this, see the following article.
* [Preserving Object Relationships](/data-migrator/templates/template-designer/preserving-object-relationships.md)
{% endhint %}
## Add Child and Parent Objects
{% hint style="info" %}
#### Adjusting Template Canvas
To ensure the items you are working with fit on your display, you may need to adjust the canvas view. Here's how you can manipulate the canvas:
* **Zoom In and Out**: Adjust your view by using the mouse scroll wheel or by pinching in or out on your trackpad to change the zoom level.
* **Pan Across the Canvas**: Click and hold the canvas, then drag in any direction to move your view around and explore different areas.
Experiment with these tools to optimize your workspace and view all necessary items comfortably.
{% endhint %}
{% stepper %}
{% step %}
### Select Template
1. Click **Templates** from the left sidebar menu.
2. Click the template to add objects to.
{% endstep %}
{% step %}
### Add Child Objects
1. Hover the cursor over the object to add a child object to.
2. Click the **+** icon below the object to display the child object selector.
3. Search or scroll to find the child object to add.
4. Click the object to add.
5. Once added, the child object will appear on the canvas with a line connecting the parent object's bottom to the child object's left side.
6. Repeat this process to add as many child objects as you need.
{% endstep %}
{% step %}
### Add Parent Objects
1. Hover the cursor over the object to add a parent object to.
2. Click the **+** icon above the object to display the parent object selector.
3. Search or scroll to find the parent object to add.
4. Click the object to add.
5. Once added, the parent object will appear on the canvas with a line connecting the child object's right side to the parent object's top.
6. Repeat this process to add as many parent objects as you need.
{% endstep %}
{% step %}
### Save Changes
Once you are done adding objects to the template:
1. Click **Save template** to save your changes.
{% 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/adding-objects-to-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.
