---
title: "Power BI Connector: cloud-to-cloud migration and usage identification"
canonical: "https://support.appfire.com/space/SUPPORT/3488253172/Power%20BI%20Connector%3A%20cloud-to-cloud%20migration%20and%20usage%20identification"
format: markdown
---
This article covers two distinct use cases for the Power BI Connector for Jira during a cloud-to-cloud migration: identifying active app usage across the instance and the process for migrating connector data between two Jira Cloud sites.

## Summary

The Power BI Connector for Jira does not currently support automated cloud-to-cloud migration (for example, via JCMA). This article provides a manual workaround for migrating connector configurations and explains how Jira administrators can identify active connectors and their owners within the instance.

---

## Use case 1: identifying app usage and active connectors

Jira administrators often need to identify which projects or users are actively using the Power BI Connector to prioritize migration efforts.

### Problem

There is no direct backend script or automated report provided by Appfire to list project-specific usage due to privacy and security constraints. Connector configurations are tied to individual users.

### Solution

Jira administrators can manually view all active connectors and their owners through the app's administration settings.

**Steps for Jira admins:**

1. Navigate to **Apps** > **Power BI Connector** > **Administration**.
2. Select **All Connectors**.
3. This view displays all active connectors configured in the instance and identifies the users (owners) associated with them.

---

## Use case 2: cloud-to-cloud data migration

When moving from one Jira Cloud instance to another, connector configurations (data sources, JQL filters, field selections) must be migrated.

### Problem

Appfire does not currently support automated migration of connector configurations between Jira Cloud instances. Connectors must be manually rebuilt on the target site.

### Solution (manual workaround)

To migrate data, administrators or connector owners must document existing configurations and recreate them in the new instance.

#### Step 1: document existing configurations

Because administrators cannot see the JQL of connectors they do not own, they must temporarily take ownership or have the owners provide the details.

1. Go to **All Connectors** in the source site.
2. For each connector:
  - Note the **Actual Owner**.
  - Perform **Transfer Ownership** to yourself (Jira admin).
  - View and document the **JQL Filters**, **Selected Projects**, **Fields**, and **Permissions**.
  - Revert ownership to the original owner.

#### Step 2: install the app on the target instance

1. On the destination Jira Cloud site, go to **Apps** > **Find new apps**.
2. Search for **Power BI Connector for Jira by Appfire** and install it.

#### Step 3: recreate connectors

1. Open the app in the destination Jira instance.
2. Manually create each connector using the details documented in Step 1.
3. **Note:** This will generate new **Data Source URLs**.

#### Step 4: update Power BI reports

1. Open your `.pbix` files in **Power BI Desktop**.
2. Go to **Transform Data** > **Advanced Editor**.
3. Replace the old **Data Source URLs** with the new URLs generated in Step 3.
4. Re-authenticate using your email and a new API Token if prompted.

#### Step 5: republish

1. Verify the data in Power BI Desktop.
2. Republish the report to the **Power BI Service**.
3. Re-configure any scheduled refreshes with the new credentials.