# Migrating Talend projects and artifacts

The migration of Talend projects and artifacts is implemented in a six steps wizard. You can automate the upgrade of a project designed in a non-compatible version of Talend Studio as well as the publication of artifacts to Talend Cloud.

To automate tasks such as a project upgrade or an artifacts deployment, you need to configure and run the installation of a Continuous Integration/Continuous Deployment (CI/CD) sandbox. Qlik Talend Cloud Migration Toolkit installs a local Talend 8.0 CI/CD sandbox environment with all the tools required to automate the upgrade, including the installation of Talend CommandLine 8.0 latest version.

After the successful project upgrade, you can use the newly upgraded Talend 8.0 project to automate the build of Job and Route artifacts using the local CI/CD sandbox environment. Those artifacts can be published to a Talend Cloud workspace and the associated Talend Management Console task is created and configured.

Information noteImportant: This feature should not replace the existing Software Development Life Cycle (SDLC) process and the usage of any current CI Server. It provides a fast and convenient way to review the project upgrades and test the build and execution of project artifacts in a Talend Cloud test environment before a full-fledged migration to Talend 8 on Talend Cloud.

Here is a list of key concepts:

| Key concepts | Details |
| --- | --- |
| Talend 8 CI/CD sandbox environments | A CI/CD sandbox is an environment dedicated to automating<br>CI/CD tasks.<br><br>Here are some properties to remember:<br><br><ul><li>It is called sandbox, because it's a local and isolated                                        replica of a CI/CD environment, but simplified for <span>Talend</span>.</li><li>It does exactly what <span>Talend Studio</span> can do in terms of migration, build, and                                        publication.</li><li>It does not use <span>Talend Studio</span> for these tasks; instead, it uses <span>Talend CommandLine</span>, which is <span>Talend Studio</span> without the graphic user interface.</li></ul><br><br>Qlik Talend Cloud Migration Toolkit automates the local installation of the required tools:<br><br><ul><li>Java JDK</li><li>Git client: Used to clone the Git repository.</li><li>Maven with additional plugins: Maven is a build automation                                        tool for Java projects. </li><li><span>Talend</span> 8 CommandLine</li></ul><br><br><br>Multiple environments can be installed based on the monthly<br>release of the Talend CommandLine. |
| CI/CD manifest | A manifest is a list of configurations that defines the CI/CD<br>implementation.<br><br>In Qlik Talend Cloud Migration Toolkit, you can configure manifests to:<br><br><ul><li>Upgrade your source project in a new version of <span>Talend Studio</span>.</li><li>Build selected Jobs and Routes and publish them to <span>Talend Cloud</span> or your artifact repository.</li><li>Generate reports.</li></ul><br><br><br>A CI/CD manifest is composed of four sections:<br><br><ul><li>The CI/CD environment version that will be used for the                                        CI/CD execution.</li><li>The source project: It can be a Git repository information                                        (URL and credentials) or a local workspace path where the                                            <span>Talend</span> project is located.</li><li>The targets for the CI/CD process: Currently, <span>Qlik Talend Cloud Migration Toolkit</span> supports several types of targets:<ul><li><span><span>Talend Cloud</span></span>: Target used to request the                                                publication of project asset artifacts and the                                                creation of the associated tasks. The target                                                configuration references the <span>Talend Cloud</span> Environment and Workspace names, where the                                                artifact will be published, the task name,                                                description templates and engine used by the                                                task.</li><li><span>Artifact Repository</span>: Target                                                used to request the publication of project asset                                                artifacts to an Artifact Repository (Nexus3, JFrog                                                Artifactory). The configuration contains all the                                                requested parameters: Repository type (Nexus3 or                                                Artifactory), URL, credentials and repository                                                name.</li><li><span>CVE Report</span>: Target used to                                                request the generation of a CVE (Common                                                Vulnerabilities and Exposures) report of the                                                  <span>Talend</span> project.</li><li><span>Project Upgrade Report</span>:                                                Target used for the generation of the <span>Talend</span> project upgrade reports based on the version of                                                  <span>Talend</span> 8 used by the current CI/CD environment. </li></ul></li><li>A list of assets to be processed: Once upgraded, the project                                        opens in a Web version of <span>Talend Studio</span>, where you can select the Jobs and Routes you want to                                        deploy.</li></ul> |
| CI/CD pipeline | A pipeline is the translation of a manifest into a series of<br>steps to be executed by the CI/CD sandbox.<br><br>Each step is<br>the execution of a CI/CD order:<br><br><ul><li><p>Git commands</p></li><li>Maven commands</li><li>Report generation (CVE and upgrade)</li></ul><br><br><br>Based on the requested targets and list of assets in the<br>manifests, Qlik Talend Cloud Migration Toolkit optimizes the number of steps in the pipeline as well as the<br>Maven command parameters used in the steps. |

### In this section

* [Installing the CI/CD environment](https://help.qlik.com/en-US/migration/installing-the-ci-cd-environment)
* [Creating a project upgrade manifest](https://help.qlik.com/en-US/migration/creating-project-upgrade-manifest)
* [Creating a CI/CD manifest](https://help.qlik.com/en-US/migration/creating-ci-cd-manifest)
* [Manifest list](https://help.qlik.com/en-US/migration/manifest-list)