The Atlassian Data Center roadmap: Is Your Migration Timeline a Plan or a Prayer?

Share

If you’ve been part of the Atlassian ecosystem for a while, you remember the wave of migrations triggered by the end of Server support. For many teams, it was a sprint against the calendar. 

Now, the clock is ticking on Atlassian Data Center.

With the March 30, 2026 milestone behind us, Atlassian has officially stopped selling new Data Center licenses to new customers. If you are already running Data Center, you still have support, for now. But the runway is shrinking faster than most IT roadmaps account for.

With the next hard deadlines approaching in March 2028 and March 2029, the question every enterprise IT leader needs to ask is simple: Is your cloud migration timeline a realistic plan, or is it a prayer?

 

The Hard Deadlines: What’s Passed and What’s Ahead

Atlassian’s roadmap for winding down Data Center isn't an overnight switch; it's a phased phase-out designed to push organizations systematically toward Atlassian Cloud.

Here is where things stand:

  • March 30, 2026 (Passed): End of New DC Sales. Atlassian and Marketplace partners ceased selling new Data Center subscriptions, apps, and trials to new customers. If an organization wasn't already on Data Center, Cloud is now the only path forward.
  • March 30, 2028 (Approaching): End of Expansions & New Apps. Existing Data Center customers will no longer be able to purchase new apps from the Marketplace, increase user tiers, or buy additional licenses. Your footprint freezes.
  • March 28, 2029 (Final Cutoff): End of Life (EOL). Full support and maintenance officially end. Jira and Confluence Data Center instances transition to read-only mode, and security patches stop entirely. (Note: Bitbucket follows a distinct hybrid licensing model, but core collaboration tools will shut down).

 

Why "We Have Until 2029" Is a Dangerous Trap

When teams hear "2029," the immediate reaction is often relief: "We still have time."

In enterprise IT, that sense of security is deceptive. Moving from Data Center to Cloud is fundamentally different from a routine version upgrade. It is an architecture transformation, a security review, and a business process realignment all rolled into one.

Consider the reality of enterprise migration schedules:

  1. Discovery & App Assessment (2–4 months): Taking inventory of hundreds of custom fields, workflows, active user directories, and Marketplace apps. Many legacy on-prem apps do not have a 1:1 cloud feature match and require testing modern Cloud alternatives or Forge apps.

  2. Data Cleanup & Architecture (2–3 months): Decades of accumulated Jira data means stale projects, orphaned schemes, and inactive users. Migrating clutter to Cloud inflates subscription tiers and degrades performance. Cleaning it up takes cross-team negotiation.
  3. Proof of Concept & Dry Runs (3–5 months): Testing the Atlassian Cloud Migration Assistant (JCMA/CCMA), running script conversions (especially ScriptRunner or custom REST integrations), and timing database cutovers over weekends.
  4. User Acceptance Testing (UAT) & Training (2–3 months): Validating permissions, notification schemes, and third-party integrations with actual business teams while introducing users to the Cloud interface.
  5. Final Cutover & Hypercare (1 month): The freeze, execution, validation, and post-launch troubleshooting.

Add these up, and a standard enterprise migration realistically takes 9 to 18 months.

If your organization plans to migrate before the March 2028 expansion freeze (which you should, especially if your headcount is growing), the window to start discovery is right now.

 

The 3 Big Surprises That Derail Migration Timelines

Having guided enterprises through complex Atlassian migrations for over a decade, we repeatedly see the same three roadblocks stall timelines:

1. App Parity & Custom Scripts

On Data Center, teams frequently built deep custom logic with direct database access, custom Java plugins, or extensive ScriptRunner routines. In Atlassian Cloud, you operate in a multi-tenant API and Forge environment. Direct SQL queries are gone, and API rate limits exist. Identifying which scripts must be rebuilt using Jira Automation or Forge takes engineering time.

2. User Management & Access Governance

Data Center often relied on local directories or internal LDAP configurations. Transitioning to Cloud means implementing Atlassian Guard (formerly Atlassian Access), integrating with Identity Providers (IdPs) like Okta or Azure AD, and establishing centralized domain verification. Security and governance sign-offs are rarely quick.

3. Compliance, Data Residency & Legal Approvals

For financial services, healthcare, and European enterprises subject to GDPR, data residency is a critical checkpoint. Atlassian Cloud offers robust in-region data residency (including Germany, Switzerland, the US, and more), but getting internal Infosec and Data Protection Officers (DPOs) to review and approve cloud architectures takes months of lead time.

 

How to Turn Your Timeline into a Plan

You don't have to scramble at the last minute. A successful migration is simply a series of well-sequenced, low-stress milestones:

  • Step 1: Run an Instance Audit. Run the Cloud Migration Assistant in assessment mode. Identify inactive users, unused projects, and app usage data.
  • Step 2: Map Your Marketplace Apps. Review every installed plugin. Categorize them into Must Have, Replace with Cloud-Native/Automation, or Retire.
  • Step 3: Secure Your Identity Strategy. Configure your organization in Atlassian Administration and test single sign-on (SSO) with your identity provider early.
  • Step 4: Execute Iterative Test Runs. Never let the final cutover be your first full data migration. Run multiple staging dry runs to clock exact migration speeds and resolve database integrity issues.

Recommended Migration Guides & Playbooks


Don't Leave Your Cloud Migration to Chance

The end of Data Center isn't an emergency if you start on your own terms. Taking control of the timeline now lets you clean up technical debt, optimize user licenses, and move to Cloud with zero disruption to your teams' daily work.

Ready to see what your migration pathway looks like?

Contact Idalko’s certified Atlassian Platinum Experts to book a pre-migration assessment, evaluate app compatibility, and build a predictable, battle-tested migration roadmap.

 

Let’s Talk. It’s on The House.

CONTACT US