keepcalculator

06 Numbers and Powers

Atlassian Migration FAQ: Deadlines, Licensing, Backups

Card No. 06·75984 · Updated · Standard formula, shown below

This article answers the most common questions about migrating from Atlassian Server to Cloud or Data Center, focusing on deadlines, licensing, backups, and rollback. You’ll get clear, factual answers to the key concerns, plus the context needed to plan a migration with confidence.

Background: Why the Deadlines Exist

Atlassian stopped selling new Server licenses on February 2, 2021, and ended support for Server products on February 15, 2024. This means no more security patches, bug fixes, or compatibility updates for Server installations. The company’s push is toward Cloud, but Data Center remains a supported option for organizations that need self-managed deployment. Understanding these dates is crucial because they affect your licensing, security, and compliance posture.

Licensing: What Happens After the Deadline

If you still run Server after the support cutoff, you can continue using the software, but you do so at your own risk. Atlassian will not provide updates or fixes, and you may face compatibility issues with third-party apps. To stay supported, you must either move to Cloud or purchase a Data Center license. Data Center licenses are sold per user tier (e.g., 500, 1000, 2000+ users) and require an annual subscription. There is no perpetual license option for Data Center—only annual or multi-year terms. If you have a Server license, Atlassian offers a discount on Data Center for a limited time, but the exact terms vary by product and region.

Backups: What to Do Before You Migrate

Before any migration, you must have a complete, tested backup of your Server instance. This includes the database, the home directory (where attachments and configuration live), and any customizations. For Jira and Confluence, use the built-in XML backup for content, but note that it does not include attachments or the database schema. A full backup requires a database dump (e.g., pg_dump for PostgreSQL) and a file-level copy of the home directory. Test your backup by restoring it to a staging environment. A backup is only as good as its restore test.

Rollback: How to Undo a Migration

Rollback is possible if you keep your Server environment intact until the new system is stable. Before you start, document your current Server version, database version, and any customizations. After migrating to Cloud or Data Center, you can point your users back to the old Server instance if you haven’t decommissioned it. However, any changes made in the new system after the cutover will be lost. For Data Center, rollback is simpler because you are essentially upgrading your existing environment; you can revert to the previous version if you have a backup of the old installation. For Cloud, rollback is more complex because you are moving data to a different platform; you would need to export your data back and re-import it into Server, which is time-consuming and may lose recent changes.

How to Choose Between Cloud and Data Center

The choice depends on your organization’s needs. Cloud offers lower upfront costs, no server maintenance, and automatic updates. Data Center gives you control over data residency, custom integrations, and high availability. Consider factors like:

  • Compliance requirements (e.g., data residency, audit trails)
  • Internet connectivity (Cloud requires stable internet)
  • Budget (Cloud is subscription-based, Data Center has annual fees)
  • Team size (Data Center is cost-effective for large teams, Cloud has per-user pricing)

Atlassian provides a migration assistant tool that analyzes your Server instance and recommends a path, but the final decision should align with your IT strategy.

Migration Process: Steps and Tools

Atlassian offers a guided migration path using the Jira Cloud Migration Assistant and Confluence Cloud Migration Assistant. These tools automate much of the process, but you still need to plan:

  1. Inventory your current apps and customizations.
  2. Clean up your data (delete old projects, pages, and users).
  3. Run the migration assistant to copy data to Cloud.
  4. Verify the migrated data in a sandbox.
  5. Communicate the cutover date to users.
  6. Switch DNS and redirect users to the new instance.

For Data Center, the migration is essentially an upgrade from Server to Data Center, which involves installing the Data Center version and updating your license. Atlassian provides detailed upgrade guides for each product.

Common Problems and How to Avoid Them

Common issues include app incompatibility, data loss, and downtime. Third-party apps may not have Cloud versions, so you may need to find alternatives. To avoid data loss, always run a full backup and test it. Downtime can be minimized by doing a phased migration, but you should expect some disruption. Another frequent problem is underestimating the time needed for data cleanup—old projects and attachments can slow down the migration. Allocate extra time for testing and validation.

Costs and Budgeting

Cloud pricing is per user per month, with free tiers for small teams. Data Center has a flat annual fee based on user tier, which can be more cost-effective for large organizations. However, Data Center also requires server infrastructure costs (hardware, hosting, IT staff). Cloud includes hosting and maintenance, so the total cost of ownership may be lower for many teams. Atlassian offers a Server to Cloud migration discount, but it is time-limited. Check the current pricing on Atlassian’s website for accurate figures.

Frequently Asked Questions

Can I stay on Server after February 2024?

Yes, you can continue using Server, but you will not receive security updates or support. This is risky for compliance and security, so Atlassian strongly recommends migrating.

What is the difference between Server and Data Center licensing?

Server is a perpetual license with a one-time cost, but it has a user limit (e.g., 100 users for Jira). Data Center is an annual subscription with no user limit (tiered pricing) and includes features like clustering and high availability.

How long does a migration take?

It depends on the size of your data. A small instance with a few GB can migrate in hours, while a large instance with hundreds of GB may take days. Plan for at least a week to include testing and validation.

Can I rollback after migrating to Cloud?

Yes, but it is not automatic. You must keep your Server environment and have a recent backup. You can re-import your data, but any changes made in Cloud after the cutover will be lost. It is best to do a final sync before rolling back.

What happens to my third-party apps?

Many apps have Cloud versions, but not all. Check the Atlassian Marketplace for Cloud-compatible versions. If an app is not available, you may need to find an alternative or develop a custom solution.

Is there a free migration tool?

Yes, Atlassian provides free migration assistants for Jira and Confluence. They are built into the Cloud products and guide you through the process.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →