Migrating from Data Center to Jira Cloud: A Complete Guide
The Cloud Advantage: Why Now Is the Time to Move
With Atlassian's recent announcement about Data Center's end-of-life, teams are accelerating their Cloud migration plans. It makes sense - Atlassian is channeling its development resources into the Cloud platform, delivering faster feature rollouts, enhanced automation capabilities, and continuous improvements to roadmaps and dashboards.
The Cloud shift eliminates the fragmentation of tools and removes infrastructure headaches. When Atlassian takes over availability, scaling, backup management, and upgrades, your team can redirect their energy toward perfecting workflows and improving delivery.
Many organizations initially chose Data Center for security reasons, but Cloud has made tremendous strides in this area. You'll now find expanded data residency options, robust compliance frameworks like FedRAMP, and dedicated single-tenant environments for organizations with strict security requirements. For most teams, the Cloud platform now provides all the security controls they relied on in Data Center, plus a more straightforward path to stay current.
Starting your migration journey requires thoughtful planning: carefully cataloging your current setup, executing pre-migration verification checks, and thoroughly testing in a Cloud sandbox before touching your production environment.
The Jira Cloud Migration Assistant (JCMA) and Atlassian's comprehensive migration resources provide clear pathways, effective tools, and validation procedures to keep downtime minimal and avoid technical complications.
In this guide, we'll share practical strategies for organizing your migration and provide hard-won insights based on our experience helping teams successfully transition to the Cloud.
Laying the Groundwork: Migration Planning Essentials
Taking Stock: Assessment Phase
Before transferring any data from Data Center to Cloud, you need a clear picture of your current environment. Conduct a thorough inventory including:
- Project assessment – Distinguish between active and abandoned projects; determine which ones truly matter
- Workflow evaluation – Examine complexity levels and identify unnecessary transitions
- Custom field review – Identify and merge duplicate fields while removing obsolete ones
- Dashboard and report inventory – Determine which need to be preserved
- User and group analysis – Verify accounts and remove dormant profiles
This comprehensive audit streamlines your migration, resulting in a more efficient and clean transition.
Third-Party App Evaluation
Cloud compatibility varies significantly across marketplace apps. While some support seamless migration through JCMA, others require custom migration processes, and a few may not have Cloud equivalents at all. Identifying potential blockers early prevents unwelcome surprises during the actual migration.
When evaluating your Data Center apps for Cloud readiness, look for these key indicators:
- Comprehensive JCMA integration and detailed migration resources
- Strong security credentials: Runs on Atlassian (ROA), data residency compatibility, SOC2 verification
- Clear Cloud pricing structure
- Equivalent functionality between DC and Cloud versions
Selecting Your Migration Approach
You'll need to choose between two primary migration strategies:
- Complete site transfer (lift-and-shift): Move your entire Jira Software or JSM instance in one operation
- Incremental migration: Transfer projects in batches, enabling functionality testing and minimizing service disruption
Atlassian's Cloud Migration Guide supports both methods, and your choice should reflect your instance size, complexity level, and acceptable downtime threshold.
Creating Your Migration Blueprint
After completing your assessment, develop a structured migration plan covering:
- Detailed timeline with scheduled test phases and final cutover dates
- Selected migration approach (complete vs. incremental)
- Resource allocation – assign clear responsibilities for data cleanup, app verification, user administration, and communication
A well-defined plan creates a clear roadmap for all stakeholders and minimizes the risk of delays or technical complications.
Pre-migration Optimization
Before transferring content to Jira Cloud, optimize your Data Center instance. A streamlined environment migrates more efficiently and with fewer complications.
Data Center Preparation Steps
Data Cleanup
- Remove or archive obsolete projects and test environments
- Deactivate dormant user accounts and streamline redundant groups
- Consolidate overlapping custom fields and remove unused ones
- Archive legacy issues that don't require migration
App Compatibility Verification
- Thoroughly review each marketplace app in your ecosystem
- Confirm Cloud availability and understand the data migration process
- Use Atlassian's app assessment tools within JCMA to identify Cloud-ready apps and understand migration pathways
Migration Tooling Preparation
- Ensure JCMA is installed and updated on your Data Center instance
- Configure a dedicated Cloud sandbox environment for testing, keeping it separate from production
Understanding Your Migration Options
You have two primary methods for transitioning from Data Center to Jira Cloud: the Jira Cloud Migration Assistant (JCMA) or Jira Site Import. Your selection should consider instance complexity, size, and acceptable migration downtime.
Option 1: Jira Cloud Migration Assistant (JCMA) - Recommended Approach
JCMA serves as Atlassian's purpose-built migration tool for transferring projects, users, groups, and configurations to Cloud environments. It enables staged migrations, allowing project-by-project transfers, result verification, and risk minimization. The tool preserves issue history while helping you evaluate marketplace apps and automations before the final transition.
For most organizations, this represents the optimal approach. It reduces disruption, handles diverse workflows and custom fields effectively, and facilitates planned, phased migration. This method particularly benefits teams wanting to test in sandbox environments, address permission or user management issues early, and ensure smooth transitions during the final production migration.
Key Requirements
- Compatible Data Center version with latest JCMA installed
- Properly configured destination Jira Cloud site
Process Overview
- Deploy and launch JCMA on your Data Center instance
- Link to your Cloud environment and develop a migration strategy
- Evaluate apps, projects, and users; resolve duplicate/invalid emails; confirm domains
- Execute pre-migration diagnostics and address flagged issues
- Specify migration components: Projects, Users & Groups, JSM configurations, and supported Apps
- Implement and supervise the migration; review logs; confirm results
Option 2: Jira Site Import (Complete Backup Transfer)
The Jira Site Import method involves exporting a comprehensive XML backup from Data Center and importing it into Jira Cloud. This all-at-once approach works well for small, straightforward instances.
Consider this approach for scenarios requiring a single cutover when extended downtime is acceptable. Be mindful of size restrictions and understand that imports typically overwrite existing Cloud data, with limited support for partial imports. Plan comprehensive validation procedures and establish a rollback strategy.
Process Overview
- Generate a complete Data Center backup
- Import into your Cloud platform
- Validate data integrity, permissions, dashboards, and workflow functionality; resolve discrepancies before going live
Expert Recommendation: If uncertain, begin with JCMA. You can still employ Site Import for specific scenarios after testing with JCMA and identifying components that require alternative approaches.
Test Migration: Rehearse for Success
Always conduct a test migration before making changes to your production environment. This reveals what transfers smoothly to Jira Cloud and what requires adjustment, helping reduce actual migration downtime.
Create a dedicated test Cloud environment. Utilize a separate sandbox to trial your migration without affecting users. Install identical marketplace apps and replicate key settings from your production environment.
Thorough Testing Guidelines
- Start with representative projects before expanding
- Verify issues, attachments, comments, and history records
- Test workflows, custom fields, dashboards, and automated processes
- Confirm permission structures and user management (groups, roles, access levels)
- Validate app functionality and integration behavior
Refine configurations, optimize data, or adjust migration parameters based on your findings. Continue testing until you achieve clean results.
Involve key stakeholders in the testing process. For instance, include project leads or service agents to perform typical tasks in the test environment and provide feedback. This helps identify practical issues early and refines your post-migration orientation process.
Executing the Migration
Schedule your migration during low-usage periods to minimize disruption. Clearly communicate the timeline, expected impact, and where users can monitor status updates.
Remember to set your Data Center instance to read-only mode to prevent changes during the migration. Then proceed with your chosen method, typically JCMA, while closely monitoring the process.
Follow your planned sequence precisely: projects first, followed by users/groups, and finally any app data supported by the migration tool. Monitor logs and warnings continuously, addressing minor issues immediately rather than allowing errors to accumulate.
Immediately after completion, verify the Cloud environment:
- Examine representative projects to confirm proper transfer of issues, attachments, and histories
- Test complete workflow sequences; verify transitions, validators, and automations
- Check permission structures and user management settings
- Review dashboards, filters, and custom fields for missing elements or duplications
After confirming everything functions correctly, verify completion with a focused checklist: user accounts are operational, data integrity is confirmed (for projects, workflows, dashboards, and custom fields), and essential apps are functioning as expected.
If you discover gaps, address them immediately and reprocess only the affected elements. Then remove the read-only restriction and announce completion, including information about where users can report issues during the stabilization period.
Post-migration Adjustments
Begin with reviewing permissions and roles. Cloud permission structures often differ from Data Center configurations, so performing a quick audit prevents frustration: verify users can browse and modify issues, access boards and dashboards, and administer appropriate projects. When issues arise, examine permission schemes first, followed by groups and project roles.
Conduct an early user management review. Verify accounts and email domains, remove unexpected access, and reassign project roles as needed. For Jira Service Management users, verify portal access and customer permissions to ensure agents and customers can resume work promptly.
Next, review workflows and automations. Certain validators, post-functions, or scripted rules from your on-premises environment may not exist in Cloud. Rebuild essential rules using native Cloud automations, then perform basic "create - transition - notify" tests to ensure proper functionality. Monitor custom fields as well; redundant or unused fields can impede team efficiency and create interface clutter.
To maintain continuity, perform brief functional tests in key projects: create issues, process them through primary workflows, verify notifications, and confirm board and report functionality. Address any issues immediately and retest affected areas.
Effective communication is essential after migration completion. A concise announcement highlighting Cloud platform enhancements (such as integrated roadmaps and enhanced native automation) and support resources will alleviate concerns and accelerate adoption.
Finally, plan a focused optimization review. Identify redundant apps, audit remaining Data Center components, standardize schemes, organize dashboards and filters, and document your new processes for future project implementations. This targeted approach reduces ongoing administration requirements and maintains your Jira Cloud environment's performance and usability.
Addressing Common Migration Challenges
Even with careful planning, certain patterns frequently cause difficulties. Here's what to monitor and how to quickly resolve issues without extending migration downtime.
App and Add-on Compatibility Issues
Many marketplace apps behave differently in Cloud environments compared to Data Center, and some don't automatically migrate data. If you depend on scripting or time-tracking extensions, prepare for reconfiguration. Conduct a comprehensive app assessment and research each vendor's migration pathway using Atlassian's app evaluation tools.
Warning signs: Missing information, workflow disruptions, or feature gaps after migration.
User Management Discrepancies
Account mappings between DC and Cloud are often imperfect. Duplicate accounts (identical email with different usernames) or reactivated dormant users may appear. If you utilized LDAP/AD in your on-premises environment, consider implementing SCIM provisioning through Atlassian Guard to maintain clean user management in Cloud.
Best practice: Validate email addresses and domains during preliminary checks; synchronize groups from your identity provider to ensure permission structures match team expectations.
Permission Configuration Mismatches
Certain global permissions and group-to-role mappings translate inconsistently. When users unexpectedly lose browsing or editing capabilities, or when dashboards appear empty, first examine the project's permission scheme, then verify group and role memberships. Comparing against your Data Center model typically reveals the discrepancy.
Automation and Workflow Disconnects
Cloud automations operate with different triggers, actions, and service limitations. On-premises scripted validators or post-functions frequently require Cloud-native reconstruction. When transitions fail or notifications stop working, examine the rule's audit trail and Cloud automation limitations, then simplify the rule structure or divide it into smaller components.
Custom Field and Configuration Conflicts
Naming duplications (e.g., multiple "Customer Name" fields), unnecessary custom fields, or incompatible field types can interrupt migration or create data mapping problems. Merge duplicates and remove obsolete fields before migration, then inspect screens and dashboards afterward to ensure proper field rendering.
Large Data Volume Challenges
Extensive product data, particularly attachments, can slow migration processes or exceed Cloud plan limitations. Standard plans have product-specific storage constraints; consider archiving older projects, reducing attachment sizes, or implementing a staged migration for data-intensive teams to minimize risk.
Recovery strategies:
- Only reprocess the affected projects or app data after resolving the root cause
- Maintain a focused post-migration verification list (issues, attachments, workflows, permissions, essential apps)
- When a rule or integration fails, revert the change, maintain site usability, and refine in your sandbox before redeploying to production
Transitioning Marketplace Apps to Cloud
The majority of marketplace apps support Cloud environments, and many developers provide clear migration pathways through the Jira Cloud Migration Assistant. A practical approach involves evaluating each app during planning, confirming Cloud availability, and understanding whether data transfers automatically or requires manual intervention. For workflow-critical or dashboard-essential apps, consider implementing a limited pilot, then validate in a sandbox before proceeding to production.
When reviewing marketplace listings, look for trust indicators such as the Runs on Atlassian Badge and SOC2 certification, which validate the vendor's security credentials.
Smart Checklist, for example, displays these trust indicators on the Atlassian marketplace, confirming its Cloud readiness and security compliance.
Check out Smart Tools for Jira on Atlassian Marketplace.
For specific migration steps or data handling questions, consult the vendor's documentation or contact their support team for migration guidance customized to your Cloud environment.
Final Thoughts
Successful Data Center to Jira Cloud migration hinges on thorough planning, realistic testing, and transparent communication. Audit your existing environment, select appropriate migration tools (typically JCMA), conduct comprehensive sandbox testing, and verify permissions, user management, and key applications after transition.
Following migration, monitor system health closely: promptly address minor issues, eliminate unnecessary configurations, and optimize automation and scheme structures to help teams resume normal operations quickly. For detailed guidance, consult Atlassian's Cloud Migration Guide. For additional context on app migration and preparation, our previous article on Server-to-Cloud migration provides valuable supplementary information.
Once established, take advantage of Cloud-exclusive features: native automation capabilities, enhanced search functionality, and integrated roadmaps to establish more efficient workflows in your new Jira Cloud environment.
Frequently Asked Questions
What primary advantages does Jira Cloud offer compared to Data Center?
Jira Cloud delivers faster feature updates, integrated automation, enhanced roadmaps and dashboards, while eliminating infrastructure management requirements. Atlassian manages availability, scaling, backup processes, and upgrades, allowing your team to concentrate on workflow optimization and delivery improvement rather than maintenance tasks.
How do I determine whether to use site migration or phased migration?
Site migration (complete transfer) works effectively for smaller instances or when a clean transition is necessary. Phased migration better suits larger, complex environments as it enables project-by-project migration, functionality testing, and reduced service interruption. Your selection should reflect instance size, complexity, and acceptable downtime duration.
What happens to marketplace apps during migration?
Most marketplace apps support Cloud migration, though functionality and data transfer methods vary. Some apps integrate with JCMA for automated migration, others require manual setup, and a few may lack Cloud equivalents entirely. Always verify app compatibility and review migration documentation before proceeding.
How can I ensure correct permission transfer for users?
Cloud permissions don't always directly correspond to Data Center configurations. After migration, perform a thorough review of permission schemes, group memberships, and project roles. Test access with representative users to confirm they can browse issues, view boards/dashboards, and perform necessary functions.
What should I do if workflows or automations malfunction after migration?
Some validators, post-functions, or scripted rules from Data Center may not exist in Cloud. Rebuild essential rules using Cloud-native automation tools, then test basic workflow paths to verify proper functionality. For complex automations, consider implementing simpler rule sets that operate within Cloud service parameters.
How much downtime should I anticipate during migration?
Downtime varies based on instance size and migration strategy. Phased migrations can limit downtime to brief windows for each project group. Complete site migrations typically require freezing all changes during the transfer process, which may take hours or days depending on data volume. Always schedule migrations during low-activity periods.
What's the most effective approach for managing user differences between DC and Cloud?
Validate email addresses and domains during pre-migration verification. If you used LDAP/AD in Data Center, consider implementing SCIM provisioning through Atlassian Access for synchronized user management. Watch for duplicate accounts (identical email with different usernames) and previously deactivated users that might reactivate during migration.
Was this helpful?
Thanks!
Viktoriia Golovtseva _TitanApps_
About this author
Senior Content Writer & Marketer
Railsware
2 accepted answers
3 comments