When does Jira Data Center reach end of life?
Three dates matter. On 30 March 2026 Atlassian stops selling new Data Center licences to new customers. On 30 March 2028 licence sales end for existing customers too. On 28 March 2029 Data Center becomes read-only. Read-only is the end state, not the start of the problem — the practical deadline is whenever your renewal, your apps or your auditors get there first.
What happens to our Atlassian Data Center after the sunset?
After 28 March 2029, Atlassian Data Center products become read-only. All support, downloads, and renewals stop. Organizations must migrate to Atlassian Cloud or alternative solutions before this date to maintain full functionality.
How long does a Data Center to Cloud migration take?
Our published delivery windows run from ~2 days for a small, low-complexity instance to ~5 months for a large, high-complexity one, measured to a UAT-ready target. Every tier then includes 2 weeks of hypercare after go-live. Size sets the floor; apps and customisation set the rest.
How much does a Data Center to Cloud migration cost?
We publish a flat price for every size and complexity combination, from €1,000 at the small end to €86,000 for a large, high-complexity instance. It is a fixed price, not a day-rate estimate that drifts. If you are on or applying for Atlassian FastShift, the combined total drops by 20% because Atlassian carries the programme-management overhead.
What does the Jira Cloud Migration Assistant not migrate?
It carries the core well: issues, pages, users, groups, attachments, comments and history. What it does not carry is the configuration wrapped around them. Permission schemes that share a name with a scheme already in your Cloud target get renamed during migration. Issue security level permissions that reference unsupported custom field types do not migrate at all. Confluence user macros, ScriptRunner Groovy, Data Center-only REST endpoints, the shape of your Assets schema and filter JQL that breaks on a tenant move all need hands-on work.
What happens to our Marketplace apps?
Every app lands in one of three outcomes: the vendor has a Cloud version and a supported migration path, the vendor has a Cloud version but no path for your data, or there is no Cloud equivalent at all. The third case is the one that moves timelines, and we resolve it by rebuilding the functionality as a custom Forge app. Worth knowing separately: Atlassian Connect, which a large share of Cloud Marketplace apps still run on, reaches end of support on 31 January 2027.
Can we migrate without downtime?
Users keep working in Data Center right up to the cutover, and the cutover itself is a short, verified delta rather than a big-bang export. That is what zero-downtime honestly means: pre-staged users, groups and attachments, a rehearsed dry run, and a production window measured in hours rather than a lost weekend. What it does not mean is that the source instance stays writable while the final delta runs.
What happens to ScriptRunner scripts and user macros?
They do not move. Data Center Groovy does not run in Atlassian Cloud, and Confluence user macros have no native Cloud equivalent. We rebuild them as custom Forge apps so the functionality moves with your data instead of breaking on go-live, which is the same team and the same codebase as our Forge development service.
Do we have to migrate Jira and Confluence at the same time?
No — they can be staged, and on larger instances they usually should be. The order matters more than the timing: users and groups go first so identity resolves consistently, and anything that links across products, such as Confluence pages embedding Jira issues, needs both sides addressable when the second product lands. We plan that sequence in the assessment.