Skip to main content Skip to complementary content

Step order

In the Qlik Analytics Migration Tool, the order in which multiple Migration Steps execute within a job is based on a predefined priority. This priority reflects logical dependencies between operations. For example, spaces must be created before applications can be imported into those spaces, meaning Create Spaces will execute before Import Applications.

This sequencing ensures consistent execution across jobs, regardless of the order in which steps are selected.

Execution priority

The following list defines the full execution order of supported migration steps, from highest to lowest priority:

  1. Delete Users
  2. Delete Applications
  3. Delete QlikView Applications
  4. Delete Data Connections
  5. Delete NPrinting Reports
  6. Delete Spaces
  7. Export Users
  8. Import Users
  9. Export Extensions
  10. Import Extensions
  11. Export Themes
  12. Import Themes
  13. Create Spaces
  14. Add Assignments To Spaces
  15. Update Space Owners
  16. Migrate Data Connections
  17. Export Applications
  18. Import Applications
  19. Update App Object Owners
  20. Update Application Scripts
  21. Reload Applications
  22. Publish Applications
  23. Add Shares To Applications
  24. Migrate NPrinting Reports
  25. Migrate NPrinting Filters
  26. Add Reload Schedules To Applications
  27. Validate Applications
  28. Update Application Owners
  29. Convert QlikView Applications
  30. Import QlikView Applications
  31. Update QlikView Application Scripts
  32. Reload QlikView Applications
  33. Publish QlikView Applications
  34. Update QlikView Application Owners
  35. Reset App Descriptions
  36. Reset QlikView App Descriptions
Information note

To confirm the actual execution order of steps in a job, use the Show Steps button in the Jobs list. The full step list will be displayed in execution sequence.

Related pages

Visit the discussion forum at community.qlik.com

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!