Migrating Connector for Salesforce & Jira from Classic to NextGen

Owned by Nirosan (Unlicensed)
Last updated: Oct 19, 2023
3 min read

This page outlines the steps to migrate your Connector data from Classic Connector for Salesforce & Jira (Classic) to Connector for Salesforce & Jira Server (NextGen).

This guide is for Jira administrators who want to migrate their user experience from Classic Connector to NextGen Connector. The data migration happens within the same server.

At the end of this guide, you will have:

  • Migrated your Classic Connector to Nextgen Connector.

  • Retained Classic Connector’s historical association data after the migration to NextGen Connector.

  • Migrated connections, mappings, and associations from Classic Connector to NextGen connector.

Prerequisites

Before you start the migration, ensure to go through the following:

This guide assumes that you have installed Connector for Salesforce & Jira Server for the first time and have only been using Classic Connector for Salesforce & Jira.

If you have been using both Classic Connector for Salesforce & Jira and Connector for Salesforce & Jira before this migration, the following will happen post-migration:

  • Connection configuration will be overwritten if a Connection with the same name exists.

  • Entity mapping and field mapping for bindings will be updated using the configuration from Classic Connector.

Jira Data Center allows you to run a cluster of multiple Jira nodes. Perform and complete the migration strictly on one node only. Different nodes don’t share the same migration state.

For example, you have 2 nodes in your Jira data center and start the migration in the first node. When you access the second node, the migration is not started as this data does not carry over.

Before starting the migration, check the application link page, if there are multiple connections pointing to different Salesforce URLs, take a screenshot of those connections or copy them down.

The migration assumes that the Jira Admin knows the correct mapping between the connections and the Salesforce organizations.

After Step 2 - Starting the migration processis completed, all the connections will be migrated and listed together. You may have to restart the migration process if you are not aware of the correct mapping between connections and Salesforce organizations. For more information, check out Step 2 - Starting the migration process | Identifying Salesforce URLs.

  • Understand the feature differences between the Classic connector for Jira Server and the Connector for Salesforce and Jira (NextGen).

  • Allocate time to understand the steps required to upgrade, reconfigure, and test the data.

  • This migration does not transfer data across any services, instead, it transforms the existing data that is used by the Classic Connector to match the new Next Gen Experience.

Upgrading app versions

In Jira Server, ensure both connectors are up-to-date. We recommend the following versions (Refer to Atlassian Marketplace for the latest supported version):

  1. Click the cog icon (Administration) > Manage apps > under Atlassian Marketplace, select Manage apps again.

  2. Find “ServiceRocket Salesforce.com Connector Plugin” and “Connector for Salesforce & Jira” from the list.

  3. Expand the section to see the version.

  4. If you need to upgrade to the latest version, click Upgrade.

Reviewing connections, mappings, and application links

To check your connection(s) and mapping(s) configuration:

  1. Click the cog icon (Administration) > Manage apps > under Cloud Connectors, open Connections, Mappings, and Mapping Schemes in a new tab.

To check your application link(s):

  1. Click the cog icon (Administration) > Applications > under Integrations, click Application links.

Next step