--- title: "Jira Migration" canonical: "https://support.55degrees.se/space/SP/4406018090/Jira%20Migration" format: markdown --- [jira cloud & data center] > Macro (refined-tabs) > > > Macro (refined-tab) > > If you’re migrating data from one Jira Instance to another, you’re more than likely wondering if your marketplace apps are compatible and how the move will impact them - and if you’re reading this - you’re wondering about ActionableAgile® analytics for Jira specifically. > > > ℹ️ When migrating, make sure to migrate the data in such a way that the historical data is intact. The CSV Importer in Jira does *not* migrate historical data for example. > > ℹ️ > > ℹ️ The Jira Cloud Migration Assistant *does* migrate Issue History as documented in [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. > > #### What Data Migrates? > > - **Jira Data** > - ActionableAgile® Analytics does **not** store your Jira Data, so there’s no data to migrate from the tool. > - **Saved Data Sets** > - The configurations for your ActionableAgile® Analytics Saved Data Sets (shared or personal) and Views are stored in your Local Storage and can be migrated with our Migration Tool. > > > ℹ️ If - when migrating - the Jira ID’s for your Spaces, Filters, Boards or Work Items changes, you’ll need to delete your Saved Data Sets and Views and recreate them as the configuration to load them will be outdated. > > #### User Impact > > Users will need to review how their Saved Data Sets and Views have migrated. > > #### Version Difference > > - Similarities > - We have endeavoured to make ActionableAgile® Analytics for Jira Cloud and Data Center as similar in functionality and interface as possible. > - All charts, insights, and calculations are available across the Data Center and Cloud versions. > - Differences > - Faster access to new features. Cloud gets updates first and more often, without the need for manual upgrade by a Jira Admin. > - For non-user-facing aspects, there may be some differences between the platform. For example, in Jira Cloud, the number of search threads is hardcoded though it is configurable in Jira Data Center. > - Features that are already available on Cloud: > - Jira Dashboard Gadgets (will not be released to Data Center). > - Landing page - a new starting point for exploring your data, answer key questions, and making your workflow smoother. > - Dataset Views - allowing you to save and share your various dataset configurations. > > #### Licensing > > 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) > > > ℹ️ For the actual migration steps from Jira Data Center to 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) > > 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. > > > ℹ️ 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. > > **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. > > > Macro (refined-tab) > > [jira Data Center → cloud] [version 5.8.0+] > > Our Migration Log is an automated migration path which is part of Jira Cloud’s Migration Assistant - it is enabled when you mark ActionableAgile® Analytics app as [needed in cloud] in the *Assess Your Apps* section of JCMA’s migration process. > > ![Screenshot 2026-07-29 at 09.36.49.png](media://34aac031-8896-4b20-b0fa-24094f3290d9) > > Via the [actions] menu, you’ll have the option to **Cancel**, **Re-Run** or **View Logs**. > > ![image-20260302-093656.png](media://4c01ebb2-c88d-4988-b614-341f6ba8b4c7) > > ### View Logs > > The Migration Log is the central place to review results from your ActionableAgile® Analytics data migration from Jira Data Center To Jira Cloud. It presents each migrated data set with clear status, ownership, and actions so you can quickly verify outcomes and take follow-up steps. > > > ℹ️ At a glance, you can: > > ℹ️ > > ℹ️ - Scan overall migration outcomes. > > ℹ️ - Review each data set’s status, type (shared or personal), owner, and reason (if a problem occurred). > > ℹ️ - If a problem occurred, retry the data sets migration or delete it. > > #### Migration Table > > | Column | What you’ll see | > | --- | --- | > | Dataset Name | Name of the migrated data set. | > | Dataset ID | Identifier of the data set. | > | Type | Shared or Single User. | > | Owner | Who owns the data set. | > | Status | [sent] [not sent] | > | Reason | If not successful, reasoning as to why. | > | Action | Reload 🔄 | > > #### Actions You Can Take > > **Reload a Data Set** > > Use the reload action to re-run a migration for the selected data set—ideal after fixing a configuration issue or permissions. > > - Click the reload icon in the Action column for the target row. > - A loading spinner appears during processing; actions are temporarily disabled to prevent duplicate requests. > > #### Best Practices > > - Before reloading, address any permission or configuration issues that caused failures. > - Use Dataset ID when contacting support for faster triage. > > #### FAQ > > - **Why would I retry a data set with the status Sent? **It may be that the data set was successfully sent, but when you check the data set in Cloud, something could be amiss and you may wish to retry the migration.