> 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/samples/sample-projects/data-migration-replication-and-synchronization/batch-data-source-entities-to-files.md).

# Batch Data Source Entities to Files

appRules features an unmatched number of options for migrating, replicating and synchronizing data.&#x20;

## Product & Hosting Options

#### Platform Product Availability

The workflow activities and other modules used in this sample project are available in the following appRules Platform products:

<table><thead><tr><th width="374"> Platform Product</th><th>Availability</th></tr></thead><tbody><tr><td>appRules Data Migration Engine</td><td><img src="/files/TwIa4jfSXn8d5sec2iaY" alt=""></td></tr><tr><td>appRules Integration &#x26; Automation Engine</td><td><img src="/files/AFvJKfivo35tTxWYPgpk" alt=""></td></tr><tr><td>appRules Enterprise 360</td><td><img src="/files/AXm2ll6g1iwIsktMavZe" alt=""></td></tr></tbody></table>

#### Hosting & Execution Environment&#x20;

If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:

| Hosting Option        | Recommended for Project          |
| --------------------- | -------------------------------- |
| IIS                   | ![](/files/QOSHR42DEO5gm0OHJjJU) |
| appRules Host Service | ![](/files/xfdDoP4i5rjcaob3rXOC) |
| appRules Desktop      | ![](/files/WtLyqszZWsM6wJjE3zKg) |

{% hint style="info" %}
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project.  Just point your browser to the appRules URL
{% endhint %}

&#x20;

{% hint style="info" %}
The completed project is available in the appRules **Samples** project database. Click the "Open" toolbar button on the appRules home page to select the "Batch Data Source Entities to Files" project.
{% endhint %}

The '"Batch Data Source Entities to Files" sample project demonstrates how to use the appRules MigrateData activity to perform batch migration of entities in a data source to files in a folder.

In the sample project, a single workflow activity is configured to load tables from a SQL Database into CSV files in a folder.

**Drag the MigrateData activity from the Migrate-Replicate-Synchronize module of the toolbox on to the designer and configure it as follows:**

Select **Source Database** as the default source, and  **Export to Files** as the data migration type.

<figure><img src="/files/0JVCrwR5uy7ChZWlKXdt" alt=""><figcaption></figcaption></figure>

Select the tables to be exported:&#x20;

<figure><img src="/files/SrGVaE8er4pUKGY4h7VY" alt=""><figcaption></figcaption></figure>

All properties required for the Target Entities collection will be automatically set for the process.  You can make any required changes to suit your needs.

<figure><img src="/files/AEuv2V7c1UmcVl1rCgrY" alt=""><figcaption></figcaption></figure>

Run the project and the files will be created in the Output folder:

...DbFiles\Samples\DataMigration\Output\Source Database-Files


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.appstrategy.com/apprules-r-documentation/samples/sample-projects/data-migration-replication-and-synchronization/batch-data-source-entities-to-files.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.
