--- title: "Migration Guide" canonical: "https://support.55degrees.se/space/SP/4236083232/Migration%20Guide" format: markdown --- [Jira cloud & Data Center] > ℹ️ ### Data Center End of Life > ℹ️ > ℹ️ Atlassian has announced the end-of-life for Jira Data Center. While this means change is on the horizon, you can count on 55 Degrees to support you every step of the way. > ℹ️ > ℹ️ This guide is designed to help you plan and execute a smooth migration to Jira Cloud, ensuring you continue to get the most from ActionableAgile® Analytics - now and in the future. > ℹ️ > ℹ️ **Our commitment:** > ℹ️ > ℹ️ - We’ll support Data Center customers with active ActionableAgile Analytics licenses until Atlassian’s official end date - March 28, 2029. > ℹ️ - We’ll help you unlock even more value on Cloud, where new features arrive first. > Macro (refined-tabs) > > > Macro (refined-tab) > > ### Background > > If you and your team are moving from **Jira Data Center **→** Jira Cloud**, you’re more than likely wondering if your marketplace apps are compatible and how the move will impact them. > > ### What Remains? > > **Core Functionality**: All charts, insights, and calculations are available across DC and Cloud. > > ### What’s Better on Cloud? > > - *Faster* access to new features. Cloud gets updates first and more often, mostly without the need for manual upgrade by a Jira Admin. > - Reduced risk: no need to plan for DC’s phase-out. > - Features that are already available on Cloud: > - **Jira Dashboard Gadgets** (will *not* be released to Jira Data Center). > - **Landing Page **- a new starting point for exploring your data, answer key questions, and making your workflow smoother. > - **Views** - allows you to save and share your various data set configurations. > > > ℹ️ Read more about the features here: Links > > ### What’s the Impact on Users? > > Since we don’t store your data, you and your team will need to set up your preferred datasets again when you move to Jira Cloud. **Thus, your datasets will not be available to users until they are recreated.** > > ### Do I Need a New License? > > Yes, you will need a new license if you’re moving to Jira Cloud since the Atlassian Marketplace treats the licenses differently. For more details, please visit [https://www.atlassian.com/licensing/marketplace#general-faqs](https://www.atlassian.com/licensing/marketplace#general-faqs). > > > > Macro (refined-tab) > > ### What Data Will Migrate? > > > ℹ️ [Coming soon] > > ℹ️ > > ℹ️ We are working on implementing **fully automated app data migration**, which will include the migration of your: > > ℹ️ > > ℹ️ - Shared Data Sets > > ℹ️ - Personal Data Sets > > ℹ️ - Views > > ℹ️ > > ℹ️ When this feature is released, you’ll no longer need to recreate any datasets. > > ℹ️ > > ℹ️ 🚀 Read more about our Migration tool here: [https://support.55degrees.se/space/SP/4236083232](https://support.55degrees.se/space/SP/4236083232) > > ***For now though…***** **You and your team will need to **recreate shared datasets** (and review any migrated personal datasets) once you are on Jira Cloud. > > ActionableAgile® Analytics for Jira does *not* copy or store your Jira data outside of Jira. It reads information from your Jira instance and then stores your personal (non‑shared) datasets and settings as user properties in Jira. > > When you migrate from Jira Data Center → Jira Cloud using Atlassian’s migration tooling: > > - **Personal (non‑shared) datasets** *are* migrated with your user account, because they live in Jira user properties. > - However, after migration, some of these datasets may not work as expected because the underlying **Space IDs, Board IDs, Filters, and Custom Fields may change or not be mapped one‑to‑one**. > - **Shared datasets are *****not***** migrated **because they are tied to specific Spaces, Boards, Filers, and users in the original Jira instance. The migration does not reliably remap all of those references to the new Cloud instance, so we cannot safely migrate shared datasets. > > > ℹ️ #### More on why shared datasets are not migrated > > ℹ️ > > ℹ️ Jira’s migration tools move your Jira data, but they don’t guarantee a clean one‑to‑one mapping for everything that ActionableAgile Analytics relies on. > > ℹ️ > > ℹ️ When you move from Data Center to Cloud, things like: > > ℹ️ > > ℹ️ - **Space IDs and keys** > > ℹ️ - **Board IDs and filters** > > ℹ️ - **Custom field IDs** > > ℹ️ - **User IDs** > > ℹ️ > > ℹ️ …may change or not be mapped exactly the same way. > > ℹ️ > > ℹ️ Shared datasets reference these IDs directly. After migration, those references often no longer match anything in the new Cloud instance, which can cause datasets to fail to load or behave unpredictably. > > ℹ️ > > ℹ️ To avoid broken or confusing configurations, we **do not migrate shared datasets**. Instead, we recommend noting down the configuration of important shared datasets before migration and recreating them in Cloud. > > > ℹ️ If you are concerned about specific datasets that are critical to your reporting, please reach out to us via [support@55degrees.se](mailto:support@55degrees.se) before you migrate so we can help you plan. > > > > Macro (refined-tab) > > ### Prepping for Migration > > Review your current use of ActionableAgile® Analytics on Jira Data Center. > > > ℹ️ Your shared datasets will not migrate > > If you have shared datasets, note down their configuration so that you can recreate them once the migration to Cloud is complete. > > ### The Migration > > > ℹ️ For the actual migration from Jira Data Center → Jira Cloud, we refer to Atlassian's guide: > > ℹ️ [https://www.atlassian.com/migration/plan/cloud-guide#introduction](https://www.atlassian.com/migration/plan/cloud-guide#introduction) > > > ℹ️ When you migrate your Jira item data - make sure to migrate the data in such a way that the historical data is migrated as well. The CSV importer in Jira does not migrate historical data for example. > > ℹ️ > > ℹ️ The Jira Cloud Migration Assistant does migrate Issue History as documented at [https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html](https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html). Without the historical data - ActionableAgile® Analytics for Jira will not be able to identify the status history. > > #### **Step-By-Step Guide** > > #### **1. Assess** > > - Review your current use of ActionableAgile® Analytics on Jira Data Center. > - Identify key datasets and saved configurations. > > #### **2. Plan** > > - Map out which features you rely on most. > - Check the FAQ for features that may differ between DC and Cloud. > > #### **3. Trial Run** > > - Install ActionableAgile® Analytics for Jira Cloud in a test site. > - Import sample data and validate key reports. > > #### **4. Prepare Data** > > - Work with your Jira admins to plan the DC → Cloud migration of Jira itself. > - Document how ActionableAgile® Analytics datasets will be recreated in Cloud. > > #### **5. Migrate** > > - Execute the Jira migration. > - Recreate datasets and saved views in ActionableAgile® Analytics for Cloud. > > #### **6. Review & Validate** > > - Compare charts and insights between old DC reports and new Cloud reports. Confirm accuracy. > > #### **7. Train & Adopt** > > - Introduce users to any new features available in Cloud. Provide quick guides or training sessions.