Description:

• When organizations migrate from Confluence Data Center (DC) to Confluence Cloud, users often have a large number of legacy DC links stored in emails, chat tools (Slack, Teams), documentation, and browser bookmarks.
• Currently, these links become dead ends post-migration unless customers implement and maintain their own redirection solutions using a mapping CSV generated by Atlassian’s migration support tools.
• We are requesting a native, Atlassian-hosted redirection service that automatically forwards requests from legacy Confluence DC URLs to the correct Confluence Cloud page based on the migration mapping.
• This would eliminate the need for customers to build, host, and maintain their own redirect infrastructure and ensure a smooth user experience for all users accessing old links after migration.

Key requirements:

• Atlassian hosts and manages the redirection logic and infrastructure.
• Redirection should work for all standard Confluence DC URL patterns such as 

  /display/SPACEKEY/Page+Title

  and

  /pages/viewpage.action?pageId=...

  and

  /x/ewQO

Current workaround:

• Atlassian provides a mapping CSV, and customers must implement their own redirect logic, typically via web server rules or custom scripts.
• This is not scalable or feasible for many organizations, and introduces ongoing maintenance overhead.