Assess your instance scale using Jira Cloud Migration Assistant: Database queries and usage metrics

Assess the scale of your Jira and Confluence instances

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

You can assess the cloud readiness of your Jira Data Center instance by collecting data about its content, such as the number of users, projects, custom fields, and many more.

How it works

The cloud readiness of your Data Center instance will be assessed by comparing your data with Atlassian guardrails relevant for migrations or your future setup in cloud.

How you’ll collect, share, and view your data can be done in one of the following ways:


OPTION 1 Using Portfolio insights RECOMMENDED

You’ll use Portfolio insights to connect to Data Center and collect the data (with a fallback manual collection possible). Your cloud readiness report will be generated instantly.

Your raw data will be available to Atlassian migration teams who can provide additional information, if needed.





OPTION 2 Sharing raw data with Atlassian

You’ll run the assessment from the migration assistant and attach results to your MOVE ticket. Migration teams will prepare a cloud readiness report and share it with you. Use this option only when recommended by Atlassian migration teams.

(info) Use for Atlassian Government Cloud migrations.

Collected data

In both options, the report is prepared based on the data collected through the migration assistant. Here’s a summary of what we collect:

  • Jira entities: Number, or metadata, of entities, such as projects or issues

  • Usage data: for example the number of active users in the past days

  • Instance metadata: products installed, details about the database, Data Center nodes, and some metadata related to your instance, such as Server ID or timezone

  • Browser metrics: performance and browser metrics, including network speed and quality, based on users' browser

  • Apps: number and size of entities that might affect the migration, for the most critical apps

Once collected, the data is saved in a ZIP archive and either transferred or uploaded to Portfolio insights or attached by you to your MOVE migration ticket.

For more details, see What data is collected

Not all collected data is analyzed and used in your report.

How we use the data

We’ll only collect and use the metadata about your Jira instance. This metadata doesn’t contain any Personally Identifiable Information (PII) or user-generated content (UGC). It’s based only on IDs.

This will help us better understand your data complexity and cloud performance needs, and will allow us to craft a migration strategy and plan that mitigates risk and sets you up for success. Additionally, the metadata collected will help us continually improve our products and tooling.

FAQs

Here are some common questions.

Do you collect any identifiable data?

The assessment doesn’t collect any personal identifiable data (PII). Any data that we collect is based on IDs.

Do I need Internet connection? Do you call APIs outside of my network?

The Internet connection is required for Option 1: Portfolio insights when you connect to your Data Center instance and automatically transfer the data to Portfolio insights.

If you have an air-gapped environment, you can fallback to manual collection and upload.

We’re also not calling any APIs outside of your instance’s network.

Do I need to run the assessment on the production instance or is the testing one enough?

 We recommend that you run the assessment on your production instance, because it improves accuracy of our recommendations. We understand that’s not always possible, so here’s a more detailed explanation so you can decide.

Data shape

When it comes to data shape, which is – for example – the number of projects, users, configuration items, entities exceeding the guardrails, and so on, the testing instance should be sufficient. Even if it's behind the production instance by a month, the data shape will be relatively similar, so we'll be able to assess it accurately. The production instance is still better, but the testing one should be enough.

Performance: Traffic, usage, and instance metadata

Apart from just data, we also assess the traffic and usage of your instance, based on the data from your users' browsers. We also collect instance metadata, which is – for example – hardware details or network speed. All of these metrics can affect performance and we use it to determine whether your target cloud site is sufficient for your needs. If it’s not, we might recommend splitting your instance into multiple sites in cloud.

Assessing your testing instance won’t give accurate (or any) results on traffic, usage, and instance metadata, which are important factors.

Do I need to run the assessment on each Data Center node separately?

No, the assessment collects the data from the entire Data Center instance, and you don't need to run it separately on each node.

You also can't choose a specific node to run it on. 

What's the performance impact on the Data Center instance?

We did performance testing and optimizations to make sure the assessment doesn’t affect your instance. When it’s running, your users can keep doing their work in Jira.

What's the user key / ID collected from the user's browsers?

When collecting data from your users' browsers, we collect the user key associated with every user. These keys are hashed on export and never exposed to Atlassian teams. We only use them for grouping, clustering, and creating themes for research and analysis.

Before you begin

