Assess your instance scale using Confluence 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 Confluence Data Center instance by collecting data about its content, such as the number of users, spaces, pages, attachments, 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.

Note: Use this option only when recommended by Atlassian migration teams.

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:

  • Confluence entities: Number, or metadata, of entities, such as spaces or pages

  • 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

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 Confluence 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 spaces, 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 Confluence.

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 Confluence 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 <Confluence-url>/admin/darkfeatures.action

  2. Add the following flag: 

    migration-assistant.enable.assess-l1-cloud-tooling.feature

For details, see Enabling dark features in Confluence.

2. Run the assessment in your migration assistant

To run the assessment and collect the data:

  1. Open the Confluence 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'll most likely do it by attaching it to a MOVE ticket or Support request that pointed you at this page.

We will review the output results to better understand the complexity, data shape, performance needs, and risks, if any. 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. 

FileDescription
confluence-entities-[date].csvData about specific entities, retrieved from the database. It helps us understand the scale of your instance and determine the best migration strategy.
confluence-macros-[date].jsonl

Data about Confluence macros, including information on:

  • Macros that don't exist in cloud, and are therefore incompatible
  • Macros whose equivalents exist in cloud, but have some differences in functionality
  • Nested-body macros that will be broken after migration

We don't collect data on all macros from your instance. We include specific types of macros not available in cloud or different from their cloud equivalents, and specific sequences of nested-body macros. For details, see the sections below.

When you send the assessment file to Atlassian, we won’t be able to analyze macros. We’re only sharing this data in the file to give you more info on the incompatible macros we found.


confluence-browser-metrics-[date].jsonlData from users' browsers on the performance of your instance. It helps us understand what you’ll need in cloud for best performance.
confluence-usage-metrics-[date].csvUsage metrics taken from access logs. It helps the Confluence Cloud teams determine the best cloud instances for you.
confluence-traffic-distribution-[date].csv

Distribution of traffic (%) on different actions done by your users, for example viewing pages or adding comments. It can help you find some unusual traffic.

Details of metrics included in the files

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

File: confluence-entities-[date].csv

The file includes data about Confluence entities, for example:

  • Spaces and pages
  • Users and groups
  • Attachments and media
  • Database tables

You can find more details on exact metrics below.

What kind of entities are collected

  • Total number of users

  • Number of users with a unique username

  • Number of active users

  • Number of inactive users

  • Number of user groups

  • Total number of spaces by status

  • Number of attachments per each of top 100 spaces with most attachments

  • Total attachments size in GB

  • Metadata of groups with 35k or more user memberships

  • Number of active user groups

  • Number of attachments in each of the top 100 pages with most attachments

  • Number of attachments per space

  • Maximum number of comments in a page

  • Number of pages per each of top 100 spaces with most pages

  • Maximum number of pages in a space

  • Number of pages with restrictions

  • Maximum number of restrictions in a page

  • Maximum number of likes in a page

  • Maximum number of space permissions in a page

  • Maximum number of space group permissions in a space

  • Number of pages per version

  • Number of pages per status

  • Number of Jira Issue Macros in each of top 10k pages with most Jira Issue Macros

  • List of installed apps

  • Number of media in each of the top 50 pages with most media

  • Size of the biggest 10 non-personal spaces in GB

  • Metadata of spaces modified in last 180 days

  • Number of groups per each of top 100 users with most groups

  • Number of embedded attachments per each of the top 100 pages with most embedded attachments

  • Number of current attachments per each of the top 100 pages with most current attachments

  • Maximum number of space user permissions

  • Database tables size in GB

  • Database size in GB

  • Media size in GB

  • Number of tables per each of the top 50 pages with most tables

  • Number of pages per page status

  • Total attachments size in GB

  • Tables size in GB per each of the top 50 pages with most tables

  • Metadata of personal spaces of inactive users

  • Maximum number of child pages in a page

  • Maximum depth of child pages in a page

  • Number of table cells per each of the top 50 pages with most table cells

  • Metadata of the top 10 non-personal spaces with the largest data size

  • Metadata of the personal space with the largest data size

File: confluence-macros-[date].jsonl

The file includes information about macros that won't be fully compatible after the migration. It doesn't include all macros from your instance – we only collect specific types and sequences that we know are incompatible with cloud.

The macros in the file are divided into spaces where they appear, and include the following main types:

TypeDetails
Different macros

Macros whose equivalents exist in cloud, but have some differences in functionality.

Collected macros: viewxls, viewppt, change-history, contentbylabel, code

Not available macros

Macros that don't exist in cloud and won't work after the migration.

Collected macros: html, html-include, rss

Nested macros

Macros that are nested inside other macros.

We collect a high number of sequences (for example, divbox > section > divbox > text-data) that we know aren't supported in cloud, but not all possible sequences. 

We don't support all macros or nested-body macros because collecting and analyzing every possible case could have performance impact on your instance and make the assessment package too large.

When you send the assessment file to Atlassian, we won’t be able to analyze macros. We’re only sharing this data in the file to give you more info on the incompatible macros we found, so you can review them.

File: confluence-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 Confluence Instance and back. This helps gauge the responsiveness of users' network connection.

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

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

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

  • Peak-hour active users per day: Number of unique users who interacted with the Confluence 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: confluence-traffic-distribution-[date].csv

The file includes the % distribution of traffic on different actions performed by users. Here's the list of actions:

  • Viewing a page
  • Editing a page
  • Adding a comment
  • Adding and resolving inline comment
  • Using quick search
  • Using advanced search
  • Liking a page or a comment
  • Publishing a page
  • Creating a draft
  • Viewing home page
  • Viewing page history
  • Viewing a blog
  • Adding labels
  • Toggling (enabling or disabling) space permissions for a group
  • Using CQL (Confluence Query Language) to search by username
  • Using CQL to search by random page ID
  • Using CQL to search by page title
Last modified on Jun 26, 2025

Was this helpful?

Yes
No
Provide feedback about this article

Related content

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