Skip to main content

Atlassian Cloud migration: what changes after the end of Data Centre (2029) and how to plan for it.

Linkedin
Xeridia's creativity regarding migration to Atlassian Cloud and the end of Data Centre in 2029.

Atlassian has announced the withdrawal of Data Centre, effective 28 March 2029. In addition, there will be previous milestones (end of new sales to new customers on 30 March 2026 and last purchase date for existing customers on 30 March 2028). After the end of life (EOL), licences and associated plugins will switch to ‘read-only’ mode.

How will the end of Data Centre impact businesses?

• Architecture change: from on-premise to SaaS.

• Functional and app review: DC and Cloud are not always equivalent; some plugins require alternatives.

• Identity and security: transition to Atlassian Guard (formerly Access) for SAML SSO, identity provisioning and policies (2FA, data controls).

• Data residency and compliance: choice of location and policies in accordance with regulations (GDPR, etc.).

• Business continuity: pilots, migration and rollback plans to avoid downtime.

Why do it with a specialised partner

• Users and workflows: requires the migration of a large number of accounts, permissions, workflows, automations, and SSO configuration.

• Corporate integrations: APIs, webhooks, and apps predominate in the cloud; identity provisioning and SSO are orchestrated from Guard.

• Operational risk: minimise disruptions, preserve history and traceability, and ensure compliance.

At Xeridia, we are a Platinum Solution Partner with over 18 years in the Atlassian ecosystem and specialisation in Cloud Migration. We tackle complex migrations (legacy, M&A, multiple tools) and accompany you in the modernisation of cloud applications:

1. Discovery and inventory (data, plugins, integrations, compliance).

2. DC to Cloud roadmap (functional equivalencies, app alternatives, identity/Guard).

3. Pilot and validation (performance, security, UX, data residency).

4. Phased migration plan, documented rollback.

5. Post-migration support and adoption (training and governance reinforcement).

Atlassian has already published the Ascend programme and a detailed timeline for this transition period. If your organisation is still on Data Centre, now is the time to plan.

FAQs

How long does a migration take?

It depends on the volume, plugins, and integrations. In medium/large companies, it is usually planned from weeks to months, with prior pilots and phases by area/team.

What about my Marketplace apps?

Each case is evaluated individually: Cloud equivalent, functional alternative or specific development.

What about compliance (GDPR, data residency)?

Atlassian Cloud allows you to set data residency for key products and apply controls with Guard. We validate these requirements in the design phase.

Request an evaluation for migration to Atlassian Cloud.