Recommended Free Tools
First identify whether your organization runs Atlassian Server or Data Center: their deadlines are different. Server support ended on February 15, 2024 PT. For impacted Data Center products, end of life is March 28, 2029 at 23:59 PST, and the support wind-down began March 30, 2026. Use the applicable date to set a migration plan, then test the move and protect the production cutover rather than treating a calendar deadline as a migration schedule.
Which Atlassian deadline applies to your organization?
Check the deployment type for each product you use; do not assume that a Server date also applies to Data Center. Atlassian’s Server End of Support FAQ and Data Center End of Life announcement set out separate dates and product scopes.
As an Amazon Associate I earn from qualifying purchases.
| Deployment and scope | Milestone | What it means |
|---|---|---|
| Atlassian Server products and apps | February 15, 2024 PT | Support ended on this date. Atlassian says support and bug fixes are no longer available for Server products and apps. |
| Impacted Data Center products | March 30, 2026 | The announced support wind-down began. New customers can no longer buy new Data Center subscriptions or new Marketplace Data Center apps. |
| Existing customers of impacted Data Center products | March 30, 2028 at 23:59 PST | Existing customers may continue buying subscriptions, apps, and expansions until this date. |
| Impacted Data Center products | March 28, 2029 at 23:59 PST | End of life. Subscriptions and associated Marketplace apps expire and become read-only. Atlassian says technical support, critical-vulnerability security bug fixes, and Cloud connectors continue through this date. |
Server: the support deadline has passed
The Server end-of-support scope includes Jira Software, Jira Core, Jira Service Management, Confluence, Bitbucket, Crowd, Bamboo, Atlassian-built Server apps, and Marketplace apps for Server. Atlassian’s stated paths for Server customers are Cloud or Data Center, and it recommends Cloud for most Server customers. See its Server End of Support FAQ.
Data Center: check product-specific exceptions
The 2029 end-of-life announcement does not apply to Bitbucket Data Center: Atlassian says it will not end of life under this announcement and that existing customers will gain access to a Bitbucket Hybrid License for Data Center and Cloud. Atlassian also says certain Data Center customers may receive extended maintenance after March 28, 2029 by exception. Do not assume an exception or product-specific arrangement applies; confirm it directly with Atlassian via its Data Center End of Life information.
#1 Best Overall
How should you choose a destination?
For a Server deployment, assess Cloud and Data Center as the supported-platform paths, bearing in mind Atlassian recommends Cloud for most Server customers. For impacted Data Center products, include the announced end-of-life date in the decision: a Data Center upgrade does not remove that 2029 milestone. The destination needs to work for your products and constraints, not just fit a broad recommendation.
- Product and app fit: Check required features, Marketplace app availability, and whether integrations and customizations will work in the target environment.
- Security and location: Validate the specific security, data-residency, regulatory, and authorization requirements for your organization. For government environments, confirm the relevant authorization status and timing rather than assuming it is available.
- Operational fit: Compare the migration effort, acceptable outage, user and account readiness, and the ongoing operating model and cost.
- Deadline and support horizon: Consider the relevant Server or Data Center milestones, including purchase and support phase-down dates, not only the final end-of-life date.
Atlassian’s migration resources cover planning, methods, downtime, app assessment, and product-specific checklists. Confirm current, product-specific requirements with Atlassian before committing to a destination.
How long should you allow for a Jira or Confluence migration?
Atlassian reported an average of nine months from assessment through launch in a February 14, 2023 article, How to prepare for the end of server. Treat that as dated planning context, not a current guarantee or a forecast for your organization. Your schedule depends on your deployment, product and user footprint, app availability, customizations, policy requirements, test results, and stakeholder readiness.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Build your own estimate from work and evidence: discovery and destination decisions; app and account preparation; test migrations and fixes; user-acceptance testing; and the production cutover with post-migration checks. If a test reveals blockers, revise the schedule before booking the final window.
How to plan and test the move safely
- Establish the source facts. Record whether each product is Server or Data Center, its version, licenses, user count, data and customization footprint, integrations, and contractual or regulatory constraints. Map the work against the applicable dates above.
- Choose and validate the destination. Compare the required security, residency, functionality, app and integration support, operating constraints, and acceptable outage against the destination options available for your source deployment.
- Inventory apps and users. Use Atlassian’s migration hub for product-specific guidance on user management, app assessment, migration methods, and checklists. Resolve account or app gaps before relying on a production date.
- Confirm tool and source compatibility. Check that your source version works with the migration tooling you intend to use. Review prerequisites and pre-migration checks in the relevant product documentation before running a migration.
- Rehearse in a test environment. Back up the source, run checks, perform a test migration, and carry out user-acceptance testing. Fix problems and retry as needed; choose the production date based on test results. Atlassian’s 2024 Cloud Migration Checklist recommends this test-and-revise approach.
- Set a staffed production window. Select a low-activity period and allow contingency time. Ensure migration staff and any selected Atlassian or Solution Partner support are available. Tell support teams and stakeholders when the move is happening, and tell users what changes to avoid. Atlassian advises customers migrating more than 1,000 users to inform their Cloud Migration Manager of the production date at least a month ahead.
- Control and protect cutover. Use a runbook, take a final backup, and limit source-side changes while migration runs. Atlassian suggests temporarily limiting data creation, modification, and configuration changes—or briefly making the source read-only—to reduce changes during the event. Monitor progress, then validate the migrated environment and provide user support.
What Jira Cloud Migration Assistant covers
Atlassian describes Jira Cloud Migration Assistant as an app for moving Jira from Server or Data Center to Cloud. Its documented features include Marketplace app and user-email assessments, domain review, selective or full migration, pre-migration checks, reports, and error logs. The documentation says migration data is stored for 14 days from migration creation.
Listed coverage includes Jira Core, Jira Software, Jira Service Management, and certain Advanced Roadmaps plans. Data types include projects and issues, users and groups, boards and sprints, workflows and filters, and Assets. Check Atlassian’s Jira Cloud Migration Assistant documentation for the current details. This is Jira-specific guidance: Atlassian lists separate migration resources and assistants for Confluence and Bitbucket in its migration hub.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Who can help with migration planning?
If your team needs hands-on planning or implementation support, Atlassian’s migration materials point to Atlassian Solution Partners. Atlassian also lists FastShift, its dedicated-support migration program. Confirm current eligibility and terms with Atlassian; availability may change.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