Here are some prerequisites:

  • We add new data points on a regular basis. To get the most accurate results, update Jira Cloud Migration Assistant to the latest version.

  • The assessment duration depends on your data. On average it takes up to a few hours, but should be much faster for less complex instances.

OPTION 1 

Using Portfolio insights RECOMMENDED

In this option, you’ll connect to your Data Center instance from Portfolio insights to collect the results, and then view your cloud readiness report.

1. Go to Portfolio insights

You can access Portfolio insights by going to admin.atlassian.com, and selecting Settings > Portfolio insights. Check the following page for detailed instructions.

Get started with Portfolio insights

2. Connect to your Data Center instance

To connect to a Data Center instance, you’ll need to meet some requirements like installing the Cloud Companion app and allowlisting the https://api.atlassian.com domain.

How to connect to Data Center instances

3. (Fallback) Manually collect and upload data

If you’re unable to connect to your Data Center instance, you can manually run the assessment and upload the results to Portfolio insights.

How to manually collect and upload data

4. View your cloud readiness report

Once the data is collected and transferred/uploaded to Portfolio insights, you’ll be able to view your cloud readiness report, with insights into your data and recommendations on how to fix or improve it.

How to view your cloud readiness report

OPTION 2

Sharing raw data with Atlassian

In this option, you’ll manually run the assessment from the migration assistant. When it’s ready, you’ll download a ZIP archive and share it with Atlassian by attaching it to your MOVE ticket.

1. Run the assessment from the migration assistant

1. Enable the assessment

If you updated your migration assistant to the latest version, the assessment will already be enabled so you can skip this step. We're leaving this flag for users on earlier versions.

To enable the assessment:

  1. Go to <Jira_URL>/secure/admin/SiteDarkFeatures!default.jspa

  2. Add the following flag: 

    com.atlassian.jira.migration.features.assess-l1-cloud-tooling

If you need more details, see Enabling dark features in Jira.

2. Run the assessment in your migration assistant

To run the assessment and collect the data:

  1. Open the Jira Cloud Migration Assistant.

  2. In the Assess your instance card on the home screen, select Begin assessing.

  3. We’ll ask you to confirm that the data will be stored on your instance. Select Continue.

  4. The assessment will start.

2. Download and share results with Atlassian

1. Download the ZIP archive

Once the assessment is complete, select Download report in the same Assess your instance card.

2. Share the results with Atlassian

Share the results with Atlassian:

  • You can attach the results to a MOVE ticket or Support request that pointed you at this page.
  • For Atlassian Government Cloud migrations, share the results over email with your Atlassian point of contact.

We will review the output results to better understand the complexity, data shape, performance needs, and risks. These will help inform the creation of your Migration Strategy and Plan.

What data is collected

Details of files included in the ZIP archive and examples of collected data points.

File

Description

jira-entities-[date].csv

Data about specific entities, retrieved from the database. It helps us understand the scale of your instance.

jira-usage-metrics-[date].csv

Usage metrics taken from access logs. It helps the Jira Cloud teams determine the best cloud instances for you.

jira-instance-metadata-[date].jsonl

Details about your instance, including products, infrastructure, database, Data Center nodes, and some metadata for easier identification.

jira-browser-metrics-[date].jsonl

Data from users' browsers on the performance of your instance. It helps us understand what you’ll need in cloud for best performance.

Apps subdirectory

Data about entities that might affect the migration, for the most critical apps. If you have these apps, each will have a separate file inside.

cloud-database-queries-[date].csv

(Deprecated) This file includes data about specific entities, similarly to jira-entities-[date].csv file. We've used it before we merged all entities into a single file. This file will be removed in one of the upcoming versions.

Details of metrics included in the files

More details about the data points and metrics included in the files.

File: jira-entities-[date].csv

This file includes the following metrics:

Users and groups
  • Total number of users
  • Number of active users
  • Number of inactive users
  • Number of users deleted from an external directory
  • Total number of agents
  • Number of active agents
  • Total number of customers
  • Total number of groups
  • Metadata of groups with 35k or more members
  • Average and max number of members in a group
  • Average and max number of groups users have
  • Max number of groups associated with a user
  • Number of users with a unique username
Attachments
  • Total number of attachments
  • Size of all attachments in GB
  • Max number of attachments in an issue
