• Products
  • Documentation
  • Resources

Examples and use cases for updating product links

We’ve gathered some examples that are common to migrations. For each, we described the parameters that you need to set when updating the links.

All of the examples on this page assume that the destination product was migrated with one of the Cloud Migration Assistants, not the site import.

You can only update links on products that were migrated to cloud. If a Data Center instance is linking to a migrated product (and staying in your network), you won’t be able to update these particular links. Learn more about supported links

You have two Data Center instances:

  1. jira.mycompany.dc.com

  2. confluence.mycompany.dc.com

You migrated both to the mycompany.atlassian.net site that now includes:

  1. Jira Cloud in mycompany.atlassian.net

  2. Confluence Cloud in mycompany.atlassian.net

Here’s an overview of this setup and the links you’ll need to update:

Architectural view of the use case described above

To update remote links from Jira to Confluence, complete these steps:

  1. In admin.atlassian.com, choose Jira Cloud as the product you’re updating.

  2. Add the migrated Confluence Cloud as the destination product:

    1. Destination URL: Current cloud URL of Confluence Cloud (mycompany.atlassian.net)

    2. Migrated from: Original Base URL of Confluence Cloud (confluence.mycompany.dc.com)

To update remote links from Confluence to Jira, complete these steps:

  1. In admin.atlassian.com, choose Confluence Cloud as the product you’re updating.

  2. Add the migrated Jira Cloud as the destination product:

    1. Destination URL: Current cloud URL of Jira Cloud (mycompany.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud (jira.mycompany.dc.com)

You also need to update local links within each product. These can be links that were pasted by users and include the old Base URL. In such a case, product and destination product are the same. You can complete these updates as part of the updates described above or do them separately.

Example: To update local links within Jira, you:

  1. Choose Jira Cloud as the product you’re updating.

  2. Add the same instance of Jira Cloud as the destination product:

    1. Destination URL: Current cloud URL of Jira Cloud (mycompany.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud (jira.mycompany.dc.com)

Confluence needs an equivalent update.

You have two Jira Data Center instances:

  1. Jira Data Center 1: jira.dc1.com

  2. Jira Data Center 2: jira.dc2.com

You migrate them into Jira Cloud instances in separate sites:

  1. Jira Cloud 1: jira.cloud1.atlassian.net

  2. Jira Cloud 2: jira.cloud2.atlassian.net

Here’s an overview of this setup and the links you’ll need to update:

Architectural view of the use case described above

To update links from Jira Cloud 1 to Jira Cloud 2, complete these steps:

  1. In admin.atlassian.com, choose Jira Cloud 1 as the product you want to update.

  2. Add the migrated Jira Cloud 2 as the new destination product:

    1. Destination URL: Current cloud URL of Jira Cloud 2 (jira.cloud2.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud 2 (jira.dc2.com)

To update links from Jira Cloud 2 to Jira Cloud 1, complete these steps:

  1. In admin.atlassian.com, choose Jira Cloud 2 as the product you want to update.

  2. Add the migrated Jira Cloud 1 as the new destination product:

    1. Destination URL: Current cloud URL of Jira Cloud 1 (jira.cloud1.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud 1 (jira.dc2.com)

You also need to update local links within each product. These can be links that were pasted by users and include the old Base URL. In such a case, product and destination product are the same.

Example: To update local links within Jira Cloud 1, you:

  1. In admin.atlassian.com, choose Jira Cloud 1 as the product you’re updating.

  2. Add the same instance of Jira Cloud 1 as the destination product:

    1. Destination URL: Current cloud URL of Jira Cloud 1.

    2. Migrated from: Original Base URL of Jira Cloud 1.

Jira Cloud 2 needs an equivalent update.

This is supported only for Jira.

In this case, a single Jira Server or Data Center instance was migrated into multiple federated instances in cloud. We’ll look at updating local links within the federated instances and previously local links that became remote because of federation.

Case description

You have the following instance:

  • Jira Data Center. jira.dc.com. This instance has projects Teams 1 and Teams 2.

You migrated the projects Teams 1 and Teams 2 into:

  1. Teams 1 into Jira Cloud 1: jira.cloud1.atlassian.net

  2. Teams 2 into Jira Cloud 2: jira.cloud2.atlassian.net

Here’s an overview of links that you’ll need to update and recreate:

Diagram showing required link updates for federation.

To update links within the Jira Cloud 1 instance:

  1. In admin.atlassian.com, choose Jiira Cloud 1 as the product you want to update.

  2. Add the same Jira Cloud 1 instance as the destination product.

    1. Destination URL: Current cloud URL of Jira Cloud 1 (jira.cloud1.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud 1 (jira.dc.com)

You can complete the following update together with this one by adding another destination product.

To update links within the Jira Cloud 2 instance:

  1. Add the same Jira Cloud 2 instance as another destination product.

    1. Destination URL: Current cloud URL of Jira Cloud 2 (jira.cloud2.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud 2 (jira.dc.com)


To recreate and update previously local links, you need to use REST API.

When creating an API request, you’ll specify the following instances:

  1. Product URL: Current cloud URL of the product you’re updating, Jira Cloud 1 (jira.cloud1.atlassian.net)

  2. Destination URL: Current cloud URL of Jira Cloud 2 (jira.cloud2.atlassian.net)

  3. Migrated from: Original Base URL of Jira Cloud 2 (jira.dc.com)

Learn how to recreate links with REST API

To recreate and update previously local links, you need to use REST API.

When creating an API request, you’ll specify the following instances:

  1. Product URL: Current cloud URL of the product you’re updating, Jira Cloud 2 (jira.cloud2.atlassian.net)

  2. Destination URL: Current cloud URL of Jira Cloud 1 (jira.cloud1.atlassian.net)

  3. Migrated from: Original Base URL of Jira Cloud 1 (jira.dc.com)

Learn how to recreate links with REST API

You use a test instance as an intermediary before migrating into a production instance.

You have the following instances:

  1. Jira Data Center: jira.dc.com. This instance has a project Teams in Space that you want to migrate.

  2. Jira Cloud Test: jira.test.atlassian.net. You’ll migrate the project into this instance first, for testing.

  3. Jira Cloud Production: jira.prod.atlassian.net. After testing, you’ll migrate the project into this instance.

  4. Confluence Cloud: confluence.atlassian.net. This instance has links to the project Teams in Space in Jira Data Center. These links will break after migration.

You successfully migrated the project Teams in Space into Jira Cloud Test, and then into Jira Cloud Production. Now, you need to update links from Confluence Cloud to this project.

In such a case, you omit the test instance and update links from Confluence Cloud to Jira Cloud Production:

  1. In admin.atlassian.com, choose Confluence Cloud as the product you want to update.

  2. Add Jira Cloud Production as the destination product:

    1. Destination URL: Current cloud URL of Jira Cloud Production (jira.prod.atlassian.net)

    2. Migrated from: Original Base URL of Jira Cloud Production (jira.dc.com)

Additional Help