--- title: "Migration from Data Center to cloud" canonical: "https://support.appfire.com/space/APBCFJ/850133325/Migration%20from%20Data%20Center%20to%20cloud" format: markdown --- > Macro (aura-html) This page explains the migration support details for the Power BI Connector app data from the Data Center to the cloud. ## Pre-requisites ### **Data Center** - Ensure you have the latest version of the Power BI Connector* *app* *(*Migration is supported from Power BI Connector, DC version *5.5.0). - Install [Jira Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?hosting=datacenter&tab=overview) on the Data Center instance from which you intend to migrate the Power BI Connector app configurations. For more information, refer to [What is Jira Cloud Migration Assistant?](https://support.atlassian.com/migration/docs/what-is-jira-cloud-migration-assistant/) - The Power BI Connector* *Data Center app supports the integration of [Assets](https://www.atlassian.com/software/jira/service-management/resources/insight-data-center-get-started-guide) (formerly known as Insight), [Projectrak](https://marketplace.atlassian.com/apps/1210816/projectrak-project-tracking-for-jira?hosting=datacenter&tab=overview), and [Tempo Timesheets](https://marketplace.atlassian.com/apps/6572/timesheets-by-tempo-jira-time-tracking?hosting=datacenter&tab=overview). If you are using these integrations and want to migrate data to the cloud, ensure that these applications are installed on the cloud. ### **Cloud** - Install (and configure) the latest version of the Power BI Connector app. - **Use the supported integrations on the cloud after migration: ** If you are using any of the supported integrations in the Data Center and plan to use them on the cloud, then install the required applications on the cloud. - **Assets **(formerly known as Insight): - Assets is Jira Service Management’s native asset and configuration management tool. To use Assets for the Jira Cloud, install the Jira Service Management Cloud Premium or Enterprise. For more information, refer to [Assets in Jira Service Management](https://support.atlassian.com/assets/docs/get-to-know-asset-and-service-management-with-assets/). - Create a new custom field with the name Assets. For more information, refer to [Insight (now Assets) Integration](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/611382968). - Make sure the user who will use the Assets configuration on the Power BI Connector has access to the Jira Service Management. - **Projectrak** **Integration**: To use project fields, install [Projectrak](https://marketplace.atlassian.com/apps/1210816/projectrak-project-tracking-for-jira?hosting=cloud&tab=overview) ( project tracking solution for Jira) on your cloud instance. For more information, refer to [Projectrak Integration](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/621772920). - **Tempo** **Timesheets: **To use Tempo Timesheets, install [Tempo Timesheets](https://marketplace.atlassian.com/apps/6572/timesheets-by-tempo-jira-time-tracking?hosting=cloud&tab=overview) on your cloud instance. For more information, refer to [Tempo Timesheets](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/578453921). --- ## Migration process 1. Before you begin, ensure you have all the required applications installed on the Data Center and cloud. Refer to [Prerequisites](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/850133325/Migration+from+Data+Center+to+cloud#Pre-requisites). 2. Navigate to the **Migration Assistant home** screen: **System **> I**MPORT AND EXPORT **>** Migrate to cloud***.**** ***With the help of Migration Assistant, migrate the global app configurations, users, groups, permissions, and connectors as required. For more information, refer to [this page](https://confluence.atlassian.com/cloud/use-the-jira-cloud-migration-assistant-to-migrate-from-server-to-cloud-993925215.html). > 📝 The Jira Cloud Migration Assistant offers two migration options. We recommend selecting the **Choose what to migrate** option, as it provides you with the flexibility to select exactly what you want to migrate. > 📝 > 📝 ![JCMA migration options, choose what to migrate](media://005c4564-c159-48c6-b211-2659d1045120) 3. Post-migration review: The migration page allows you to view details, monitor the progress of the app migration, and view app migration progress logs.
App migration progress logs You can monitor the progress of the app migration within the migration page. - The **Migration dashboard** lists the saved migrations. - To review your migration details, under **Actions** > select **View details**. - On the details page, you will find a summary of the migration and detailed progress for each project in the migration. - Under the **App migration progress**, click **Actions** (**...**) and select **View logs** to view details about the app migration progress logs. - The log file is a CSV file that is downloaded to your system and displays details about warning messages in the app migration progress. > 📝 - If your migration is incomplete or has failed, you can download the error logs to understand the errors in detail. Refer to [https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/#After-you-run-the-migration](https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/#After-you-run-the-migration) > 📝 - If you are are stuck with the app migration or you encounter multiple warning messages in your app log file, refer to the [App migration progress logs](https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/#App-migration-progress-logs). - If you need further assistance, you can create a [support request](https://appf.re/support) and share the log file and your cloud site URL.
4. Once the migration is complete, review your app on the cloud platform to validate that everything is functioning as expected. > 📝 Once the app migration is complete, allow some time for the app to finish processing the migration on the cloud. --- ## > Macro (anchor) Limitations The below field configurations are not migrated for Connectors. | **Entity** | **Field configurations** **not checked for Connectors after migration** | | --- | --- | | Dates | - Target end - Target start | | Epic | - Epic Color - Epic Status | | Portfolio | Parent Link | | Custom | - Team - ${field.storyPoints} | | Tempo | Account | | Service Desk | - Approvals - Satisfaction | > ℹ️ To configure the fields, edit the migrated Connector in the cloud, select the required fields, and Save the Connector. > ℹ️ > ℹ️ ![Power BI Connector field configurations](media://5b88bcaf-c48c-4f3f-bd24-e75593fc17a1) --- ## Known Issues - The **JQL queries** are migrated as is for Connectors. To update the JQL query to be relevant to the cloud, edit the Connector in the cloud, input the JQL query, and Save the Connector. > 📝 For example: > 📝 > 📝 - The **JQL query **involving custom field IDs** **retain the custom field IDs of the Data Center after migration. For example, the **JQL query** in the cloud shows the custom field ID: `project = KT and cf[10400] is empty.` > 📝 - To update the JQL query custom field ID, edit the Connector in the cloud, input the JQL query in relevance to the cloud, and Save the Connector. - Under **Sprint Metrics,** the Data Center **Board** configuration is not updated for Connectors in the cloud. - To update the **Board** relevant to the cloud, edit the migrated Connector in the cloud, select the Board, and Save the Connector. - **AQL for Insight (Asset) Objects**: The AQL defined for the Insight object in the Data Center is not migrated to the cloud. - To update the query, edit the Connector in the cloud, input the AQL for Insight (Asset) Objects, and Save the Connector. - **Jira Importers custom field - ${field_Story_Points}**: If any of the Data Center Connectors are configured with the custom field **${field_Story_Points}**, then after migration, you will encounter an error for those specific Connectors data extraction. - Resolution (before migration): Before migrating to the cloud, edit the Connector that includes the custom field ${field_Story_Points} configuration in the Data Center, uncheck the custom field ${field_Story_Points}, and Save the Connector. > ℹ️ The field **${field_Story_Points} **is added by JIM when a project is created in the Data Center. [JIRA Importers (JIM) add-on](https://developer.atlassian.com/server/jira/platform/writing-a-custom-importer-using-the-jira-importers-add-on/) enables administrators to import issues from external issue trackers into JIRA. > 📝 We are currently addressing the known issues to ensure migration support in upcoming releases. --- ## Migration use cases Below are a few migration use cases that you may encounter during the migration process. **Use Case 1**: Migration from the Data Center to a cloud instance is attempted single or multiple times. - **Postmigration**: ✅ Single or multiple migration attempts are supported on the same cloud instance, and the Connector data is overwritten. The Connector data is extracted successfully and is functional in the cloud instance. **Use Case 2**: Migration from the Data Center to different cloud instances. - **Postmigration**: ✅ The Power BI Connector app data supports migration to single or multiple cloud instances. ✅ The Connector data is extracted successfully if migration is performed solely on one single Jira cloud instance. :warning: However, when Power BI Connector app data (the next migration or multiple migrations) is migrated from the Data Center to multiple cloud instances, the extraction of Connector data fails on all the Jira cloud instances. 🙂 To resolve this, you need to clean up all the cloud instances for Connector data and retain the data on only one single instance from which you intend to extract the Connector data. > ℹ️ **Recommendation** > ℹ️ > ℹ️ - Since the Connector data extraction fails on multiple cloud instances, it is recommended to limit the migration to a few Jira cloud instances and keep track of all the cloud instances on which you have migrated the app data. This will make it easier to perform the necessary cleanup. - **Resolution**: Postmigration, the Connector data extraction is supported on only one single Jira cloud instance. If you have migrated to multiple cloud instances, refer to the resolution options below. | **Option 1** | **Option 2** | | --- | --- | | - Delete the Connectors on multiple cloud instances and retain the data solely on the specific instance on which you intend to extract the Connector data. Refer to the page [How to transfer ownership and delete connectors](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/919011369).
> ℹ️ **To simplify the process of cleaning the Connector's data across multiple cloud instances**: > ℹ️ > ℹ️ ✅ It is recommended to transfer ownership of the Connectors in the Jira cloud instance after the migration is complete. > ℹ️ > ℹ️ :warning: It is discouraged to transfer ownership during the migration process, as doing so may result in creating duplicate records in the Jira cloud instance. | - [Create a support request](https://appf.re/support) with the Appfire support team and share the below details: - Share all the Jira cloud instance URLs on which you have migrated the Power BI Connector app data. - Also, specify the Jira cloud instance on which you intend to retain and extract the Connector data. - The resolution of this issue will take a minimum of three days. Our team will contact you and set up a production downtime for resolution. | --- ## Post-migration Administration configurations To know how the administration configurations are migrated from the Data Center to the cloud, refer to [Post-migration Administration configurations](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/919273575). --- ## Difference between Data Center and cloud version To know the difference between the Power BI Connector app’s Data Center and cloud version, refer to [Power BI Connector: Data Center and cloud feature comparison](https://appfire.atlassian.net/wiki/spaces/APBCFJ/pages/919306352). --- ## Problem reporting If you experience any unexpected problems or behavior changes, [create a support request](https://appf.re/support). It helps us to identify and prioritize fixes and improvements.