Skip to main content

Importing items

You can import items from previous versions of Talend Studio or from a different project of your current version.

The items you can possibly import are Business Models, Jobs, Routes, Services, Routines, Documentation, or Metadata.

Information noteNote:

From Talend 7.0 onward, a digital signature is added to each project item when it is saved in Talend Studio. When importing a project or project items, Talend Studio validates the signatures and rejects items with an invalid signature. This is a security measure to prevent accidental or malicious modification of project items.

However, you can import a project or project items exported from an earlier version of Talend Studio before the expiration date of a 90-day grace period from the first installation of Talend Studio or before the date set in the migration token, whichever comes later. Upon successful import, all imported items are signed.

For more information on setting a migration token, see .

Talend Studio allows any authorized user to import any project item from a local repository into the remote repository and share them with other users.

To import items, right-click any entry such as Job Designs, Routes, Services, or Business Models in the Repository tree view and select Import Items from the contextual menu or directly click the icon on the toolbar to open the Import items dialog box and then select an import option.

To import items stored in a local directory, do the following:

  1. Click the Select root directory option in the Import items dialog box.

  2. Click Browse to browse down to the relevant project folder within the workspace directory. It should correspond to the project name you picked up.

  3. If you only want to import very specific items such as some Job Designs, you can select the specific folder, such as Process where all the Job Designs for the project are stored. If you only have Business Models to import, select the specific folder: BusinessProcess, and click OK.

    But if your project gathers various types of items (Business Models, Jobs Designs, Routes, Services, Metadata, Routines...), we recommend you to select the project folder to import all items in one go, and click OK.

  4. If needed, select the overwrite existing items check box to overwrite existing items with those having the same names to be imported. This will refresh the Items List.
    Information noteNote: You cannot overwrite the existing items, if:
    • the item is identical but the path is different, or
    • the name is identical but the item is different.
  5. From the Items List which displays all valid items that can be imported, select the items that you want to import by selecting the corresponding check boxes.

  6. Click Finish to validate the import.

To import items from an archive file (including source files and scripts), do the following:

  1. Click the Select archive file option in the Import items dialog box.

  2. Browse to the desired archive file and click Open.

  3. If needed, select the overwrite existing items check box to overwrite existing items with those having the same names to be imported. This will refresh the Items List.

    Information noteNote: You cannot overwrite the existing items, if:
    • the item is identical but the path is different, or
    • the name is identical but the item is different.
  4. From the Items List which displays all valid items that can be imported, select the items that you want to import by selecting the corresponding check boxes.

  5. Click Finish to validate the import.

Information noteNote: If there are several versions of the same items, they are all imported into the Project you are running, unless you already have identical items.

You can now use and share your Jobs, Routes, Services, and all related items in your collaborative work. For more information about how to collaborate on a project, see Working collaboratively on project items.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!