--- title: "Run project" slug: "run-project" description: "Run projects efficiently with batch processing, delta runs, and data synchronization for integration, migration, and master data management tasks." tags: ["Task topic"] status: "update" updated: 2026-10-05T12:05:58Z published: 2026-10-05T12:05:58Z canonical: "docs.staedean.com/run-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 project You can use a project to exchange 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. Depending on the tasks that are set up for the project, you can use a project to run: - An integration or data migration. - Outbound web services. - Batch classes. - Master data management. - Test cases. 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. Sometimes, you want to import only the delta: 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 (see picture). In Connectivity Studio, you can do a delta run. To do a delta run: As a result, if the project is run, for each project task, only the messages that have the **Run for delta** field set to **Run** are run. When a message is run in a delta run, only records are inserted. No records are updated or deleted. Select **Yes** in the **Delta run** field. > [!NOTE] > **Note** > > For outbound web service actions, you can set up data synchronization of type '**Date range**'. To apply this setup when you run web service actions from a project, select **Yes** in the **Delta run** field. 1. For the project tasks, add the applicable messages with the **Run for delta** field set to **Run**. 2. Set the current **Delta run** field to **Yes**. 6. You can set up data synchronization for messages and web service actions. If data synchronization is active, the project run must process the outbound queue. Therefore, the applicable messages or web service actions are not run directly, but only from the outbound queue. When the project is run, the outbound queue is only processed for the messages or web service actions that are linked to the project tasks. Select **Yes** in the **Process outbound queue** field. 7. 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 a recurrence schedule for the project. Click **Recurrence** and fill in the fields as desired. 4. Click **OK**. 8. Click **OK**. > [!NOTE] > **Note** > > You can also run a project from the project form.