Every old Data Centre URL embedded in documents, tickets, emails, and bookmarks stops working the moment you move to Cloud. Finding and replacing them manually takes weeks — and misses the ones you didn't know existed.
Teams manually copy and paste document URLs into Confluence pages, wikis, and runbooks. One URL change, one wrong prefix, and the whole chain breaks — silently, with no way to know until someone hits a dead end.
Upload your migration export CSV and Link-a-Link automatically indexes every old-to-new URL pair across your entire workspace. Users can search by old DC URL, PageID, or page title and get the live Confluence Cloud equivalent in under a second — no admin help needed.
Admin uploads the migration CSV from the settings panel. The file is processed and indexed automatically — no manual steps, no waiting.
Users search from the global app page using an old URL, a PageID, or a partial page title. Bulk search mode accepts multiple queries at once.
The mapped Cloud link appears instantly. One click opens it. The search is logged to the analytics dashboard.
Configure your document numbering systems once — the prefix, the base URL, the system name. Then drop an IntellinQ macro anywhere in Confluence. Editors type a document number and the correct URL is resolved and displayed automatically. No copying, no pasting, no broken links when base URLs change.
| An editor types | IntellinQ resolves to |
|---|---|
| PDL-423 | docs.yourcompany.com/PDL-423 |
| SS-1017 | smartsolve.yourcompany.com/SS-1017 |
Fully hosted on Atlassian Forge. No servers to provision, no databases to manage, no deployment pipelines. Install from Marketplace and it works.
Every workspace's data is completely isolated. Your migration index never touches another organisation's data — verified with multi-tenant FCT testing.
A sharded indexing architecture handles hundreds of thousands of page mappings with sub-second lookup times. Professional plan has no row limit.
Use the global Confluence app page for ad-hoc lookups, drop the IntellinQ macro on any page for inline access, or use bulk search mode for whole lists.
The dashboard shows top searched terms, successful lookups, not-found rates, and recent activity — so you know exactly how your team uses the data.
No search queries are stored. No account IDs are logged. Support reports contain zero personal data. Compliant with Atlassian's data residency requirements.
Your IT or wiki admin exports the migration mapping CSV and uploads it from the Link-a-Link settings panel in Confluence. The file is processed automatically in the background — typically under 30 seconds for tens of thousands of rows.
Link-a-Link shards the index by tenant and stores it securely. No manual configuration. The search feature activates automatically the moment processing completes.
Anyone in the workspace opens the Link-a-Link global page and searches. Results appear as they type. Old URL, PageID, partial title — all work. One click takes them to the live Cloud page.
Hundreds of internal documents still link to old DC URLs. Instead of a months-long manual remediation project, your team uploads the migration export and the old links resolve instantly for everyone.
Your runbooks, incident playbooks, and change management pages reference document numbers like CHG-4521 or INC-9032. With IntellinQ macros, those references become live links that always point to the right place — even when base URLs change.
Link-a-Link's admin dashboard shows you what your team is searching for, what they can't find, and how often the mapping data is being used — giving you real insight into documentation health.
No. Link-a-Link is fully self-contained. Install it from the Marketplace and it works immediately — no AWS account, no Forge credentials, no infrastructure.
The standard export format from the Confluence Cloud migration assistant is supported. At minimum, the CSV needs columns for the old URL (or PageID) and the new Cloud URL. The admin panel validates the file on upload and shows a clear error if the format doesn't match.
Under 30 seconds for most files up to 50,000 rows. Very large files (200,000+ rows) may take 1–2 minutes. The admin dashboard shows processing status in real time.
Yes. Link-a-Link does not store search queries, does not log user account IDs, and does not share any data between workspace tenants. Support reports contain only aggregate counts and technical metadata — never personal data or page titles.
Absolutely. The two features are independent. Some teams use only IntellinQ for document linking; others use only Confluence Mapping for post-migration support. Both are included in every install.
Install Link-a-Link in one click from the Atlassian Marketplace. Your first 5,000 mappings and your first IntellinQ system are always free — no card required.
Link-a-Link