Job Export and Import

Jobs are not versioned objects. Control Hub retains the job ID with each export and import, but does not have to handle job version numbers.

You can export and import jobs and job templates. You cannot export and import a job instance created from a job template.

When you import a job or job template, you select the job properties that you want to import. The imported job uses the default values for any properties that you clear. For the initial import of a job, you'll most likely want to import all properties. You can then update the job properties in the target organization after the import. For example, you might want to use different job labels or different runtime parameters in the target organization.
Note: If you clear the Pipeline property for the initial import of a job, Control Hub still imports the dependent pipeline. If the pipeline includes fragments, the fragments are also imported with the pipeline. Jobs must include a pipeline.

For subsequent imports of a job or job template that already exists in the target organization, you'll want to clear the properties that have been modified in the target organization. Any properties that you import overwrite the configured job properties in the target organization. For example, if you modified the job labels and runtime parameters in the target organization, you would choose not to import those properties when you import the job.

When you export and import a job or job template, Control Hub also exports and imports the pipeline version included in the job, and any fragment versions used by the pipeline. Control Hub uses the same rules to import dependent pipelines and fragments as it uses when you individually import pipelines and fragments.

When you export and import a job template, Control Hub does not export and import job instances created from that template. After importing a job template, you create new job instances from that template.

Tip: Pipelines typically include more changes during the development process than jobs. After you initially import a job into the target organization, you might want to import the updated pipeline rather than importing the job again. The imported job in the target organization will indicate that a newer pipeline version exists, which you can easily update.