Confluence Migration Exporter
What holds for Jira holds for Confluence: a clean migration starts with a reliable source. The Confluence Migration Exporter provides the complete picture of your Confluence environment.
- Complete picture of the Confluence environment
- Read-only, structure and configuration only
- Shipped signed, checkable at any time
- Read-only, no write access
- Evaluated against the Data Center original
- No interference with live operations
- Results documented transparently
As the sister plugin to the Jira Migration Exporter, the Confluence Migration Exporter delivers everything the Confluence migration needs in terms of structure and configuration knowledge: spaces and permissions, the page tree with versions, attachments, templates and user macros, labels, references, mentions, content restrictions, application links and the appearance.
Like its Jira counterpart it works strictly read-only and is installed as a signed package via the normal app management.
What a standard migration leaves open
After a standard migration
- Confluence as a blind spot in the migration
- Macros and references checked only in the cloud
- The appearance is lost unnoticed
- Unclear what is being accessed
With this tool Confluence Migration Exporter
- A complete picture of spaces, structure and permissions
- Captured beforehand, as the basis for repair
- Appearance and links captured too
- Read-only, transparent
How the Confluence migration gets its data
Installed once, strictly read-only.
-
1
Install
The signed package is deployed via the normal app management.
Verified: Installation checkable via the free status query.
-
2
Read out
Spaces, page tree, permissions, macros and more are provided read-only.
Verified: Read-only access only.
-
3
Evaluate
Analysis, reports and configuration repair work on this picture.
Verified: Evaluable even without live access to the system.
What it does
Complete environment picture
Spaces and permissions, page tree and versions, attachments, templates and user macros, labels, references, mentions, content restrictions and application links.
Structure and configuration
The exporter captures what a Confluence migration builds on: the structure of spaces and pages, not the editorial content where only configuration is needed.
Strictly read-only
Read-only operations exclusively, no write paths. The migration itself runs in a controlled way through the actual tools.
Basis for analysis and repair
The Confluence analysis, the reports and the configuration repair all build on this picture.
Appearance included
The appearance and the application links are captured too — details that are otherwise easily lost in a migration.
Signed and licensed
Shipped as a signed package via the normal app management, certificate supplied separately, without private keys. The status query stays free.
Common questions before migrating
Does the plugin read page content?
It captures structure and configuration — spaces, page tree, versions, permissions, macros and references. Where only configuration is needed, content is not accessed, and no write path exists.
Does the analysis work without live access?
Yes. The captured picture can be evaluated even without live access to the system — handy for planning and the assessment.
How is it delivered?
Like its Jira counterpart: as a signed package via the normal app management, certificate supplied separately, without private keys. Licensed, with a freely checkable status query.
Does the exporter cover the nested macros?
It captures them in full as structure. Resolving nested macros is the job of the Confluence tools; the exporter provides the reliable basis for that.
Safe and transparent
Reading separated from writing
Reads come from a read-only data layer; writes go through a single controlled channel. Read access never burdens your Cloud.
Evaluated read-only
Everything is evaluated read-only; nothing is written back into your systems. Operations and cloud budget stay untouched.
Repeatable without risk
Every step can be run again without doing harm. An interruption is no problem, and a second run creates no duplicates.
One isolated stack per customer
All tools run on the Jira Migration Manager platform, fully separated per engagement. No mixing of data.
All results are documented transparently and can be checked against the Data Center original. Nothing is silently changed or left out.
More tools
Migration platform
Jira Migration Manager
The platform that brings every migration tool under one roof and makes a Jira DC-to-Cloud migration safe and repeatable: separate read and write paths, rate-limited into the Cloud, credentials encrypted, one isolated stack per customer.
- Read-only read layer and rate-limited write channel kept strictly separate
- All tools on one shared data base, chainable into pipelines
- Token-secured perimeter, encrypted keystore, one stack per customer
Assets Migration
Asset Relink
Migrates Insight/Assets to the Cloud in full: fields and contexts, AQL filters, screens and the object values on every issue. Exactly where standard tools lose the links.
- Create fields, contexts and screens in the Cloud
- Translate AQL filters from Data Center to Cloud
- Relink object values on every issue
Managed Migration
Jira Migration Helper
JCMA migrates the bulk of your data but leaves configuration broken or unmigrated. Jira Migration Helper closes these gaps module by module and, with Managed Migration, runs the right fixes for each finished project automatically — every one dry-run by default and verified against the live Cloud API.
- Repair filters, dashboards, fields, roles and permissions that JCMA leaves open
- Managed Migration: automatically run the right fixes per project as it finishes
- Web UI or CLI, every module dry-run by default and secured by the idempotent write gateway
A fit for your migration?
Describe your case in a few lines — I'll tell you honestly whether and how this tool helps.
Book a callAtlassian ends support for Data Center on 28 March 2029. If you are moving a large, deeply connected environment, plan early rather than late.