Jigit - Migrating from Data Center to Cloud | Move Work Forward Documentation

This guide covers how to move your Jigit configuration from Jira Data Center (or Server) to Jira Cloud.

Before you start

Install Jigit on your Jira Cloud instance from the Atlassian Marketplace.
Make sure your Cloud instance can reach your Gerrit servers over the network.
Review Supported Git Providers and Feature Comparison to understand what is and is not available in Cloud before migrating.

If you've customised your migration secret, set the same value on both sides. Data Center and Cloud both ship with the same built-in migration secret by default, so most migrations - whether via CMA or the manual export/import below - work without any action here. But if either side has been changed to a custom value (Data Center's Global Settings > Migration secret, or Cloud's Jigit admin > Settings > Migration secret), both must be set to the same value. This secret encrypts your credentials before transfer and decrypts them on the other side - a mismatch means the migration completes but decrypting the transferred credentials fails.

What is migrated

The following configuration is carried across automatically by both migration options.

What is migrated	Detail
GitHub integrations	Connection details, authentication type (PAT or GitHub App), base URL, repository path, include/exclude Jira project scopes, webhook settings, repository pattern (MASK type), enabled/disabled state.
Gerrit configurations	Connection details (URL, username), project filter, include/exclude Jira project scopes, search settings, topic patterns, load batch size, enabled/disabled state.
GitLab integrations	Connection details are preserved. If the Data Center integration pointed at `gitlab.com`, it imports with status Unsupported - open it and click Save once to activate it (see Step 3 below). If it pointed at a self-managed GitLab server, it stays Unsupported permanently, since Jigit Cloud only connects to `gitlab.com`.
Azure DevOps integrations	Connection details preserved and imported with status Unsupported. We recommend migrating Azure DevOps workloads to Azure DevOps for Jira instead.

What is NOT migrated

Not migrated	What to do
Historical indexed data (commits, branches, PRs)	Jigit Cloud begins fresh indexing immediately after activation. All current branches and PRs will be indexed from the live Git providers; no manual action required.
Commit-only integrations	Cloud does not support commit-only indexation. Any DC integration with only commits enabled (no branches, no PRs) is imported as disabled. To reactivate, edit the integration and enable branch or PR indexation.
Webhook configuration	Webhook settings themselves don't carry over. To re-enable near-real-time updates in Cloud, turn on Support Git webhooks globally and Integrate a webhook on each integration - Jigit registers the webhook with GitHub or GitLab automatically. There's no need to manually update a URL on the provider side. See Jigit - Cloud Configuration.
Project-level configurations	DC supports per-project Jigit configuration. Cloud is global-only. Project-level DC configs are migrated to the global scope. Review the imported configurations after migration to confirm scope is correct.
GitHub Dependabot / Advanced Security configurations	These are project-level DC features with no Cloud equivalent in Jigit. Review your security posture separately after migration.
Smart commits settings	Smart commits are not supported in Jigit Cloud and are not migrated.
Activity report configurations	The activity report is a DC-only feature.
User-level Git credentials	Per-user credentials are not migrated. Users should re-enter their personal Git credentials via Profile > Jigit Git Connections after migration is complete.

Option A: Automated migration via Atlassian Cloud Migration Assistant (CMA)

When available, the CMA path will allow you to migrate Jigit configurations as part of your broader Jira Data Center to Cloud migration.

Launch the Atlassian Cloud Migration Assistant on your Data Center instance.
Select the Jira projects and apps to migrate and include Jigit. The Jigit configuration will then be included automatically.
The CMA exports your Jigit configurations and Gerrit configurations and transfers them to Cloud.
Jigit Cloud receives the export and processes it in the background.
Once complete, all supported integrations appear in Jira Admin > Apps > Jigit > Integrations with their status shown.
Review each integration, activate any that are in a paused state, and update webhook URLs where applicable.

Jira project ID mappings are resolved automatically by the CMA platform. You do not need to manually re-enter project include/exclude lists.

Option B: Manual migration

Use this option today. It involves exporting your configuration as a JSON file from Data Center and importing it into the Cloud admin UI.

Step 1: Export configuration from Data Center

In Jira Data Center, go to Jira Administration > Add-ons > Jigit.
Navigate to the Migration tab.
Click Export configuration.
Save the downloaded JSON file securely.

The export file contains encrypted authentication tokens. Store it securely and delete it once the import is complete.

Step 2: Import configuration in Jira Cloud

In Jira Cloud, go to Jira Administration > Apps > Jigit.
Navigate to the Migration tab.
Click Import configuration and upload the JSON file exported in Step 1.
Enter the encryption passphrase if one was set during export.
Click Start import.

Jigit processes the file in the background. A summary is displayed when complete, showing how many integrations and Gerrit configurations were imported and their statuses.

Step 3: Review imported configurations

After the import, check the status of each imported item:

Status	Meaning	Action needed
Active	The integration is ready and indexing will begin within 5 minutes.	None.
Disabled	The integration was disabled in DC, or it was commit-only (not supported in Cloud).	Edit the integration, enable branch or PR indexation, and re-enable it.
Unsupported	The integration uses a provider with no Cloud equivalent (Azure DevOps), or a self-managed GitLab instance - Cloud connects to `gitlab.com` only. Connection details are preserved either way.	For Azure DevOps: see Azure DevOps for Jira. For a self-managed GitLab instance: no Cloud equivalent currently. For a `gitlab.com` integration migrated before GitLab Cloud support existed: open the integration and click Save once - this activates it. A fresh migration of a `gitlab.com` integration today imports normally (Active or Disabled) and won't show Unsupported at all.

Step 4: Indexing begins automatically

Once an integration is in Active status, Jigit begins indexing automatically within 5 minutes. There is no need to trigger indexing manually.

Historical data from Data Center is not transferred, but Jigit indexes all current branches and pull requests from the live Git providers as part of the initial index run.

Step 5: Set up webhooks (optional)

If you had webhooks configured in Data Center, that configuration doesn't carry over - webhooks need to be set up again in Cloud. This is now simpler than a manual URL update: turn on Support Git webhooks in Jigit admin > Settings, then turn on Integrate a webhook on each GitHub or GitLab integration you want it for. Jigit registers the webhook with your Git provider automatically - there's nothing to copy into GitHub or GitLab yourself. See Jigit - Cloud Configuration for the full walkthrough, including the extra token scopes each provider needs for automatic registration.

Step 6: Ask users to reconnect personal credentials

Users who had personal Git credentials configured in Data Center will need to re-enter them in Cloud. Direct them to Profile > Jigit Git Connections to add their credentials.

After migration: verification checklist

All expected integrations appear in Jigit admin under Integrations or Gerrit
At least one integration shows Active status
Any gitlab.com integration migrated before GitLab Cloud support existed has been opened and saved once to activate it
Indexing has completed - open a Jira issue that had linked PRs in DC and confirm the Jigit Development panel appears
If using Gerrit: open a Jira issue with linked changesets and confirm the Gerrit tab appears in the Activity section
Users have re-entered personal Git credentials where needed
Any commit-only integrations reviewed and updated with branch/PR indexation enabled if desired
Azure DevOps users directed to Azure DevOps for Jira

Updated: September, 2026