---
title: "Differences between CMJ Server/Data Center and CMJ Cloud"
canonical: "https://support.appfire.com/space/CMJ/607388798/Differences%20between%20CMJ%20Server%2FData%20Center%20and%20CMJ%20Cloud"
format: markdown
---
> Macro (aura-html)

## Comparison

If you're a Jira Server/Data Center user transitioning to Jira Cloud and using Configuration Manager, you'll have to migrate to *[Configuration Manager for Jira Cloud](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?tab=overview&hosting=cloud)*.

Check out the table below for a breakdown of the features in Configuration Manager for Server/DC versus Configuration Manager for Jira Cloud. It provides insights into the following features:

- [AVAILABLE] - features that have already been *rolled out*,
- [NOt available] - features* not planned for the future*,
- [COMING SOON] - features *currently in development,* and
- [FUTURE] - features *planned for the future*.

Need more details on the differences between [Configuration Manager for Jira](https://appfire.atlassian.net/wiki/spaces/DCMFJ) and [Configuration Manager for Jira Cloud](https://appfire.atlassian.net/wiki/spaces/CMJC)? Feel free to reach out to our [support team](https://appfire.atlassian.net/servicedesk/customer/portals) for assistance. 

|  |  |  |
| --- | --- | --- |
| ### Feature | ### Configuration Manager for Server/DC | ### Configuration Manager for Cloud |
| #### Jira application support |
| Jira Core configuration | [available] | [available] |
| Jira Software configuration | [available] | [available] |
| Jira Service Management configuration | [available] | [available] |
| #### Deployment of configuration elements |
| Boards<br>*Selecting boards to deploy* | [available] | [available] |
| Boards associated with the deployed project<br>*Automatically adding such boards to the deployment* | [available] | [future] |
| Filters | [available] | [future] |
| Dashboards | [available] | [future] |
| Issue data and attachments | [available] | [future] |
| Filtering issues to deploy with JQL | [available] | [future] |
| #### Configuration analysis |
| Analysis report of the deployed configuration | [available] | [available] |
| Detailed analysis of the deployed configuration<br>*In the detailed analysis, we display actual changes like a project scheme changing from X to Y, adding a custom field to a screen, or adding a post function to a workflow.* | [available] | [Available] |
| Audit log | [available] | [Coming soon] |
| #### Transformations/Selective Merge |
| Renaming configuration elements inline | [available] | [available] |
| Change mapping between source and destination configuration elements | [available] | [available] |
| Custom field conflict resolution | [available] | [available] |
| Modification of active workflows | [available] | [Available] |
| Modification of active workflow schemes | [available] | [Future] |
| User mapping | [NOt available] | [available] |
| Group mapping | [NOt available] | [Available] |
| #### App data and configuration deployment<br>Deploying 3rd-party Jira apps' configuration and data between Jira instances |
| Workflows | [available] | [available] |
| Custom fields and projects | [available] | [future] |
| App configuration that is not project-related | [available] | [future] |
| #### Integrity Check |
| Integrity check of the deployed configuration | [available] | [future] |
| Built-in integrity check UI | [available] | [future] |
| Built-in Power Admin | [available] | [NOt available] |
| #### REST API Automation |
| Public REST API | [available] | [NOt available] |
| #### Rollback |
| Rollback of configuration changes | [available] | [NOt available] |