Migration: Shared jobs

There are some additional factors to consider when migrating a Matillion ETL shared job to a Data Productivity Cloud shared pipeline. To correctly migrate shared jobs, use the process given below.

Before doing this, ensure that you fully understand the concepts and use of both shared jobs in Matillion ETL and shared pipelines in the Data Productivity Cloud.

Best practice for shared pipelines is to create them in their own dedicated project that is separate from the projects that consume them. These instructions assume you will be doing that.

---

Migration path

1. In Matillion ETL, unpack the shared jobs you want to export.

   Note

   If you have the original source of the shared jobs, you can skip this step and export the source instead.

2. Export the unpacked jobs, as described in the migration process.

3. In the Data Productivity Cloud, import the shared jobs, as described in the migration process. Ensure that you are importing into the project you are using to hold your shared pipelines.
4. Refactor, test, and amend these pipelines as needed to ensure they perform the expected function in the Data Productivity Cloud.
5. Share the pipelines, as described in Sharing a pipeline.
6. In Matillion ETL, export the jobs that use the shared jobs.
7. In the Data Productivity Cloud, import the exported jobs. These will become your consuming pipelines in the Data Productivity Cloud.
8. Create a mapping to resolve any issues in the import that require refactoring. Read Migration mappings to learn how to do this.
9. Refactor and test the imported pipeline to ensure it functions as expected and correctly calls the shared pipelines it needs.