Jira Data Center is ending. Switch to Plane without trade-offs.

Self-hosted, air-gapped, and enterprise-ready.

Run Plane on your infrastructure with full control over your data, access, and operations.

• 2025
• 2026
• 2027
• 2028
• 2029

Important Dates

MARCH 2026
End of sale
New Data Center subscriptions and Marketplace apps are no longer available.

MARCH 2028
End of expansion
Existing customers can no longer purchase new licenses or expand their current plans.

MARCH 2029
End of life
All Data Center products become read-only with no support or security patches.

THE CASE AGAINST DEFAULTING

Defaulting to Atlassian Cloud is still a decision

Atlassian is ending Data Center. But moving to Atlassian Cloud isn't the only path, and it comes with trade-offs most teams don't evaluate until they're mid-migration.

• Control and data residency
  Atlassian Cloud moves your data into Atlassian's infrastructure and jurisdiction. For regulated teams, that can mean losing control over where data lives, how it's accessed, and whether you can meet compliance requirements.

• Cost trajectory
  Jira Cloud pricing scales with usage, with tiered feature gating and paid add-ons for capabilities that were included in Data Center. Predictable costs become harder to maintain as your system scales.

• Plugin dependency
  Most Jira workflows depend on Marketplace apps. Migrating to Cloud often means rebuilding that same system, plugin by plugin, with no guarantee of feature parity.

• Migration experience
  Atlassian's migration tooling varies by team size and complexity. Many teams hit gaps, manual steps, or long migration cycles with limited hands-on support.

THE ALTERNATIVE TO ATLASSIAN CLOUD

Self-hosted

Plane is built for teams that need to replace Jira Data Center without giving up infrastructure control. It brings projects, documentation, workflows, and AI into one system, with no plugins and no fragmentation, so your team doesn't have to rebuild how they work.

• Self-hosted by default
  Run Plane on your infrastructure or fully air-gapped, with full control over your data, network, and environment.

• Built as a system, not plugins
  Projects, docs, workflows, and reporting work together out of the box, without rebuilding your stack through Marketplace apps.

• Migration without disruption
  Import Jira and carry forward your workflows, structure, and ways of working. No rebuilding from scratch.

THE MIGRATION

How to move your Jira DC to Plane

1. Connect your Jira instance
   Enter your Personal Access Token, email, and domain. Read-only access. Jira stays untouched.

2. Map your workflows
   States, priorities, issue types, and users auto-map to Plane. Review and adjust what doesn't match.

3. Run the import
   Issues, comments, epics, sprints, and attachments come over. Most teams finish a dry run in under 3 hours.

4. Validate and cut over
   Run both tools in parallel. Sync new issues incrementally. Switch when your team is ready.

Dedicated onboarding specialist
Scoped migration plan, hands-on setup, and direct access to your migration engineer.

Training and documentation
Hands-on sessions for admins, project leads, and users. Productive from week one.

PLANE VERSUS JIRA

Everything you had on Data Center, and more

Uncompromised security

• Self-hosted and air-gapped

• Full data residency

• Audit trails

• Custom security policies

Resources for your migration

• Self-hosting deployment guide
• Jira to Plane migration guide
• Plane self-hosted architecture
• Air-gapped deployment

FAQs

How does migration from Jira DC work?
Connect your Jira instance with a Personal Access Token. Plane auto-maps states, priorities, issue types, and users. Issues, comments, epics, sprints, and attachments come over in a single import.

Can we self-host Plane like Jira Data Center?
Yes. Plane runs on your infrastructure via Docker Compose, Docker Swarm, or Kubernetes.

What about SSO, LDAP, and audit requirements?
Plane supports SAML SSO, OIDC, LDAP, Google OAuth, and GitHub OAuth.