> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform-products/apprules-data-migration-engine/the-migrate-data-activity/initializing-the-migrate-data-activity.md).
# Initializing the Migrate Data Activity
## Activity **Initialization**
To initialize the Migrate Data Activity, drag the MigrateData activity from the Migrate-Replicate-Synchronize module of the toolbox on to the designer and configure it as described in the following sections.
## Setting up the Migration Job Type
Select the Data Migration job type from the list.
{% hint style="info" %}
Based on your selection of a job type, appRules will display additional dialogs to be used for setting up the values for populating the "[Target Entities Collection" ](/apprules-r-documentation/platform-products/apprules-data-migration-engine/the-migrate-data-activity/target-entities-collection.md)which is discussed in the next section.
{% endhint %}
## Initializing From an Existing Activity
To initialize the Migrate Data Activity from an existing activity, follow the steps below:
1. Click the Copy button on the Migrate Data Activity modal to display the Copy modal.
2. Select the project database and activity, then click the "Copy Properties" button.
All properties of the selected Migrate Data Activity including the "[Target Entities Collection" ](/apprules-r-documentation/platform-products/apprules-data-migration-engine/the-migrate-data-activity/target-entities-collection.md)will be copied into the current activity.
## Editing a Saved Migrate Data Activity
Once you have initialized and saved the Migrate Data Activity, you can edit it by clicking its Configure icon on the designer. The "Edit Activity" modal will be displayed:
---
# 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.appstrategy.com/apprules-r-documentation/platform-products/apprules-data-migration-engine/the-migrate-data-activity/initializing-the-migrate-data-activity.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.
