# Introduction

**Problem Statement:**

In situations where users need to replicate a process from one company to another or one environment to the other, they are faced with the challenge of identifying and individually migrating the dependencies associated with a given form. These dependencies can encompass workflows, alarms, configured reports, templates, and more. Currently, the migration is achieved through Postman on a case-by-case basis.

**Solution Approach for Process Migration:**

1. **Select the Desired Form:** Initiate the migration process by choosing the form you wish to migrate.
2. **Identify Dependencies:** Use the GET metadata API to retrieve comprehensive information about the form's dependencies.
3. **Execute Migration:** Employ a single POST API call to migrate the data. This includes the main form, its dependent forms, workflows, alarms, reports, templates, and other associated components required to maintain the process's functionality.

<br>


---

# Agent Instructions: 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:

```
GET https://docs.senpiper.com/process-migration/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.