## [Broken Links After a Confluence Cloud Migration: How to Find and Fix Them](/blog/broken-links-after-confluence-cloud-migration.md)

October 14, 2026 ·

<!-- -->

7 min read

[NGPilot](https://ngpilot.com)

Quick Answer

A Cloud migration moves your content. It does not fix the links **inside** it. Anything a user typed by hand — an old Jira URL in a page body, a Server link pasted into a comment in 2021, a macro pointing at your old domain — survives the migration verbatim and now points at a host that no longer exists. Find them with advanced search on the old domain, define one mapping rule per domain, preview every match before rewriting, and sweep page bodies, blog posts, comments, macro parameters and attachment names separately.

The migration is done. Pages moved, spaces are there, the site is live and people are using it. Then someone clicks a link in an onboarding page and lands on a 404 that points at `jira.mycompany.com` — a hostname that stopped answering the day you cut over.

It is a common post-migration complaint, and it has a specific cause worth understanding, because the fix is different depending on where the link is.

What you'll learn

1. Which links the migration fixes and which it silently leaves behind
2. Why comments and macro parameters are where the damage hides
3. The search queries that actually find the stragglers
4. How to build mapping rules that are safe to run in bulk
5. Why Jira links inside Confluence need their own mapping

**Tags:**

* [confluence](/blog/tags/confluence.md)
* [cloud-migration](/blog/tags/cloud-migration.md)
* [broken-links](/blog/tags/broken-links.md)
* [confluence-admin](/blog/tags/confluence-admin.md)
* [how-to](/blog/tags/how-to.md)

[**Read more**](/blog/broken-links-after-confluence-cloud-migration.md)