Confluence Mapping
Find any old DC URL, PageID, or page title in your migrated workspace — instantly.

Admin panel — upload and manage your migration CSV
What it does
When you migrate from Confluence Data Centre to Cloud, every old URL embedded in documents, tickets, emails, and bookmarks stops working. Confluence Mapping solves this in three steps: an admin uploads the migration export CSV, the file is indexed automatically, and any user can then search for an old URL, PageID, or partial page title and get the live Cloud equivalent in under a second.
Key capabilities
- CSV upload — admin uploads migration export from settings panel
- Automatic indexing — no manual configuration, no waiting
- Multi-format search — by old URL, PageID, or partial page title
- Bulk search mode — multiple queries at once
- CSV export — download results for auditing
- Real-time analytics — every search logged to dashboard
SQL Queries for DC Links
Extract old Data Centre page IDs and URLs directly from your Confluence DC database to build the mapping CSV.
Why you need this
To build a complete mapping file, you need a list of every old DC page ID and URL from your Confluence Data Centre instance. The standard Confluence migration export does not always include this for every page — running a SQL query against your DC database is the most reliable way to get a complete list.
⚠ Important
Always run these queries on a read replica or during off-peak hours. Avoid running directly against a production database during business hours.
PostgreSQL
SELECT
c.CONTENTID AS dc_page_id,
s.SPACEKEY AS space_key,
c.TITLE AS page_title,
CONCAT('/wiki/spaces/', s.SPACEKEY, '/pages/', c.CONTENTID) AS dc_link
FROM CONTENT c
JOIN SPACES s ON c.SPACEID = s.SPACEID
WHERE c.CONTENTTYPE = 'PAGE'
AND c.CONTENT_STATUS = 'current'
ORDER BY s.SPACEKEY, c.TITLE;
MySQL / MariaDB
SELECT
c.CONTENTID AS dc_page_id,
s.SPACEKEY AS space_key,
c.TITLE AS page_title,
CONCAT('/wiki/spaces/', s.SPACEKEY, '/pages/', c.CONTENTID) AS dc_link
FROM CONTENT c
INNER JOIN SPACES s ON c.SPACEID = s.SPACEID
WHERE c.CONTENTTYPE = 'PAGE'
AND c.CONTENT_STATUS = 'current'
ORDER BY s.SPACEKEY, c.TITLE;
Expected output
| dc_page_id | space_key | page_title |
|---|
| 1024 | ENG | API Reference |
| 2048 | HR | Onboarding Guide |
| 4096 | OPS | Incident Runbook |
Export the query results as CSV. You will combine this with the Cloud mapping data from Atlassian (see next page) before uploading to Link-a-Link.
ℹ Next step
Once you have your DC page IDs, request the matching Cloud mapping file from Atlassian. See Cloud Links from Atlassian.
Cloud Links from Atlassian
How to request the DC-to-Cloud page ID mapping file from Atlassian Support after your migration.
What this is
When you migrate from Confluence Data Centre to Cloud, Atlassian generates a mapping file that links every old DC page ID to its new Cloud equivalent. This file is not always provided automatically — you typically need to request it from Atlassian Support after the migration completes.
How to request
- Go to Atlassian Support (support.atlassian.com)
- Create a new support request under Cloud Migration
- Request the DC-to-Cloud page ID mapping file for your migration
- Specify your migration batch date and Cloud instance URL
- Atlassian Support will provide a CSV file mapping old DC page IDs to new Cloud page IDs
💡 Tip
Request this file immediately after your migration completes. Atlassian Support typically takes 2–5 business days to provide the mapping file.
Expected file format
The mapping file from Atlassian will look similar to this:
| dc_content_id | cloud_content_id | cloud_url |
|---|
| 1024 | 5012 | /wiki/spaces/ENG/page/5012 |
| 2048 | 7834 | /wiki/spaces/HR/page/7834 |
| 4096 | 9156 | /wiki/spaces/OPS/page/9156 |
Combining with your DC export
Once you have both files (your DC export from the SQL queries and the Cloud mapping from Atlassian), combine them into a single CSV with columns for the old DC URL/page ID and the corresponding new Cloud URL. This is the file you upload to Link-a-Link.
ℹ Next step
With your combined mapping CSV ready, head to Uploading the migration CSV to load it into Link-a-Link.
Uploading the migration CSV
Admin guide for uploading your Confluence Cloud migration export.

CSV upload interface in the admin panel
Steps
- Open Link-a-Link admin → Confluence Mapping
- Click "Choose .csv file..."
- Select the migration export CSV from the Confluence Cloud migration assistant
- Click "Upload CSV"
- The file is processed and indexed automatically
ℹ Processing time
Under 30 seconds for most files up to 50,000 rows. Very large files (200,000+ rows) may take 1–2 minutes. Real-time progress shown on the admin dashboard.
Supported format
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.
Searching for old links
How users search for old DC URLs, PageIDs, and page titles.

Link Lookup — the global search interface
How to search
- Open the Link-a-Link global app page in Confluence
- Type your query into the search box
- Results appear instantly as you type
- Click any result to open the live Cloud page
What you can search by
- Old DC URL — paste the full old URL
- PageID — just the numeric page ID
- Page title — partial title matches work too
💡 Tip
No admin help needed — anyone in the workspace can use the search feature directly.
Bulk search & CSV export
Look up multiple old links at once and export results.
Bulk search
The bulk search mode accepts multiple queries at once. Useful when you have a list of old links that need to be resolved as part of an audit or remediation project.
- Open the Link-a-Link global page
- Switch to Bulk Check mode
- Paste your list of old URLs, PageIDs, or titles (one per line)
- Click Search
- Review the results table
CSV export
Export the results table as CSV for reporting, auditing, or sharing with your team. The export includes the original query, the resolved Cloud URL, and the match status (found / not found).
ℹ Use cases
Bulk search is especially useful for post-migration audits, where you need to confirm whether all known old links can be resolved.