Jira Migration Exporter
Every reliable migration needs a reliable source. The Jira Migration Exporter is a Data Center plugin that provides the complete configuration picture of your instance — the basis the assessment, the calculation and every tool read from.
- Complete configuration picture across 43 endpoints in 9 areas
- Read-only, no access to ticket content
- Replaces ScriptRunner scripts: usable without ScriptRunner too
- Read-only, no write access
- Evaluated against the Data Center original
- No interference with live operations
- Results documented transparently
For the assessment, the quote, the runbook and the individual tools not to contradict each other, they have to read from the same source. That is exactly what the Jira Migration Exporter delivers: an installable Data Center plugin that provides your instance configuration across 43 endpoints in nine areas.
It replaces the ScriptRunner scripts that used to be required — instances without ScriptRunner use the suite in full. Access is strictly read-only: configuration only, no ticket content, no write path.
What a standard migration leaves open
After a standard migration
- Data from scattered scripts and exports
- Without ScriptRunner, half the analyses are missing
- Contradictory numbers in assessment and quote
- Unclear what is being accessed
With this tool Jira Migration Exporter
- A complete picture from one interface
- Full scope, even without ScriptRunner
- One source that all documents read from
- Read-only, configuration only, transparent
How the suite gets your data
Installed once, checkable at any time.
-
1
Install
The signed package is deployed via the normal app management — with a separately supplied certificate, without private keys.
Verified: Installation checkable any time via the free status query.
-
2
Read out
Across 43 endpoints the configuration picture of the instance is provided read-only.
Verified: Read-only access only, no ticket content.
-
3
Provide
The Extractor read layer takes a versioned snapshot from it, which all tools work on.
Verified: All tools read from the same source.
What it does
Complete configuration picture
Projects and roles, fields and contexts, screens, workflows and security schemes, assets, service management, automation, Tempo, dashboards and filters — in one place.
43 endpoints, nine areas
A clearly defined interface delivers every migration-relevant part of the instance, structured and repeatably queryable.
Strictly read-only
Read-only operations exclusively, no write paths and no access to ticket content where only configuration is needed.
Usable without ScriptRunner
The plugin replaces the ScriptRunner scripts that used to be required. Instances without ScriptRunner run the entire suite with no detours.
One source for everything
Assessment, calculation, runbook and every tool read from the same picture. That is why the documents never contradict each other.
Signed and licensed
Shipped as a signed package via the normal app management; the certificate is supplied separately, without private keys. The status query stays checkable at any time.
Common questions before migrating
Does the plugin access ticket content?
No. It reads configuration only — projects, fields, workflows, schemes and so on. Issue content is not read, and there is no write path.
Do we need ScriptRunner?
No. The plugin replaces the ScriptRunner scripts that used to be required. Instances without ScriptRunner use the suite in full.
How is the plugin delivered and installed?
As a signed package via the normal app management, with a separately supplied certificate and explicitly without private keys. Operation is licensed; the status query stays free so the installation can be checked at any time.
Why a dedicated plugin instead of the Jira API?
Because the standard API delivers many migration-relevant details not at all or only incompletely. The plugin provides a complete, consistent picture — the basis for making sure nothing is overlooked.
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.
Runs on the Jira Migration Manager
This tool does not stand alone. It runs on the platform that unites every tool: a read-only read layer pulls Data Center and Cloud into a versioned snapshot, and every change goes through a single, controlled write gateway.
More on the Jira Migration ManagerMore 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.