---
title: "Run data migration project"
slug: "run-data-migration-project"
description: "Run projects efficiently with batch processing, delta runs, and data synchronization for seamless data migration and integration tasks."
tags: ["Task topic"]
updated: 2026-09-01T12:36:46Z
published: 2026-09-01T12:36:46Z
canonical: "docs.staedean.com/run-data-migration-project"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run data migration project

You can use a project to migrate data. To be able to run a project, tasks must be set up for the project. If you run the project, all related tasks are run.

Usually, you run a project in batch. Based on the defined sub-projects and tasks dependencies, tasks are run in parallel. If you do not run the project in batch, all sub-projects and tasks are run sequentially.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. Click **Run project**.
3. In the **Project** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> By default, the currently active project, as shown on the **Connectivity studio - Integration design** workspace, is selected.
4. By default, if you run a project, it runs in the current company only. You can use a company group to run a project in several companies.

In the **Company group** field, enter or select a value.
5. For data migration, you usually want to import only the delta, which are the changes since the last import.

**Example**: During a migration project, often, some time elapses between the migration of the data and the go-live moment. Therefore, just before the go-live moment, you want to import the latest open transactions. However, you do not want to run the full migration again.

In Connectivity Studio, you can do a delta run. To do a delta run:
  - For the project tasks, add the applicable messages with the **Run for delta** field set to **Run**.
  - Set the current **Delta run** field to **Yes**.

As a result, if the project is run, for each project task, only the messages are run that have the **Run for delta** field set to **Run**. When a message is run in a delta run, only the record inserts are done. So, no update or delete of records is done.

Select **Yes** in the **Delta run** field.

> [!NOTE]
> **Note**
> 
> If you run a data migration project with ODBC and doing a delta run, you must use a data synchronization of type **Date range**. Set up the data synchronization on the applicable messages. See also: [Set up data synchronization - Date range - Message](/data-management/docs/set-up-data-synchronization-date-range-message)
6. Sub-task: Set up batch processing.
  1. Expand the **Run in the background** section.
  2. By default, a project is run in batch.

In the **Batch processing** field, select an option. If **Yes**, also fill in the other fields.
  3. If desired, you can set up the recurrence for the project.

Click **Recurrence** and fill in the fields as desired.
  4. Click **OK**.
7. Click **OK**.

> [!NOTE]
> **Notes**
> 
> You can also run a project from the project form.

## Related

- [Improve data migration performance](/improve-data-migration-performance.md)
- [Migrate product masters and product variants](/migrate-product-masters-and-product-variants.md)