Skip to content

Search

Atlassian Cloud Upgrade

Your way from Data Center to Atlassian Cloud

We work with you to assess whether and how Jira, Confluence and Jira Service Management can move to the cloud, when you need to start at the latest and how much effort will be involved. We then migrate them together with your team and continue to support you after go-live.

Request Cloud UpgradeHow Does a Migration Work?
XALT — Platinum Solution Partner, Atlassian logo with silver arrow symbol.Atlassian Specialized: Cloud Migrations (EMEA)
Departure board: reaching Atlassian Cloud on timeA split-flap departure board. Two deadlines are listed as departures: on 30 March 2028 the purchase of new Data Center licenses, apps and users ends. On 28 March 2029 the Data Center licenses for Jira, Confluence and Jira Service Management expire and become read-only. Their status changes from on time to final call, and for 2028 to gate closing. Between them the XALT flight: boarding, departed, landed. Below, a map tracks the small plane from Data Center to Atlassian Cloud, and a timeline shows that the landing comes before both deadlines. Result: landed on time. DEPARTURES ATLASSIAN DATA CENTER DATEFLIGHTSTATUS 30MAR2028DCPURCHASESOFGOFGOFGFGONIANIANIAIANNTNTNTNTTAETAETAEAETILILILLIMCMCMCCMECLECLECLCLEAOAOAOAOLSLSLSLSLILILILINNNNGGGG28MAR2029JIRACONFJSMOFOFOFFONININIINNNNNTATATAATILILILLIMMMMECECECCEAAAALLLLLLLLTODAYXALT→CLOUDBDLBDLBDLDLBOEAOEAOEAEAOAPNAPNAPNPNARADRADRADADRDREDREDREREDITDITDITDTDINENENEENGDGDGDDG FLIGHT TRACKING Data CenterAtlassian Cloud BOARDINGIN FLIGHTLANDED ON TIME TODAY30 MAR 202828 MAR 2029 Departure board: reaching Atlassian Cloud on timeA split-flap departure board. Two deadlines are listed as departures: on 30 March 2028 the purchase of new Data Center licenses, apps and users ends. On 28 March 2029 the Data Center licenses for Jira, Confluence and Jira Service Management expire and become read-only. Their status changes from on time to final call, and for 2028 to gate closing. Between them the XALT flight: boarding, departed, landed. Below, a map tracks the small plane from Data Center to Atlassian Cloud, and a timeline shows that the landing comes before both deadlines. Result: landed on time. DEPARTURES DATESTATUS 30 MAR 2028New DC licensesOFGOFGOFGFGONIANIANIAIANNTNTNTNTTAETAETAEAETILILILLIMCMCMCCMECLECLECLCLEAOAOAOAOLSLSLSLSLILILILINNNNGGGG28 MAR 2029Jira · Confluence · JSMOFOFOFFONININIINNNNNTATATAATILILILLIMMMMECECECCEAAAALLLLLLLLTODAYXA 101 → CloudBDLBDLBDLDLBOEAOEAOEAEAOAPNAPNAPNPNARADRADRADADRDREDREDREREDITDITDITDTDINENENEENGDGDGDDG FLIGHT TRACKING Data CenterAtlassian Cloud BOARDINGIN FLIGHTLANDED ON TIME TODAY03/202803/2029

Deadlines

Key Dates for Data Center Customers

March 30, 2026Since then, new customers can no longer buy Data Center licenses or Marketplace apps
March 30, 2028Last day for existing customers to buy new Data Center licenses, Marketplace apps and more users. Renewals remain possible afterwards, up to 28 March 2029.
March 28, 2029Jira, Confluence and Jira Service Management Data Center licenses and their Marketplace apps expire and become read-only. Bitbucket and Bamboo Data Center are not affected.

Why XALT

How we work on a migration

Testing before go-live

We migrate critical projects to a test cloud first. A script then checks whether every issue, page, attachment and permission arrived. You see problems before your teams do.

Compliance per use case

We check rules such as DORA, BAIT, NIS2, KRITIS or BSI C5 for each workflow, not across the whole platform. They often affect only a few processes – the rest can move as usual.

Clean-up before the move

What nobody uses any more does not move: orphaned projects, old spaces, apps without users. That saves test effort during the migration and licence costs in the cloud.

Support after go-live

After the move we help your teams with automations, integrations and Rovo. We measure usage before and after the migration, so you can see what the cloud changes in daily work.

Approach

Into the cloud in five steps

1
Where Are We Now?

Initial call

We talk through your situation, your deadlines and the right starting point. Free of charge and without obligation.

2
What Is the Business Case for Our Cloud Upgrade?

Business assessment

We review regulation, contracts, target picture and the five-year costs. You get a clear recommendation you can take to management and your boards.

3
What Do We Want to Move?

Technical assessment

We take stock of your environment: projects, apps, scripts, automations, users, SSO and backup. This becomes the migration plan with effort and timeline.

4
Ready for Go-Live?

Joint migration

We agree with you who takes on which tasks, and we migrate together. Test migrations run before go-live, so we find and fix problems before they reach your teams.

5
What Do We Get Out of the Cloud Upgrade?

Cloud upgrade

The work continues after the migration: we support your teams through the switch and help with automations, integrations and AI such as Rovo – so the value of the cloud shows up, measurably, in daily work.

Public-sector building and cloud connected by a bridge with security and audit symbols

Special Case: Regulated Industries and the Public Sector

When you first have to clarify whether you may move to the cloud

