How to migrate eazyBI from Atlassian Data Center to Atlassian Cloud

Kārlis Visendorfs

February 5, 2026

How to Migrate eazyBI from Atlassian Data Center to Cloud

If you're preparing to migrate your Jira instance from Atlassian Data Center to Cloud, you're likely thinking about how your eazyBI reports and dashboards will make the journey. The good news: this doesn't have to be complicated.

eazyBI for Data Center and eazyBI for Jira Cloud are the same core application. There are no major functional differences. This isn't a rebuild or a reimplementation — it's a metadata transfer that typically completes in seconds to minutes.

This guide walks you through the entire process: what to prepare, how the migration works, and what to check afterward. Whether you're a Jira administrator handling the migration yourself or a solution partner supporting a client, you'll find everything you need here.

What Gets Migrated (And What Doesn't)

Before you begin, it's important to understand what the migration process actually transfers.

What IS migrated
Reporting metadata, like:

eazyBI accounts
User permissions and roles
Report definitions
Dashboard definitions
Advanced settings (custom configurations)

What is NOT migrated

Report data (the actual data behind your reports)

This is intentional. The migration transfers only metadata — the structure and definitions of your analytics setup. The actual report data must be re-imported from your Jira Cloud instance after migration.

Why? Because your Jira data has already been migrated to the Cloud. Once eazyBI for Jira Cloud is set up, it imports directly from Jira Cloud. This keeps the migration fast and ensures your reports reflect the data that's actually in your Cloud instance.

Before You Begin: Prerequisites & Preparation

Most migration issues trace back to ignored preparation. With the right prep, the migration is pretty painless.

Prerequisites

Start by updating eazyBI for Data Center to the latest version — the Database Migrator requires version compatibility with Jira Cloud.

Your Jira instance should already be in the cloud before you start migrating eazyBI. If your reports use data from third-party apps like Xray or Zephyr, install those in Jira Cloud first. The same goes for eazyBI itself — install eazyBI for Jira Cloud on your Cloud instance.

Leave eazyBI advanced settings empty – the migration will bring them over from Data Center. If anything is already added, the Data Center settings won’t be migrated and will need to be copied manually.

Finally, check your network. Your Data Center server needs outbound access to both your Atlassian Cloud URL and eazybi.com. If your network restricts outbound connections, check the eazyBI documentation for the list of IP addresses that need to be allowed.

Preparation

Based on our best practices, we suggest taking these preparation steps to avoid potential issues during the migration—better safe than sorry.

Back up your eazyBI database using your standard database backup tool — and test that backup. The ZIP file created by the Database Migrator is a migration package, not a backup. Don't confuse the two.

Document your custom field mappings. Custom field IDs often change during Jira migration. Record your current field IDs and names so you can update references later if needed.

Clean up first. Unused fields, abandoned accounts, and orphaned reports don't need to make the trip. Less content means fewer warnings to review and a cleaner starting point in Jira Cloud.

Make a list of your dashboard gadgets. eazyBI gadgets in Jira and Confluence dashboards must be re-added manually after migration. Document what exists now so you don't forget any.

Run a test migration. Migrate to a test Cloud environment before touching production. This reveals any issues while you still have time to address them — and it's far less stressful than discovering problems in production.

The Migration Process: Step by Step

With preparation complete, the actual migration is straightforward.

Step 1: Open the Database Migrator

In eazyBI for Data Center, navigate to Settings → Database Migrator

Step 2: Select Migration Type

Choose "From server to cloud" as your migration type.

Step 3: Enter Cloud Connection Details

You'll need three pieces of information:

Cloud Site URL — Your Atlassian Cloud instance URL (e.g., yourcompany.atlassian.net)
User Email — An admin account email that exists in Cloud
API Token — Generate this from your Atlassian account

To create an API token:

In Cloud, go to your profile → Account Settings → Security
Click "API Tokens" → "Create API Token"
Give it a name and set an expiration date
Copy the token and paste it into the migration form

Step 4: Select Accounts to Migrate

Choose which eazyBI accounts to migrate. You can select all accounts or specific ones.

Important: If you use template accounts, migrate them together with all associated child accounts; otherwise, the relationships between template and child accounts will be lost and will need to be restored manually after the migration.

Step 5: Click "Migrate"

Click the Migrate button and wait for completion. Since only metadata is transferred, this typically takes seconds to minutes — not hours.

Your Post-Migration Checklist

The migration itself is the easy part. Now comes the work of verifying everything landed correctly and reconnecting your data sources. Work through this checklist systematically:

Review migration warnings — Check for any warnings about users, fields, or accounts that weren't found. These are informational — they don't block migration, but they tell you what needs attention.

Verify advanced settings transferred — Check that your custom settings from Data Center appear in eazyBI for Jira Cloud.

Reset authorization if needed — If your Cloud user email differs from your Data Center user email, you'll see a permission error when trying to import. Fix this by going to Source Data → Reset Authorization → Assign to current user.

Import data into each account — Go to each account → Source Data → Import. This imports data from Jira Cloud. The first import will take longer than a regular import, as it is a full import.

Update custom field IDs in advanced settings — If any custom field IDs changed during Jira migration, update the references in your advanced settings and calculated fields.

Review source application import options — Verify that import settings are correct for the Cloud environment.

Re-add Jira dashboard gadgets — eazyBI report gadgets in Jira dashboards must be re-added manually. Go to your dashboards, add an eazyBI Report gadget, and configure it to display your report.

Re-add Confluence gadgets — Similarly, recreate any eazyBI gadgets in Confluence pages.

Check REST API data sources — If you import from REST API endpoints, ensure they're publicly accessible from Cloud. Update authorization if needed.

Check SQL data sources — Internal SQL databases may not be accessible from Cloud. Consider migrating them to a cloud-accessible location (Azure, AWS, etc.).

Test reports and dashboards — Compare your Cloud reports with the Data Center to verify data accuracy.

Troubleshooting: Common Issues and Solutions

Even with good preparation, you may encounter some issues. Here's what we see most often and how to resolve them.

Issue	Cause	Solution
Custom field IDs changed	Jira migration changes field IDs	The migrator automatically identifies fields by name AND type. If both match, the ID updates automatically. If a field can't be matched (e.g., name or type changed), manually update the ID in the advanced settings and calculated fields.
User permission errors	Different email addresses between DC and Cloud	Users are matched by email. If emails differ, use Reset Authorization to assign to the current Cloud user.
User keys changed	Jira migration may change user keys	If user keys change during Jira migration, historical data (such as issue assignee history) may not be correctly matched. Verify historical reports after migration.
Field type mismatches	Field types changed during Jira migration	Some fields may change type (integer → text). Re-select the field in import options and reconfigure if needed.
SQL/REST sources are inaccessible	Internal sources not reachable from Cloud	Internal data sources need public access or relocation to cloud-accessible infrastructure.
Template accounts not working	Template accounts are separated from children	Always migrate template accounts together with all child accounts that use them.
Third-party app field differences	Different field availability in the Cloud	Some Xray and Zephyr fields aren't available in Cloud. Check the app documentation for Cloud-specific limitations.
Zephyr imports slow	No incremental import in Cloud	Due to REST API limitations, each Zephyr import is a full import. Plan for longer import times.

Download Your Migration Checklist

We've compiled everything from this guide into a print-friendly PDF checklist. Use it to track your progress through each phase of the migration.

Download the eazyBI Migration Checklist (PDF)

The checklist includes:

Prerequisites verification
Pre-migration preparation steps
Migration process walkthrough
Post-migration verification
Common issues and solutions

Watch the Full Webinar

Want to see the migration process in action? Watch the complete webinar recording, including a live demonstration of migrating eazyBI from the Data Center to the Cloud.

What you'll see:

Live walkthrough of the Database Migrator
Creating API tokens for Cloud authentication
Handling authorization resets
Re-adding dashboard gadgets
Real-time Q&A with the eazyBI team

Q&A: Answers to Common Migration Questions

During the webinar, we received many questions from attendees. Here are answers to the most common ones.

Is there a list of IP addresses that need to be allowed for eazyBI migration?

Yes. Check the eazyBI documentation, specifically the REST API page, for the list of IP addresses that eazybi.com uses. If your network restricts outbound connections, you'll need to allow these IPs for the migration to work.

Does eazyBI store data on the Atlassian platform?

No. eazyBI stores data on eazybi.com , which runs on Google Cloud Platform — separate from Atlassian's infrastructure. eazyBI is SOC 2 Type II certified. For security assessments or compliance documentation, contact support@eazybi.com

How are user permissions and account roles migrated?

Users are matched by email address. If a user with the same email exists in Cloud, their permissions are migrated. If a user isn't found, you'll see a migration warning. Users with different emails between DC and Cloud will need their authorization reset manually.

Are custom field IDs updated automatically during migration?

The migrator attempts to identify custom fields by their name and type. If a match is found, the field ID is updated automatically. If not, you'll need to manually update references in advanced settings and calculated fields.

Can I migrate my Confluence gadgets?

Unfortunately, eazyBI gadgets in Confluence pages cannot be migrated automatically. This is an Atlassian platform limitation, not an eazyBI limitation. You'll need to recreate these gadgets manually after migration.

Are there differences for Zephyr in Cloud?

The data structures are largely the same between Data Center and Jira Cloud. The main difference is that incremental imports aren't available in Jira Cloud due to REST API limitations. Each Zephyr import will be a full import, so expect longer import times.

What if I use SQL databases that aren't publicly accessible?

Internal SQL databases won't be accessible from eazyBI for Jira Cloud. You'll need to either expose the database to the public network (with appropriate security) or migrate it to a cloud-accessible location like Azure SQL or AWS RDS.

Resources

Documentation: eazyBI Database Migration Guide
Webinar Recording: How to Migrate eazyBI from DC to Cloud
Support: support@eazybi.com — For migration questions, security assessments, and technical assistance
Security: eazyBI is SOC 2 Type II certified, Atlassian Cloud Fortified, and data is stored on the Google Cloud Platform. Learn more about eazyBI security.