Versions Compared

Old Version 14

changes.mady.by.user Nirosan (Unlicensed)

Saved on

compared with

New Version 15

changes.mady.by.user Nirosan (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

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 organizationorganizations.

After Step 2 - Starting the migration processis completed, all the connections will be migrated and listed together. If you do not identify the connection and it’s Salesforce URL link, you You will not be able to differentiate which connection belongs to which Salesforce URL anymore. You may have to restart the migration process.

  • 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.

...