Exporting and importing replication projects
You can export a data replication project to a file that contains everything required to reconstruct the data replication project. The export file can be imported to the same tenant, or to another tenant. You can use this, for example, to move data projects from one tenant to another, or to make backup copies of data projects. You can also update a data project from an updated export file.
The export file format has been changed from a single JSON file to a ZIP file containing several JSON files. The old JSON format will be supported for import until January 30, 2026. To convert your JSON files to the new format you can import them, and then export them to the new ZIP format. Projects in the old JSON format cannot be imported via the API.
Users are advised to export their existing projects to enjoy the new format by January 30, 2026.
Exporting a data project
To export a project, do one of the following:
-
In Data Integration > Projects, click
on the project to export, and select Export. -
Open the project, click
in the top right, and select Export.
The project is exported to a ZIP file with a file name that consists of the project name, the data platform, and a timestamp.
Importing a replication project
You can import an exported replication project to the same tenant it was exported from, or to another tenant. When the replication project is imported to a different tenant, you need to define new connections for all data sources and targets.
To import a project:
-
In Data Integration > Projects, click Create new and select Import project.
-
Add the export file. You can either drop it on the dialog, or browse to select the file.
Click Next.
-
Set Project properties for the new project.
You must select which space to add the project to in Space.
Click Next.
-
Set Connections and task settings.
You can replace the imported source and target connections. This is required if you imported a project from another tenant.
In Optional task settings you can change task settings that were overridden in the original version.
-
When you are ready, click Import.
The project is added to Data Integration home.
Updating an existing project
You can update a project from an export file. This will replace all tasks in the project, but connections and task settings will not be replaced. Tasks that are not included in the imported project will be removed.
For example, you can import a project exported from the development data space into a project in the production data space to update the production project.
Before you start updating the project:
-
To backup the project before you update, export it by clicking
, and then Export. -
Stop any tasks that will be removed from the project.
-
If the project uses SaaS application connections that do not exist yet, you must create the connections and generate metadata before you start the import.
To update a project:
-
Open the project that you want to update.
-
Click
, and then click Import. -
Select or drop the file that you want to import.
-
Make any required changes for mapping connections that are different between the project and the imported project.
For example, the imported project could be using a source connection named SQL1, while the existing project uses a similar connection named SQL2. In this case, map the imported connection to SQL2 in Set connections for the tasks added in the original version.
Information noteWhen selecting a connection to map, you can create a new database connection, but not a SaaS application connection. -
Click Import when you are ready.
The project is now updated according to the imported file.
Limitations
-
Notifications are not included when you export a pipeline. You need to set up new notifications in the imported pipeline.