Jira Server reached end of support on February 15, 2024. If you are still on Server, you are running unpatched software with known vulnerabilities.
Jira Migration Costs 2026:
Server to Cloud Timeline, Budget, and What Breaks
A complete guide to migrating from Jira Server or Data Center to Cloud. Realistic cost ranges, a 4-phase timeline, and an honest list of everything that breaks during the process. With an interactive cost estimator to budget your specific migration.
Migration Cost by Team Size
Typical total migration cost ranges including assessment, app migration, execution, and stabilization. These are one-time costs separate from ongoing Cloud subscription fees.
Small
<50 users
9-14 weeks
Mid-Market
50-250 users
12-16 weeks
Enterprise
250+ users
16-20+ weeks
These ranges are based on typical consultant rates for Atlassian Solution Partners ($150-300/hour) and commonly reported migration projects. The largest cost drivers are the number of Marketplace apps requiring migration, the complexity of custom ScriptRunner scripts, and the volume of data being transferred. Simple migrations with standard Atlassian apps and minimal customization fall toward the low end. Complex environments with dozens of Marketplace apps, extensive Groovy scripting, and hundreds of thousands of issues fall toward the high end.
Migration Cost Estimator
Enter your environment details to get a rough cost and timeline estimate for your migration.
Includes ScriptRunner, Tempo, BigPicture, and other installed apps
Low: standard workflows, few custom fields. Medium: custom workflows, some scripts. High: extensive Groovy scripts, complex permissions, many integrations.
One-time cost, excluding ongoing Cloud subscription
From assessment kickoff to post-migration stabilization
4-Phase Migration Timeline
Every Jira Cloud migration follows a similar pattern regardless of team size. The phases below detail what happens at each stage, what it costs, and how long it takes.
Assessment
Inventory of projects, workflows, custom fields, Marketplace apps, and integrations. Gap analysis between Server/DC and Cloud capabilities. Migration readiness report with timeline and risk assessment.
App Compatibility
Audit all Marketplace apps for Cloud equivalents. Test app migrations in a sandbox environment. Identify apps with no Cloud version and plan workarounds. ScriptRunner and Insight/Assets migrations are typically the most complex.
Execution
Use Atlassian Cloud Migration Assistant for bulk migration. Migrate in stages - test projects first, then production. DNS and URL redirect configuration. User account mapping and SSO setup.
Stabilization
Monitor for data accuracy issues. Fix broken automations and integrations. User training on Cloud-specific features. Performance tuning and workflow optimization. Address permission model differences between Server and Cloud.
Free tool from Atlassian: The Atlassian Cloud Migration Assistant (CMA) is a free app that handles bulk data migration. It automates user mapping, project transfers, and configuration migration. While it simplifies the execution phase significantly, it cannot handle Marketplace app migrations, custom script conversions, or post-migration validation. Those require manual effort or paid consulting support.
What Breaks During Migration
An honest assessment of the most common migration issues, ranked by severity. Plan for these proactively to avoid surprises during and after the migration.
Marketplace app gaps
HIGHSome Server apps have no Cloud equivalent. ScriptRunner Groovy scripts must be rewritten as Forge or Connect apps. Budget $2,000-10,000 per incompatible app for replacement or custom development.
ScriptRunner/Groovy scripts
HIGHServer-side Groovy scripts do not run on Cloud. Every custom script needs rewriting using Jira Cloud REST API, Forge apps, or built-in automation. This is often the single largest migration cost.
URL changes
MEDIUMAll Jira URLs change from your self-hosted domain to atlassian.net. Every bookmark, wiki link, CI/CD integration, and documentation reference needs updating.
Attachment limits
MEDIUMCloud has a 256 MB per-file attachment limit (vs unlimited on Server). Large attachments need migration to external storage or compression.
Permission model differences
MEDIUMCloud uses a simplified permission model. Complex Server permission schemes with dozens of custom roles may need restructuring. Test thoroughly in a sandbox.
Historical data accuracy
LOW-MEDIUMTimestamps, user references, and changelog entries can shift during migration. Audit critical projects post-migration to verify data integrity.
Automation limits
LOWStandard plan limits automation to 500 runs/month. If your Server instance ran thousands of automations, you may need Premium plan post-migration.
The two highest-risk items are consistently Marketplace app compatibility and ScriptRunner migration. These account for the majority of migration project overruns. Before starting a migration, run a full app audit using the Atlassian Cloud Migration Assistant to identify incompatible apps early. For ScriptRunner, inventory every custom script and estimate the effort to rewrite each one using Cloud-compatible approaches (built-in automation rules, Forge apps, or REST API integrations). Scripts that modify issue data, trigger complex workflow transitions, or integrate with external systems typically require the most rewriting effort.
URL changes are often underestimated as a migration cost. Every bookmark, wiki link, Slack message, CI/CD pipeline reference, and documentation link that points to your old Jira Server URL needs updating. For large organizations with thousands of Confluence pages referencing Jira tickets, this can be a significant effort. Plan to set up URL redirects from your old server domain to atlassian.net to handle links that cannot be updated immediately. Also notify all stakeholders about the URL change well before migration day to minimize confusion.
Decision Matrix: What Should You Do?
If you are on Jira Server (end of support) or considering migrating from Data Center, here are your three options with clear decision criteria.
Migrate to Cloud
Best for teams under 1,000 users
- ✓Eliminates infrastructure management entirely
- ✓Access to latest features including Atlassian Intelligence
- ✓Atlassian is investing primarily in Cloud going forward
- ✓Automatic updates and security patching
- ✓Free tier available for evaluation before committing
Move to Data Center
Best for 1,000+ users needing self-hosting
- ✓Maintains self-hosted control and data sovereignty
- ✓Existing Server plugins often work with minimal changes
- ✓Simpler migration path from Server than to Cloud
- ✓Still receives security updates and support
- ✗Requires infrastructure investment and ops team
Switch Tools Entirely
Consider if migration costs exceed the value
- ✓A forced migration is a natural time to evaluate alternatives
- ✓Modern tools like Linear offer simpler experiences at similar prices
- ✓Avoids future Atlassian price increases and lock-in
- ✗Data export from Jira is complex and lossy
- ✗Team retraining and workflow redesign required
Frequently Asked Questions
How much does it cost to migrate from Jira Server to Cloud?+
Jira Server to Cloud migration costs range from $15,000 for small teams under 50 users to $250,000 or more for enterprise deployments over 250 users. The cost depends primarily on the number of Marketplace apps that need migration or replacement, the complexity of custom workflows and automations, the volume of historical data, and whether you use ScriptRunner or other Groovy-based customizations. A typical mid-market migration for 50 to 250 users runs $40,000 to $100,000 and takes 12 to 16 weeks. These figures include assessment, app compatibility testing, execution, and post-migration stabilization but exclude ongoing Cloud subscription costs.
How long does a Jira Cloud migration take?+
A typical Jira Cloud migration takes 9 to 20 weeks depending on complexity. The timeline breaks down into four phases: assessment (2 to 4 weeks) to inventory projects, workflows, and apps; app compatibility testing (2 to 6 weeks) to audit and test Marketplace app migrations; execution (1 to 2 weeks) for the actual data migration using Atlassian Cloud Migration Assistant; and stabilization (4 to 8 weeks) to monitor data accuracy, fix broken automations, and train users on Cloud-specific features. Enterprise migrations with many custom integrations and Marketplace apps can extend beyond 20 weeks, especially when ScriptRunner Groovy scripts need rewriting.
What breaks during a Jira Cloud migration?+
The most common issues during Jira Cloud migration are Marketplace app incompatibilities and ScriptRunner Groovy script failures, both rated as high severity. Server apps without Cloud equivalents need replacement or custom development, costing $2,000 to $10,000 per app. All Groovy scripts must be rewritten using Cloud REST APIs, Forge apps, or built-in automation. Medium-severity issues include URL changes affecting all bookmarks and CI/CD integrations, attachment size limits (256 MB on Cloud vs unlimited on Server), and permission model differences requiring restructuring. Lower-severity items include historical data timestamp accuracy and automation run limits on the Standard plan.
Is Jira Server still supported?+
No. Jira Server reached end of support on February 15, 2024. This means Atlassian no longer provides security patches, bug fixes, or technical support for Jira Server installations. Organizations still running Jira Server are operating unpatched software with known vulnerabilities, which poses significant security risks. Atlassian has been directing all Server customers to migrate to either Jira Cloud or Jira Data Center. Data Center is the only self-hosted option that still receives updates and support. If you are still on Server, migration to Cloud or Data Center should be treated as an urgent priority.
Need help planning your migration?
Calculate your ongoing Cloud costs after migration, or compare Cloud vs Data Center to decide which target platform is right.