Atlassian Data Center Off-Atlassian Migration Tool That Carries Issue History, Custom Fields, and Permissions Into Plane, Outline, or Self-Hosted Confluence Forks
Atlassian stops new Data Center license sales on March 30, 2026, MQB peak-headcount billing has rolled out to monthly Cloud subscribers, and renewals are reportedly jumping 119–153% per Atlassian's own community forums. The 'Atlassian Ascend' migration program is built to funnel Data Center users onto Atlassian Cloud, not let them leave the ecosystem. Teams that want to land on Plane, Outline, GForge, or self-hosted Confluence forks have to stitch together half-finished open-source importers that drop comment history, sprint state, and granular permissions on the floor.
Don't pick a target product (Plane, Outline, etc) — be the source-side intermediate. Output a structured 'Jira-IR' (intermediate representation) JSON that any target can ingest, and partner with the destination tools to claim the assist. The MSP and consultancy channel will pay for this; end customers won't.
landscape (3 existing solutions)
Atlassian invests heavily in Cloud migration tooling. Off-Atlassian destinations exist but have shallow importers focused on attracting greenfield teams, not preserving a decade of Jira metadata. The integration math gets ugly fast for any single vendor to own — which is exactly why an independent migrator could charge real money.