Last updated May 16, 2025

What is link fixing?

After you migrate from Data Center to Cloud or between your Cloud sites, your instances live under a different URL, that’s why all links between individual entities (Jira issues, Confluence paegs) stop working, because they still use the previous URL.

This usually includes the following types of links:

  • Local links within the migrated instance, pasted as URLs

  • Remote links from other cloud instances to the migrated one

With Link fixing, you can update such links in bulk. How often you’ll do it depends on your migration timeframe – you can wait until all instances are migrated or do it after every migration.

Example: Remote link from a Jira issue to a Confluence page Example of a link

What's supported

Link fixing is supported for Jira and Confluence, and the following migration types:

  • From Data Center to Cloud
  • From Cloud to Cloud

You update links on every cloud instance separately. Before you start, you should identify all other instances that were originally linked to it.

You will specify their migrated cloud equivalents as new destinations for existing links, and also tell us where they were migrated from, so we can find and update the right links.

Here’s an example request body from the API where you’ll see the products mentioned above:

1
2

{
    "product":       "jira",                               
    "productURL":    "https://jira.atlassian.net",         
    "destinationURL":"https://confluence.atlassian.net",   
    "migratedFrom":  "https://confluence-datacenter.com",  
    ...
}

When you update links, you run a link update on an instance – you could also see it as a single task or a job. It updates all existing and compatible links pointing to the old URL (migratedFrom) to the new URL (destinationURL). You’ll most likely need to run multiple link updates on every product, for example if:

  • Some links weren’t updated the first time, because of insufficient permissions or errors

  • You migrated new data, which brought more links

  • You migrated more instances, so you now have more links to update

  • You can run as many link updates as you need. The already updated links won’t be included.

Local links are links to entities within the same instance, so theoretically they shouldn’t need to be updated. That’s true if you created such links through built-in features, such as Link issue – they don’t need updates. However, your users most likely pasted many local links into comments or pages as URLs. Such links include the old Base URL that needs to be updated.

In this case, the Cloud instance you’re updating and the new destination for existing links are the same:

1
2

{
    "product":       "jira",
    "productURL":    "https://jira.atlassian.net",
    "destinationURL":"https://jira.atlassian.net",
    "migratedFrom":  "https://jira-datacenter.com",
    ...
}

When you're ready, check out the tutorial or go straitgh to APIs.

Tutorial: Update links after migration

View REST APIs

Rate this page: