The Migration feature is where the magic happens. Use this screen to decide what to do and where to do it.

This feature provides an easy to follow process for safely transferring data between Jira Cloud instances. Use a migration to select Jira Cloud instances and desired projects to be copied between them. Before the final transfer, our app uses a simulation feature to ensure a successful outcome. Once configured, run the migration and the projects will be copied between instances.

What is a migration?

In the general sense, a migration is a task completed by Project Configurator for Jira Cloud. The Migration functionality is how project configurations are moved from one Jira Cloud instance to another. Instances are selected, and configurations are copied between them.

Configuring a migration

  1. From the Migration screen, click the New Migration option.

    The new migration is created, allowing you to declare source and target Jira instances. 

    The source instance is where configurations will be copied from and the target instance is where configurations will be copied to.

  2. Click the Add Configuration icon, for Step 1.

  3.  Select a source Jira Instance. 

    Configured connections are available for selection, or click New Connection to establish a new Jira Cloud instance.

    See our Connections page to learn more about establishing and authorizing Jira Cloud connections.

  4. Click Ok.

  5. Click the Add Configuration icon, for Step 2.

  6. Select the target Jira instance, then click Ok.

  7. The From and To steps appear with the Ready status icons, and the instance names are displayed.

    To change either source or target instance click on the appropriate step. Then, unselect and reselect from available connections.
  8. Click the Add Configuration icon, for Step 3, to pick projects to be copied from the source instance. Multiple projects can be selected.

    Can't find the project your looking for? You only have access to the projects here, that you do in your Jira source instance (connected in Step 1). You may need to contact your Jira Administrator to grant permissions for projects that are not available to you in PC4JC.

  9. Make selections, then click OK to confirm. 

  10. Once selected, the number of projects are displayed on the screen and selection is confirmed with the Ready Status icon.

    The choice can be amended before proceeding, by clicking the Ready status icon.
  11. Step 4 is now active and available to carry out a simulation. Click Run to carry out the simulation.

    1. During the simulation, feedback messages are presented in the Activity Log. These can be later interrogated in the Reporting screen.
  12. Upon completion, the simulated result is identified as successful or unsuccessful. Any relevant feedback messages appear as icons next to the associated step.
    1. Click a feedback message icon to see the full message in the Reporting screen. 
    2. If the simulation returns a warning message, click the associated step to make necessary changes. Then, the simulation can be run again.
  13. On completion of a successful simulation, a green Redo option appears. You may click this to carry out an additional simulation or proceed to running the actual migration.

  14. Click the Run icon, for Step 5, to proceed with the actual migration.

    As with the simulation, feedback messages are presented in the Activity Log. These can be later interrogated in the Reporting screen.

Execution timeout

Project Configurator for Jira Cloud currently has a maximum execution time for simulations and migrations of 15 minutes. It is unlikely for an execution to exceed this time limit, unless the transfer request is for an exceptionally large amount of data. 

Our recommendation, if you're experiencing timeouts with an execution, is to decrease the size of the transfer. Click the icon for Step 3, What, to deselect items for transfer. Once this initial migration has been completed successfully, the removed items can be still transfered using a second migration.

We plan to make updates for these executions, based on our customers needs. Stay up to date with any changes, using our Release Notes.