Migrate Tasks

Last updated: 10/30/2026

The Migrate Tasks step creates Qlik Cloud reload tasks from the reload tasks and task chains in the plan. It replaces the Add Reload Schedules to Applications (legacy) step.

Prerequisite steps

• Import Applications

Step details

• Retrieval method:
  Tasks are selected from the Tasks tab of the plan. Qlik Cloud tasks are identified by the description tag that this step writes. For details, see Tasks.
• Chains and standalone tasks:
  Chains and standalone tasks are migrated alike.
  • Entry points of a chain get a time-based schedule.
  • Downstream tasks get an event-based schedule on their parent.
• Tasks without a trigger:
  A task with no trigger in Qlik Sense Client-Managed has no Qlik Cloud equivalent. It is created on a deliberately short schedule window that expires before it can fire. It never runs by itself, and stays runnable by hand.
• Tasks that already exist:
  The step setting for a task that already exists in Qlik Cloud is Skip, Update, or Create.
• Managed copies:
  By default, only the primary copy of an application is reloaded. Reloading every managed copy is a per-task option on the Tasks tab of the plan.

Notes

• Starting a migrated chain by API: use the scheduling endpoint POST /api/scheduling/tasks/{id}/actions/start with no body. Starting the reload of the application through /api/v1/reloads reloads the app, but does not fire the chain.
• Qlik Cloud allows at most ten reload tasks per application and thirty concurrent reloads per tenant. For details, see Product limitations.
• To undo this step, use Delete Tasks.

Related steps

• Import Applications
• Run Tasks
• Validate Tasks
• Delete Tasks
• Reset Task Descriptions