Banks, insurers, critical-infrastructure operators and public authorities have to justify a move to the cloud to supervisors and boards. We build that case with you – with DORA, BAIT, NIS2, KRITIS, BSI C5, GDPR and classified-information rules in view. Often only a few workflows need special conditions, and the rest can migrate as usual.

  • Criteria agreed up front: before we analyse anything, we agree with you on the criteria for the decision. From there, we only continue on the path you choose.
  • Partial migration checked: we check whether sensitive areas can be cleanly separated from the rest. The remaining part can then move to the cloud while the sensitive workflows stay where they are.
Cloud for the public sector
Atlassian Cloud: data residency and EU inference

What the Atlassian Cloud adds for you

  • Connected Context: The Teamwork Graph connects information from Atlassian tools. Through the Atlassian MCP interface, AI tools can use this context in supported workflows.
  • AI in Workflows: Practical scenarios link Loom recordings to Jira tickets and bring Jira content into Confluence presentations. This allows cloud migration to lay the foundations for productive, connected work.
  • EU Data Residency and AI: Application data can be stored in selected regions. For Rovo, AI processing can also take place in the EU. This helps you meet data residency requirements.
  • Security and Agent Governance: Agents can be managed like users and are granted only the access they need. Their changes are traceable, supporting governance and audits.

Quotes

Our Migration Services

Free: Non-binding Initial Consultation
  • Assessment and effort estimate
  • Brief review of your tools: Jira, Confluence, Loom
Contact
Upgrade Assessment
  • Guided Assessment of Your Business Case and Technical Foundation
  • We review regulatory requirements, contracts and governance, the target operating model, costs over five years and the timeline.
  • You receive a decision paper for senior management and committees.
Request a quote
Full-Service Migration
  • Upgrade Assessment included
  • We take care of the entire migration
  • Migration of Jira, Confluence, Bitbucket, Jira Service Management, and more
  • Migration of all apps
  • Priority Support
  • Costs are based on the effort incurred
Request a quote
Opsgenie logo

Combined offer

Migrate Opsgenie and get a cloud assessment on top

Atlassian is retiring Opsgenie, and alerting moves to Jira Service Management. If you commission us with this migration, you get up to five days of cloud assessment for your other Atlassian products on top.

That way you settle two questions in one step: how your on-call and alerting continue in Jira Service Management, and how Jira, Confluence and the rest get to the cloud.

Request an Opsgenie migration

Success Stories

Atlassian Cloud Migration at FATH & Weltbild

View into a manufacturing hall: a system moves parts along conveyor tracks, light floods in from behind through the gate

Mechanical engineering

Atlassian Cloud Migration of Jira, Confluence and Bitbucket

FATH ran Jira, Confluence and Bitbucket itself – and paid for every outage: troubleshooting, recovery, staff time. All three systems moved to the Atlassian Cloud in one go, without disrupting daily work. Downtime fell from twelve hours a year to almost none, and operating costs dropped by 80 percent.

Read case study →
Entrance of a Weltbild store in a shopping centre, customers walking past shelves full of books and magazines

Publishing and book retail

Cloud-to-Cloud Webshop Migration with Cloud Native Redesign

Weltbild migrated its own webshop a second time – this time with an infrastructure redesign instead of a plain move. Our DevOps team brought AWS expertise, infrastructure as code and agile methods, and kept the tight deadline.

Read case study →

Customer Testimonials

Jan Falkenreck, Head of Research and Development at Get AG, smiling in front of a light wall

Working with XALT during our Cloud migration earlier this year was very pleasant. The process was structured and transparent, and we felt well supported at every stage. The clear communication and fast execution stood out in particular.

Jan FalkenreckHead of Research and Development at Get AG
Eckard Nees

Jira, Confluence, and Bitbucket are among our most important tools, used daily. We needed to migrate all of them at once to make sure our teams wouldn't face any downtime. XALT worked with great dedication and drove the migration forward. Necessary changes on Atlassian's side were also handled promptly. An all-around successful project!

Eckard NeesDirector Digitalization at the FATH Group

We use Jira daily for task tracking, project support, and mapping digital approvals and processes. That's why a reliable and secure operation of the solution matters so much to us. The Cloud migration was a necessary step to keep using our data and processes in a future-proof way. XALT supported us on our way to the Cloud very competently and flexibly. Our customer-specific particularities were also analyzed and made available again in the Cloud environment. We felt well advised in every phase of the project.

Head of IT and Grid Usage Management at EWA Altenburg

FAQ

Frequently Asked Questions

We don't know whether we're allowed to move to the cloud. How do we start?

Best with a business assessment. Together we agree on what the cloud is measured against: regulation, contracts, target picture and five-year costs. You get a recommendation you can take to management and your boards.

Can we migrate only part of our setup?

Yes, if the sensitive areas can be cleanly separated. We check that and tell you what the separation costs. The rest can then move to the cloud as usual.

Can we migrate only Jira or only Confluence?

Yes. If you want to move only Jira or only Confluence to the cloud, for example, we migrate just that system. We plan the links between the products as part of it.

What changes for our automations?

From 3 December 2026, Atlassian bills Jira Automation by individual rule steps instead of rule runs. In the technical assessment we look at which rules exceed your allowance and propose changes.

Which Atlassian products and apps can be migrated?

We migrate Jira, Confluence, Jira Service Management and Bitbucket. Marketplace apps, scripts and custom changes are recorded in the technical assessment, and for each one we clarify whether it exists in the cloud or what replaces it.

How is our data protected during the migration?

Atlassian Cloud encrypts data and complies with GDPR. For the migration itself, we agree with you who gets access, how test data is handled and when the old environment is shut down.

Contact

Talk to us about your migration

Tell us briefly where you stand. We'll get back to you with a proposal for the next step.

Where are you right now? *