Exporting and importing replication projects

You can export a data replication project to a JSON file that contains everything required to reconstruct the data replication project. The exported JSON 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 JSON export file.

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 JSON file with a file name that consists of the project name, the project type (Replication), 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:

1. In Data Integration > Projects, click in the top right, and select Import project.

2. Add the project JSON file. You can either drop it on the dialog, or browse to select the file.

   The following fields are displayed:

   • Name

     Optionally, change the name of the project. The default name is the original project name, prefixed with Imported_.

   • Space
     Select which space to add the project to.

   • Description
     Optionally, add a description for the project or edit the existing description.

   • Replace imported source connections
     You can replace the imported source connections.

     This is required if you are importing a project from another tenant.

   • Replace imported target connections

     You can replace the imported target connections.

     This is required if you are importing a project from another tenant.

   • Replace imported source schemas

     This section displays the source schemas for each of the tasks pending import. You can replace the imported source schemas.

3. When you are ready, click Import.

The project is added to Data Integration home.

Updating an existing project

You can update a project from a JSON 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:

1. Open the project that you want to update.

2. Click , and then click Import.

3. Select or drop the JSON file that you want to import.

4. 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 Replace imported source connections.

   Information noteWhen selecting a connection to map, you can create a new database connection, but not a SaaS application connection.

5. Click Import when you are ready.

The project is now updated according to the imported JSON file.