Projects and issues
  • Total number of projects
  • Number of projects by type
  • Number of active projects
  • Total number of issues
  • Total number of issue types
  • Total number of comments
  • Number of project roles by type for example assigned to users or groups
  • Number of project roles with deactivated users
  • Number of projects with 80k or more issues
  • Total number of labels
  • Number of calendars per project
  • Max number of child issues in an issue
  • Number of time metrics by project
  • Total number of entity properties which are additional data stored in Jira entities such as issues or projects
  • Number of entity properties by entity type such as issue or project
  • Metadata of issues with 10k or more history groups
  • Metadata of projects with 10k or more history groups
  • Total number of history items which are individual changes made to issues
  • Total number of history groups which group multiple changes made to an issue in a single edit
Service projects
  • Total number of queues in service projects
  • Total number of request types in service projects
  • Number of service projects with 50 or more queues
  • Number of queues in top 10 projects with the most queues
  • Number of SLAs per each service project
  • Number of projects with 30 or more SLAs
  • Metadata of projects with 30 or more SLAs
  • Metadata of projects with 90 or more SLAs
  • Number of requests created per channel for example through email or customer portal
Workflows
  • Total number of workflow schemes
Custom fields
  • Total number of custom fields
  • Max number of options in a custom field
  • Total number of custom field values
  • Total number of custom field options
Assets
  • Total number of assets
  • Total number of asset schemas
  • Number of Assets custom fields linked to 20 or more assets
Automation

These entities refer to the legacy automation from Jira Service Management.

  • Total number of automation rules
  • Total number of automation rule executions per day
  • Metadata of automation rules with 30 or more branches
  • Number of automation rules with 30 or more branches
  • Number of projects with 30 or more automation rules
  • Metadata of projects with 30 or more automation rules
Audit and logging tables

For these entries, we're mostly interested in the size of tables, rather than the number of specific items. If the tables are too big, they can slow down or block the migration.

  • Total number of incoming emails received by Jira
  • Number of logs for fetching emails from the database
  • Number of logs for processing emails
  • Total number of execution logs for all automation rules
  • Number of execution logs. Rules with IF/COND statements
  • Number of execution logs. Rules with IF statements
  • Number of execution logs. Rules with IF/THEN statements
  • Number of execution logs. Rules with THEN statements
  • Number of execution logs. Rules with THEN/ACT statements

File: jira-usage-metrics-[date].csv

  • Interactions date: Date when an interaction with the Jira instance was recorded in the access logs.

  • Active users per day: Total number of unique users who interacted with the Jira instance in the past 14 days.

  • Peak-hour active users per day: Number of unique users who interacted with the Jira instance at the same time. We obtain it by aggregating user IDs and the corresponding date-hour combinations in the access logs. It provides a snapshot of your instance’s busiest periods.

  • Node availability and data collection status: Data on the availability of each node (or single node). It also shows the status of data collection.

File: jira-instance-metadata-[date].jsonl

  • Products: Name, version, and SEN number of products installed on your instance.

  • Infrastructure: Details about the database, Data Center nodes, and Java heap size.
  • Instance metadata: Some metadata, including assistant version, Server ID, instance UUID, and timezone.

File: jira-browser-metrics-[date].jsonl

  • user ID: A unique identifier of a user. It’s generated securely and hashed randomly to maintain privacy, while also allowing us to track user interactions.

  • Browser type and version: Details about the browser, for example Google Chrome, Safari.

  • Operating system: Details about the operating system, for example Windows, MacOS.

  • Processor count: Number of processors on the device.

  • System memory (RAM): Total memory or RAM on the device.

  • Network download speed: The speed of downloading data.

  • Network connection quality: The effectiveness of network connection.

  • Network Latency (RTT): Round Trip Time (RTT) is a measurement of the time it takes for a signal to travel from a user's computer to the Jira Instance and back. This helps gauge the responsiveness of users' network connection.

File: cloud-scale-database-[date].csv

This file has been deprecated and will be removed in one of the upcoming versions. It includes data about some entities that you can also find in the jira-entities-[date].csv file. 

Apps subdirectory

This subdirectory contains files with entities for the most critical apps. 

File: user-installed-apps-[date].jsonl 

File: zephyr-squad-[date].jsonl

File: xray-[date].jsonl

File: scriptrunner-for-jira-[date].jsonl

File: jira-misc-custom-fields-[date].jsonl

File: jsu-automation-suite-[date].jsonl

Last modified on Oct 22, 2025

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.