Enhancing Link Fixing – Supporting Cloud-to-Cloud Migrations

[#1]

Hello Everyone!

I am Debjeet, a Product manager in Migration tooling team.We heard your feedback on large number of broken links during C2C migrations and the post migration clean up is significantly time consuming and requires significant manual intervention from support teams. We are thrilled to announce that we’re shipping a major enhancement to the Link Fixing Tool that enables full Cloud-to-Cloud (C2C) migration support for broken links. Until now, the tool was primarily optimized for Server-to-Cloud use cases. This change equips the tool to automatically detect and fix broken links across cloud sites—removing one of the biggest hurdles to seamless cloud-to-cloud migrations.

In addition to link fixing, the update also introduces:

• Expanded link coverage across Jira and Confluence content types (including JSM support portal, boards, and backlogs).

• Failure reason visibility in the Link Audit Report, helping customers identify why a link couldn’t be fixed—without needing to raise a support ticket.

What are we solving for?
With this release, we are closing key experience and tooling gaps:

Before	After
C2C migrations were not supported for link fixing.	Fully supported and automated.
Atlassian Support Engineers had to manually patch links via scripts.	Admins can now self-serve with no tickets or scripts.
Link fix failures had no reason exposed.	Clear reason provided in the Link Audit Report.
Customers delayed environment acceptance.	Smoother go-lives with lower friction.

You can refer to https://support.atlassian.com/migration/docs/examples-and-use-cases-for-updating-product-links/#Cloud-to-Cloud-scenarios for the guidance on using the tool. All supported URL formats have been added/updated to https://support.atlassian.com/migration/docs/supported-products-and-types-of-links/ .

If you have questions or feedback, reach out to your Atlassian support contact.