Complex Atlassian migrations, done right.
I move your Jira and Confluence environment from Data Center to Cloud — including the parts where standard tools give up: automation, assets, structure, filters and permissions. Technically deep, transparent, with no data loss.
- Data Center → Cloud
- Tested on staging, live after validation
- Purpose-built tools
$ migrate scan --deep # scanning automation, assets & structure …✓ 128 critical findings detected $ migrate fix --apply (staging) ✓ results validated on staging✓ references relinked — ready for go-live
A migration that handles the hard cases too
Most migrations don't fail at moving the tickets — they fail at what breaks afterwards. That is exactly where I come in: I take on the technically demanding parts end to end, as a service, with clear checkpoints along the way.
No data loss
Every step is transparent and repeatable: first tested on staging systems, results validated, then the go-live — never blindly.
Depth, not surface
Automation, ScriptRunner, Assets/Insight, Structure, filters, dashboards, permissions: the areas a standard migration leaves behind.
With purpose-built tools
A proven family of tools — united in the Jira Migration Manager — automates analysis and repair, from the read-only assessment to per-project automated rework. Faster, more thorough and cheaper than manual work.
How the migration runs
Analysis
A full scan of Data Center and Cloud. I find what will break after the migration — before it does.
Migration
Moving content and configuration, aligned with JCMA and the specifics of your environment.
Repair
Automation, assets, structure and the rest are fixed on staging and verified against the Cloud — with Managed Migration running automatically per finished project.
Go-live
Sign-off, live migration after approval and handover with a report. You know exactly what happened.
One stack for the whole migration: the Jira Migration Manager
Every tool runs in the same stack — the Jira Migration Manager (JMM). A read-only read layer pulls Data Center and Cloud into a versioned snapshot, the specialised tools work on it, and every change goes through a single, controlled write gateway. One isolated stack per customer.
Source
Jira Data Center
Jira Migration Manager
One isolated stack per customer
Target
Jira Cloud
From vision to work package
Migration is rarely the whole story. I plan and steer complex IT initiatives end to end — from strategy to delivery, technically grounded and governance-safe.
Programme & project setup
Vision, roadmap and work packages — programmes and projects cleanly structured, steered and taken through to business as usual.
Architecture & governance
Target and current-state architectures (TOGAF, ArchiMate), decision papers and viable governance for cloud and operations.
GDPR & compliance
Data protection, data security and regulatory requirements considered from the start — through to ISO 27001 topics.
ITSM/ITIL & adoption
Service management per ITIL, change and adoption — so the new solution not only runs but gets used.
By the numbers
- years in IT transformation & migration
- 15+
- purpose-built migration tools on one platform
- 10+
- validated results before go-live
- 100%
- specialisation
- DC→Cloud
Tools that make the migration manageable in the first place
Born out of real migration projects: specialised tools for exactly the parts JCMA and standard procedures leave open. Asset Relink and the Jira Migration Helper with Managed Migration are the flagship products — and all of them run together on one platform, the Jira Migration Manager. Usable on their own, powerful together.
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
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
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
AutomationMigrator
Migrated Jira automation rules often only appear to work in the cloud: scope, field references, triggers and owner break, and some rules never fire. AutomationMigrator compares every rule against its Data Center original and repairs it via API — exactly where standard tools report a broken rule as migrated.
- Repair scope, field references, triggers and owner per rule
- Detect silent rules that exist but never fire
- Show every repair as a dry run first, then write on approval
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
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
Custom Migration Tools
JCMA and standard apps leave their own gaps in every migration — lost translations, disconnected data sources, missing upfront analysis. For exactly these gaps we deliver the right specialised tool, usable on its own and strong in combination.
- Six real tools for precisely the gaps no standard tool closes
- Usable individually, strong in combination — one consistent tool family
- Sandbox-first throughout, with dry-run, resume and traceable logging
Your migration runs in our own data centre
No third-party cloud, no shared host: all tools run on our own dedicated hardware — fully separated per mandate and secured to the current state of the art.
Own data centre
All tools run in our own data centre on dedicated hardware — separate from everything else, with no third-party cloud provider in between.
Linux & BSD
Operated entirely on hardened Linux and BSD systems — lean, transparent and with no unnecessary attack surface.
CrowdSec & modern security
Secured with CrowdSec and state-of-the-art security technology: active intrusion detection, hardening and continuous monitoring.
Isolated per mandate
Each mandate runs fully separated on dedicated hardware used only for it — no mixing of client data.
Every mandate gets its own fully separated environment — shielded by CrowdSec.
Wolf Wolzenburg
I specialise in Atlassian migrations from Data Center to Cloud — and especially in the technically demanding cases many shy away from. Where others wave it off, I build the tool that solves the job.
Behind the migration stands a trusted advisor for digital transformation: 15+ years of international programme and project leadership, as much at home with Microsoft 365, Azure and the Power Platform as with Atlassian. Cleanly documented, proven on staging, with no nasty surprises on go-live day.
-
DC→Cloud
migration focus
-
Hands-on
own code & APIs
-
Validated
before go-live
Wolf Wolzenburg
Atlassian Migration Expert · Wolzenburg Consulting
"A migration is only done when the complicated parts work again too — not just the tickets."
Let's talkMigration on the horizon? Let's talk.
Whether it's a full migration or just the tricky leftovers: describe your case in a few lines — I'll get back to you with an honest assessment.
Usually a reply within one business day.