---
title: "Migrate from Data Center to Data Center"
canonical: "https://support.appfire.com/space/RFP/803406932/Migrate%20from%20Data%20Center%20to%20Data%20Center"
format: markdown
---
> Macro (aura-html)


> ⚠️ <span style="color: #333333">Please use the same </span><span style="color: #333333">*Rich Filters for the Jira Dashboards*</span><span style="color: #333333"> version when migrating data between two Data Center instances. Using different </span><span style="color: #333333">*Rich Filters for Jira Dashboards*</span><span style="color: #333333"> versions on the source and target instances might cause data incompatibility problems.</span>

## > Macro (anchor)

Introduction

To migrate *Rich Filters for Jira Dashboards* app data between two Jira Data Center instances, the Data Center version of *Rich Filters for Jira Dashboards* integrates with [Configuration Manager for Jira (CMJ)](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?hosting=datacenter&tab=overview). *Configuration Manager for Jira (CMJ)* is a powerful change management and data migration solution, allowing users to migrate data between Jira instances. The migrated data includes Jira issues, projects, configuration and data of 3rd party apps integrated with CMJ.

The *Rich Filters for Jira Dashboards* app uses two different types of data that need to be migrated:

1. The configuration of the rich filters defined on your Jira instance
2. The configuration of the rich filter gadgets used in dashboards on your Jira instance

*Configuration Manager for Jira (CMJ) *lets you automatically migrate both types of data: **rich filters** and **dashboards containing rich filter gadgets**. 

> ℹ️ The integration with *Configuration Manager for Jira (CMJ)* is available, starting with *Rich Filters for Jira Dashboards* version 1.24.0. The functionality described below was tested with *Configuration Manager for Jira (CMJ)* version 6.10.7.

## > Macro (anchor)

Migrating *Rich Filters for Jira Dashboards* app data

