Jira Cloud Migration.
Step by step.
Atlassian is ending Server licences and Data Center is becoming increasingly costly. Moving to Cloud is the logical next step for most organisations — but it requires careful preparation. We guide you through the entire process, from analysis to hypercare.
What to expect from your Cloud Migration
What stays the same
Your data, projects, issues, workflows and history. Jira Cloud shares the same core — your team will work in a familiar environment.
What changes
URLs, some Marketplace apps and the admin interface. Cloud introduces new features (Automations, Advanced Roadmaps), but some Server plugins have no Cloud equivalent.
What improves
Automatic updates, better performance, mobile access and a sandbox environment. No more worrying about servers, backups or security patches.
Cloud Migration Process
Pre-migration assessment
We map your instance: projects, custom fields, workflows and Marketplace apps.
Output: Inventory reportApp Assessment
We verify the Cloud compatibility of every add-on and propose alternatives for those that are incompatible.
Output: App migration planCloud preparation
We set up the Cloud site, configure Atlassian Access, and set up SSO and domain verification.
Output: Ready Cloud tenantTest migration (dry-run)
We run the Cloud Migration Assistant, transfer data to the sandbox and measure the time required.
Output: Dry-run report + UAT environmentUAT and fixes
Your team tests in the Cloud sandbox. We resolve any discrepancies and fine-tune workflows.
Output: Sign-off documentProduction cut-over + hypercare
Final migration performed outside business hours. Monitoring, data validation and team support.
Output: Live Cloud environment + hypercare supportPre-migration checklist
Deactivate inactive users
You pay per user in Cloud. Deactivate accounts of people who have left or no longer use the system.
Document your custom fields
How many do you have? Which ones are actually used? Cloud has a custom fields limit — clean up before you migrate.
List your Marketplace apps
Which plugins do you use? Do they have a Cloud version? At what cost? This directly affects your overall budget.
Back up your data
Even though the Atlassian Cloud Migration Assistant is safe, always keep a backup. Export your projects, configurations and attachments.
Inform your users
Communication is key. Let your team know what is changing, when and why. This significantly reduces resistance to the transition.
Schedule training
The Cloud UI differs from Server. At a minimum, administrators need an introductory session on Cloud-specific features.
Indicative scope
Small instance (up to 25 users)
Straightforward migration with no complex integrations. Scope confirmed after an initial consultation.
Medium instance (25–100 users)
More custom fields, workflows and Marketplace apps. Timeline depends on environment complexity.
Large instance (100–200 users)
Phased migration, change management and advanced integrations. We will prepare a no-obligation estimate after an initial call.
Frequently asked questions about Cloud Migration
Will we lose data during the migration?
No. The Cloud Migration Assistant transfers data in full — issues, attachments, comments, history, workflows and configurations.
Do all Server plugins work in Cloud?
Not all of them. Roughly 70–80% of popular apps have a Cloud version. For the rest we propose alternatives or rewrites using native Automations.
Do we have to migrate everything at once?
No. Jira, Confluence and JSM can be migrated in stages. We recommend starting with Jira, then Confluence.
How much does a Jira Cloud migration cost?
The scope depends on instance size and environment complexity. We will prepare a no-obligation estimate after a free initial consultation.
How quickly will users adapt to the Cloud UI?
The Cloud interface is more modern and intuitive. Most users find their way around within an hour. For administrators we recommend a 4-hour training session.