Cost of Migrating to Jira Cloud
Still on Jira Server or Data Center? Here’s the real cost of migrating to Cloud — timeline, budget, what breaks, and what to prepare for.
Small team (<50 users)
$15k–40k
All-in migration cost
Mid-size (50–250 users)
$40k–100k
All-in migration cost
Enterprise (250+ users)
$100k–250k+
Complex migrations with many apps
Migration timeline
Assessment & Planning
- ✓Audit current Jira instance (projects, users, workflows)
- ✓Inventory all Marketplace apps — check Cloud compatibility
- ✓Identify custom scripts and integrations
- ✓Data volume assessment (attachments, history)
- ✓Define rollback plan
App Compatibility & Cleanup
- ✓Replace apps that have no Cloud equivalent
- ✓Rebuild custom scripts as Jira Automation or Forge apps
- ✓Archive or delete stale projects to reduce migration size
- ✓User provisioning: set up SSO, directory sync
- ✓Test migration in sandbox
Migration Execution
- ✓Run Atlassian Cloud Migration Assistant
- ✓Migrate data (projects, boards, issues, attachments)
- ✓Migrate users and permissions
- ✓Validate data integrity post-migration
- ✓DNS / SAML cutover
Post-Migration Stabilisation
- ✓Re-configure automation rules in Cloud
- ✓Team training on Cloud UI differences
- ✓Monitor performance and user adoption
- ✓Decommission old Server/DC infrastructure
- ✓Update all integrations pointing to old URL
Cost breakdown
| Cost Item | Low Estimate | High Estimate | Notes |
|---|---|---|---|
| Atlassian Cloud licence (first year) | $5,000 | $50,000 | Depends on users and plan |
| Migration consultant fees | $5,000 | $30,000 | More complex = more cost |
| App replacements / rebuilds | $2,000 | $20,000 | Per incompatible app |
| User training | $500 | $5,000 | $50/user estimate |
| Productivity dip (2–4 weeks) | $5,000 | $40,000 | $200/user estimate |
| Infrastructure decommission | $500 | $5,000 | DC only: server teardown |
| Data cleanup & archiving | $1,000 | $8,000 | Before migration |
| Integration re-work | $2,000 | $15,000 | Per connected system |
| Total | $21,000 | $173,000 | Full project range |
What breaks during migration
These are the most common failure points — plan for them before you start.
Marketplace app gaps
Not all Server/DC apps have Cloud equivalents. Popular gaps: ScriptRunner (Cloud version limited), Insight/Assets (restructured), legacy test management tools.
Custom Groovy scripts (ScriptRunner)
Server ScriptRunner scripts don't migrate. You'll need to rebuild them in Jira Automation, Forge, or a third-party service.
URL changes
Your Jira URL changes from `jira.yourcompany.com` to `yourcompany.atlassian.net`. Update all integrations, bookmarks, Slack apps, webhooks.
Attachment size limits
Cloud has per-attachment limits. Large attachments may fail to migrate — pre-clean is recommended.
Permission model differences
Cloud uses a different permission model (global vs project admin). Plan for a permissions audit.
Historical data accuracy
Some metadata (sprint history, certain custom field histories) may not migrate cleanly. Validate critical audit trails.
Automation rule limits
Standard Cloud caps automation at 500 rule runs/month. Heavy automation users will need Premium.
Should you migrate to Jira Cloud?
Migrate to Cloud if:
- ✓ You want to stop managing servers
- ✓ You have fewer than 500 users (Cloud is cost-competitive)
- ✓ Your apps have Cloud equivalents
- ✓ You’re okay with data in Atlassian’s cloud
- ✓ You want automatic updates and new features
Stay on Data Center if:
- → You have 500+ users (DC may be cheaper)
- → Strict data sovereignty requirements
- → Heavy customisation via ScriptRunner
- → Air-gapped environments
- → You prefer a predictable annual licence over usage-based pricing
Planning a Jira migration?
Get a free stack audit — we’ll map your current apps, flag compatibility risks, and give you a realistic migration budget before you commit.
Get a Free Stack Audit →