In this step, you will plan for a migration from Classic Connector to the new Salesforce & JIRA Cloud Connector.

The New Connector is built on the Atlassian Connect framework and has a different data model than the Classic Connector. Hence, you will need to run a self-service export and import, as well as some further configurations. 

Prerequisites

• You have reviewed Migrating from Classic Connector for Salesforce & Jira server to cloud.

Things to Note

Maintenance window

Depending on the size of the data and the complexity of the existing configuration, it may take a few hours to complete these steps. We advise you to schedule a maintenance window in your organization to perform the migration.

Review the rest of the steps

To gauge the time you will need to go through the migration steps, we recommend reviewing all of the steps before executing.

Creating custom fields in Jira Cloud for fields mapped in the Classic Connector

Please take note that Classic Connector exports mappings with reference to the field’s name as the field’s id can be different in Jira Server and Jira Cloud. Our migration service uses the field’s name to import and add bindings in Jira Cloud.

In order for mappings to be imported, you will need to create the custom fields with the same name as they are in Jira Server for those fields that are mapped in Classic Connector.

If multiple fields with the same name are found in Jira Cloud, the migration service adds mapping for one of the fields and the field’s id will be logged in migration logs.

You may review the migration logs after importing Bindings. If the wrong custom field was mapped, you can update the mapping and select the correct field.

Any existing data on the New Connector will be wiped

Performing the migration will destroy any data (if it exists) in the New Connector. It does not remove Jira data.