> ⚠️ Before migrating your data, you should know how *Configuration Manager for Jira (CMJ) *works. The documentation of *Configuration Manager for Jira (CMJ)* is available [here](https://botronsoft.atlassian.net/wiki/spaces/CMJ/overview?homepageId=4423686). 
> ⚠️ 
> ⚠️ <span style="color: #333333">Migrating your data between two </span>Jira Data Center instances requires several configuration steps, detailed in the Configuration Manager documentation for Jira (CMJ). Below, we refer only to the migration details relevant to the migration of the <span style="color: #333333">*Rich Filters for Jira Dashboards*</span> app data.

### > Macro (anchor)

Exporting data

To export data from a Jira Data Center source instance, Configuration Manager for Jira (CMJ) allows users to create three types of snapshots: system*** configuration snapshot***, ***Project configuration snapshot***, or ***Project snapshot with issues***. The data in each snapshot type is detailed in the relevant [Configuration Manager for Jira (CMJ) documentation](https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784132/Create+a+Snapshot).

Each type of snapshot may include *Rich Filters for Jira Dashboards* app data, depending on the selected configuration at snapshot creation. More precisely:

- The ***System configuration snapshots*** will contain:
  - the rich filters from the source Jira instance if the "Include Global App Data" checkbox is selected in the snapshot creation configuration screen
  - all the dashboards from the source instance (including dashboards that might contain rich filter gadgets) if the "Include all Dashboards" checkbox is selected in the snapshot creation configuration screen
- The ***Project configuration snapshots ***and ***Project snapshots with issues*** will contain:
  - the rich filters from the source Jira instance if the *Rich Filters for Jira Dashboards* app is selected in the *Select Apps* configuration screen
  - those dashboards from the source instance (some of which might contain rich filter gadgets) that are selected in the *Select Dashboards* configuration screen.

> ✅ ### Things to keep in mind
> ✅ 
> ✅ - The rich filters are based on Jira filters. All Jira filters used in the configuration of at least one rich filter will automatically be added to the snapshot, even if the snapshot was not explicitly configured to contain these Jira filters.
> ✅ - If the snapshot is configured not to contain rich filters but to contain dashboards that use rich filter gadgets, then at the destination, these gadgets will be added as unconfigured.

#### > Macro (anchor)

Selectively including or excluding rich filters from the snapshot

By default, when creating a new snapshot, all the rich filters existing on the source Jira instance are included if the users choose to export Rich Filters app data. However, Jira administrators can refine this process and specify whether certain rich filters should be included or excluded from the snapshot. 

You can further configure which rich filters and dashboards to migrate using the **DC Migration Configuration** page.

1. Navigate to **Jira Administration **().
2. Go to **Manage apps**.
3. Under *RICH FILTERS*, select **DC migration (CMJ)**.
4. For **Migration snapshot options**,** **select how you want to include rich filters in the migration:
  - **Include all rich filters**—This** **is the default selection. It ensures that all rich filters available on the source instance are included in the snapshot.
  - <span style="color: #374151">**Include only the specified rich filters**</span>—<span style="color: #374151">This option lets you define a specific set of rich filters to be included in the snapshot. The list of rich filters is indicated by their respective IDs, separated by commas. All rich filters not included in the list will be excluded from the snapshot.</span>
  - <span style="color: #374151">**Include all rich filters except the specified ones**</span>—<span style="color: #374151">When this option is selected, you can designate a list of specific rich filters to be excluded from the snapshot. As above, the list is provided as comma-separated rich filter IDs. All rich filters not listed are automatically included in the snapshot.</span>

> ✅ ### Things to keep in mind
> ✅ 
> ✅ - <span style="color: #374151">Regardless of the selected options for filter inclusion or exclusion, the snapshot deploy procedure, described in the following section, remains the same.</span>
> ✅ - <span style="color: #374151">If the snapshot is configured to contain dashboards that use rich filter gadgets pointing to rich filters that are not included in the snapshot, then these gadgets will be added as unconfigured at the destination.</span>

### > Macro (anchor)

Deploying data

Snapshots can be deployed on Jira Data Center target instances. There are two snapshot deployment modes:

- *Merge Configuration* – the configuration in the snapshot is "merged" with the existing configuration on the target Jira instance
- *Restore Configuration* – the configuration in the snapshot "replaces" the existing configuration on the target Jira instance

For more details about the deployment modes, refer to the [Configuration Manager for Jira (CMJ)](https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/13402114/System+Configuration+Snapshots) documentation. 

The user can choose between the two deployment modes for* System configuration snapshots*. For *Project configuration snapshots *and* Project snapshots with issues*, the deployment strategy is always *Merge Configuration*.

Depending on which of the two deployment modes is used, the *Rich Filters for Jira Dashboards* app data is deployed as follows:

- If the deployment mode is *Merge Configuration*:
  - No existing rich filter on the target instance is modified in any way.
  - If the snapshot contains a rich filter that does not exist on the target instance, then the rich filter is deployed on the target instance.
  - If the snapshot contains a rich filter and if the target instance also contains a rich filter that was created as part of a previous deployment and based on the same source filter as the one in the snapshot, then the existing rich filter on the target instance is kept as is and the rich filter in the snapshot is skipped from the deployment; if the user wishes to deploy the rich filter version which is stored in the snapshot, then he needs to manually delete the existing rich filter on the target instance, before deploying the snapshot.
  - If a snapshot contains a Jira dashboard (which might contain rich filter gadgets) and the same dashboard does not already exist on the target instance, then the dashboard is deployed on the target instance.
  - If a snapshot contains a Jira dashboard (which might contain rich filter gadgets) and if the same dashboard already exists on the target instance as part of a previous deployment, then the dashboard configuration on the target is overwritten by the dashboard configuration in the snapshot.
- If the deployment mode is *Restore Configuration*:
  - All rich filters on the target instance are deleted and replaced by those in the snapshot.
  - If a snapshot contains a Jira dashboard (which might contain rich filter gadgets) and the same dashboard does not already exist on the target instance, then the dashboard is deployed on the target instance.
  - If a snapshot contains a Jira dashboard (which might contain rich filter gadgets) and if the same dashboard already exists on the target instance as part of a previous deployment, then the dashboard configuration on the target is overwritten by the dashboard configuration in the snapshot.