OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appFind and fix broken legacy URLs in Confluence Cloud after migrating from Data Center or Server
Supporting media
Editions New
This app offers two different editions - Standard and Advanced. You can start a free trial of either edition, and change your edition anytime during or after the trial.
Standard
Onboard your team and scale fast
Includes:
URL Scanning
Fix URLs
URL Mappings
Scheduled Scans
Basic Governance
Advanced
Unlock the full range of app features
Everything from Standard, plus:
Full Governance Engine
Regex Search Mode
CSV/JSON Export
Advanced Mappings
Unlimited Scans & Schedules
More details
Legacy URL Scanner helps you complete your migration from Confluence Server/Data Center to Cloud by finding and fixing outdated URLs across your entire instance. Scan pages, blog posts, and comments for legacy server links pointing to your old infrastructure. Define URL mappings to replace old domains with new cloud URLs — one at a time or in bulk. Features include full-instance or space-scoped scanning with CQL support, async scanning for large instances, scheduled scans, governance rules with allowlist/blocklist, a dashboard with statistics and trend charts, full audit log, regex search mode, and webhook notifications via Slack or Microsoft Teams.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Legacy URL Scanner for Confluence integrates with your Atlassian app
Version information
Version 2.5.0•for Confluence Cloud
- Release date
- Mar 20th 2026
- Summary
- Minor version update
- Details
Release Notes — Rate Limit Compliance:
What changed:
- API calls now respect Atlassian's Retry-After header on rate limit (429) responses instead of using fixed delays
- Bulk operations (delete filters, attachments, versions) are now throttled in controlled batches to prevent rate limit triggers
- Scanner/board loading uses controlled concurrency instead of unbounded parallel requests
Why:
Atlassian enforced new points-based API rate limits on March 2, 2026. These changes ensure all apps stay within the burst limits and correctly back off when rate-limited.- Payment model
- Paid via Atlassian
- License type
- Commercial