Migrating on-premises Talend implementations to the cloud: What do you need to start?

Imagine that you are an on-premises Talend customer, and your company has decided to move all of its operations to the cloud. They have licensed Talend Cloud and have tasked you with migrating your existing Talend projects and Jobs to this new product.

What do you need to know to begin your migration to Talend Cloud?

Talend Cloud Migration Readiness

The key to a successful Talend Cloud migration is assessment and planning.  We’ll suggest some items that may hinder success for a self-service migration.  We recommend you take the time to understand your existing installation, and then create a plan for this project.


Check your on-premise Talend installation for the following items: 

  • Is your on-premises Talend version older than 6.4?
  • Do you have Big Data Jobs that must be migrated to the cloud?
  • Do you deploy realtime Jobs?
  • Do you use more than one TAC?
  • Do you require or use Talend CI/CD?
  • Do you use more than 2 or 3 Talend projects?
  • Do your projects contain more than 100 Jobs?

These may make your migration project a bit more challenging than a self-service exercise.  In these cases, it is recommended you bring in help such as Talend Professional Services.


The Talend Audit Report will help make you more knowledgeable about your current Talend projects and the Jobs within them.  This report will analyze your Jobs and produce some very useful information.  The Audit Report will give you a rating of complexity for each Job, plus a list of items (such as context variables) that may require modification before moving to Talend Cloud. 

Note: for Talend pre-7.0 releases it’s found in the Command Line utility; for Talend 7 and later it’s part of Studio.


Now that you have a good understanding of your on-premise Talend installation, projects, and Jobs it’s time to create a plan that will cover tasks and resources for the migration project.  When putting your plan together, take into consideration the following:

  1. Allow more time to migrate complex Jobs (see the audit report)
  2. Can any obsolete Jobs be removed?
  3. Are you using Subversion for your on-premise Talend source control? If so, you will need to add a Subversion to Git migration step in your plan
  4. How many Talend Job Servers do you currently use?
  5. Do you plan to use Compute Engines to run your Jobs?
  6. Be sure your migration plan includes a backout strategy in case things don’t work out


Activate your Talend Cloud license and designate one of your technical staff to act as the Talend Cloud Security Administrator for your account.  This person should be the technical leader of the migration project and will be responsible for management and provisioning of your Talend Cloud implementation.


Be sure you get from  Talend (and nowhere else), all the new software you’ll need.  This includes:

  1. You want the latest and greatest version of Talend Studio.  Don’t use your on-premises copy, even if it is the same release as the Talend Cloud version
  2. Remote Engine. If you elect to deploy your Jobs on Remote Engines, download the Remote Engine installer for the operating system of your choice.

Complex use cases

As previously noted, If your on-premise Talend implementation requires complex use cases such as CI/CD, Big Data, or real-time, you ought to consider getting help from Talend Professional Services.  This also goes for on-premises Talend projects that contain more than a hundred Jobs.

A step-by-step Talend Cloud migration plan

For the full step-by-step migration plan to get you fully up and running with Talend Cloud, including checkpoints and support resources, please download the full self-service Talend Cloud migration guide.


Join The Conversation


Leave a Reply