The toolbox
A family of specialised tools on one platform. Each covers a domain where the native path leaves gaps — all follow the same principle: dry-run by default, verification against the Data Center original, transparent reports.
Everything here runs in production — in the customer stack, in operator mode or as a signed Data Center plugin. You do not have to use the whole box to use part of it; what your project needs is decided by the assessment.
The platform services (ingress proxy, data warehouse, write gateway, keystore, portal) form the shared foundation — in detail on the Jira Migration Manager page. More on the Jira Migration Manager
Analysis & quote 2
Pre-migration assessment
JiraAnalyzer
A detailed assessment of your entire Data Center instance before the migration begins: where the move runs smoothly, where it gets difficult, what has to be reworked by hand — and where our tools take that work off your plate.
- Checks every area of the instance, from apps and automation to assets
- Names concretely what gets difficult and what needs manual rework
- Shows for each finding which of our tools covers it
Quote & cost
Effort & cost calculation
Shows, from the real inventory of your instance, where our toolset saves time and budget — and gives you the solid basis for your quote.
- Makes the savings from our tools visible
- Computes from the real inventory, read-only
- An open, transparent calculation
Data layer 3
Read source: Jira
Jira Migration Exporter
The Data Center plugin that supplies the migration with data: across 43 endpoints it delivers the complete configuration picture of your Jira instance — read-only, as the single reliable source for every tool.
- Complete configuration picture across 43 endpoints in 9 areas
- Read-only, no access to ticket content
- Replaces ScriptRunner scripts: usable without ScriptRunner too
Read source: Confluence
Confluence Migration Exporter
The sister plugin for Confluence Data Center: it delivers the complete picture of your Confluence environment — spaces, page tree, permissions, macros and more — read-only, as the reliable source for the Confluence migration.
- Complete picture of the Confluence environment
- Read-only, structure and configuration only
- Shipped signed, checkable at any time
Data layer
Extractor
Otherwise every migration tool queries Jira live — which is slow, fragile, and burns through your scarce Cloud API budget. The Extractor pulls Data Center and Cloud once, in full, into a versioned snapshot and serves it as a read-only API.
- One run pulls DC and Cloud in full into a versioned snapshot
- Read-only API with ready DC→Cloud mappings, type- and language-aware
- Blue-green: only a complete snapshot goes live, never half the data
Assets / Insight 3
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
Build assets
AssetMigrator
Rebuilds your complete Insight/Assets structure in an empty cloud tenant — including all object-to-object links, in four stages and checked against the Data Center original at the end.
- Schemas, object types and objects fully rebuilt
- Object-to-object links included
- Reconciled against the DC original at the end
Sync assets
AssetSync
Reconciles your assets repeatably from Data Center to the cloud — for staged migrations where the source data still changes during the transition.
- Repeatable DC→Cloud reconciliation via delta
- Create, update, delete — by plan
- Dry run by default, reference relink included
Structures & workflows 2
Structure for Jira
StructureMigrator
Moves your Structure for Jira boards from Data Center to Cloud — including the permissions and saved views that the official migration path leaves behind. Transferred board by board, verified against the Data Center state, with existing Cloud boards left untouched.
- Transfers permissions and views Atlassian doesn't migrate — board by board
- Maps users and project roles to their Cloud counterparts automatically
- Dry-run before every write step, duplicate protection for existing Cloud boards
Workflows
WorkflowMigrator
Moves your workflows to the cloud and works through exactly the break points where the native path leaves the most rework — and writes the procedure down as a runbook entry for the production run.
- Field, status and project references cleanly remapped
- Anything with no cloud equivalent goes into the deviation report
- Fixes error patterns beforehand, recorded as a runbook step
Fields & translations 3
Field translations
FieldTranslationMigrator
Moves the custom-field translations from Data Center to the cloud — with a field mapping straight from the Extractor API instead of guessing names, finding roughly twice as many matches.
- Field translations per language into the cloud
- Field mapping from the Extractor API, no name guessing
- Fields that cannot be matched go into a dedicated review list
Status translations
StatusTranslationMigrator
Moves the status translations from Data Center to the cloud — with a three-pass matching that even finds statuses that cannot be found globally, and records the origin of every match.
- Status translations per language into the cloud
- Three-pass matching, project-specific too
- Origin of every match recorded, gaps reported
Duplicate fields
CustomFieldMerger
Merges duplicate custom fields in the cloud — the right moment to clean up and at the same time the most dangerous, because filters, boards, automation and screens depend on them. Five stages, every write step behind a typed confirmation.
- Duplicate fields merged safely
- All dependencies found beforehand and followed up
- Every write step with a dry run and a typed confirmation
Service Management 2
JSM canned responses
CannedResponseMigrator
Moves the Service Management canned responses from Data Center to the cloud — idempotent, with placeholders remapped and, if Confluence was migrated too, references correctly redirected.
- Canned responses across all service projects
- Idempotent: a second run creates no duplicates
- Placeholders remapped, references redirected to the cloud
JSM queues
JSM-Queue-Repair
Repairs the queries behind the agent queues that point to Data Center-internal IDs after the migration and therefore run empty — precisely, without touching the other settings.
- Empty-running agent queues filled again
- Only the query replaced, everything else stays
- Only after confirmation, end state read back
Control & tracking 1
Control & track the migration
Migration jobs are created, pre-checked and started from within the tools; a read-only status page shows progress even to stakeholders without access. Managed Migration repairs automatically per completed project — the rework begins during, not after.
Repair after JCMA 2
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
Permission schemes
PermissionSync
Reconciles the permissions on both sides scheme by scheme and role by role — with a safety model for the area where a migration does the quietest damage: anything unclear is never deleted, and two emergency stops kick in before every deletion.
- Permissions reconciled scheme by scheme, role by role
- Anything unclear is reported, never deleted
- Two emergency stops before every real deletion
Operations & troubleshooting 1
Source-system control
During the migration your Data Center Jira is continuously monitored and deliberately steered in its operating parameters: start clearance before the run, memory and error monitoring during the migration, a controlled remote restart and an emergency stop. That keeps the source system safely under control at the decisive moment. If a run fails, a findings report at assessment level results.
Runbook & evidence 2
Runbook
Runbook generator
Generates the concrete step-by-step guide for migration day from the real instance inventory — along with an honest list of what stays manual.
- A ready runbook from the real inventory
- Remaining-work list in nine categories
- Visible gaps instead of guessed numbers
Final report
Final report
After the migration it answers the question every project runs into: what did not come across? And for each point it gives the location and the way to repair it — straight into your Confluence as living documentation.
- What is missing, where it is, how to repair it
- From the real migration and remediation logs
- Lands straight in your Confluence, multiply safeguarded
Where Jira Cloud offers no API 1
Production-grade tools without an API
For migration domains where Jira Cloud offers no documented API and no usable endpoints — such as field and status translations, Structure permissions or JSM. This is where full, production-grade tools step in: reproducible, with preview, approval and verification like everywhere in the suite. Sign-in is set up once, after which they run without further intervention. If Atlassian changes the interface, the tool relearns its path instead of being rebuilt.
Usable on their own, powerful together — as one coherent platform, not a collection of loose scripts.
Which tools does your project need?
A pre-migration assessment from your real instance answers that — the right first step.
Book a call