> 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/overview-of-system-templates.md).
# Overview of System Templates
##  Overview
System Templates are predefined, read-only templates created by Flosum for common migration designs and use cases. Because they cannot be edited, the underlying logic remains consistent. You can use System Templates to migrate data by running a migration using the same process as with a user-created template.
The available System Templates are listed in the sections below, along with a brief explanation of the data they migrate.
## Available System Templates
### Filter for System Templates
1. Click **Templates** from the left sidebar menu.
2. Click the **System** filter.
3. Only System Templates will be shown in the Templates table.
### Revenue Cloud: Product Catalog Management
The **Revenue Cloud** template is built from the Salesforce Product Catalog Management Data Model. See the following link for Salesforce's documentation on this data model.
*
### Salesforce CPQ: Product & Bundle Model
The **Salesforce CPQ** template is built using objects from the `SBQQ__` namespace. The **ROOT** object is `Product2`, and all available CPQ objects are included.
---
# 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/overview-of-system-templates.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.
