---
title: "DC to Cloud feature comparison"
canonical: "https://support.appfire.com/space/JCPP/71272571/DC%20to%20Cloud%20feature%20comparison"
format: markdown
---
> Macro (aura-html)

This page explains limitations and differences between the Data Center and Cloud versions of the app.

> ℹ️ For more information on the migration process using JCMA, refer to this [page](https://appfire.atlassian.net/wiki/x/EoD5gg).

# Limitations

The following fields are not supported during migration:

- Username or user ID for user fields such as Assignee, Reporter, and so on
- Specific components
- Versions
- Issue security levels
- Status
- Labels
- Specific values in custom fields
- Entry** **substitution variable
- Epic issue type includes
- All the above-mentioned fields for subtask cloning

# Differences between Data Center and cloud versions of the app

The following table lists the differences between Data Center and cloud versions of the app:

| **Feature/Parameter** | **Data Center** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Clone behavior configuration | :check_mark:* | :check_mark: | *DC supports property file–based configuration; Cloud provides an easy-to-use [configuration](https://appfire.atlassian.net/wiki/spaces/JCPP/pages/71274379) screen to define clone operations that control the clone behavior. |
| Custom clone operations | :check_mark: (Supports maximum of 16) | :check_mark: (Unlimited) |  |
| Clone options:<br>- copy attachments
- copy watchers
- copy worklogs
- copy comments
- Copy versions
- Copy components
- copy subtasks
- copy subtask estimates
- copy parent reporter
- copy parent versions
- copy links
- copy epic issues
- copy epic issue subtasks
- copy epic issue subtask estimates | :check_mark: | :check_mark:* | *Both support all clone options. However, in Cloud, images or any form of media added to rich text editor issue fields are copied to the cloned issue only if **Copy attachments*** *is selected. If not, a broken image is displayed in the respective field of the cloned issue. |
| Mapping fields from original issue to a new value in the target issue conditioned on original issue field values:<br>- Set target project
- Set target type
- Set target component
- Set target version
- Set link type
- Set link direction | :check_mark:* | :check_mark: | Both support mapping all issue fields. DC uses property keys; For more information, refer to the **Mapping keys*** *section in the [Clone properties](https://appfire.atlassian.net/wiki/spaces/JCPP/pages/71275018) page. |
| Setting standard and custom fields for <u>**subtasks**</u> | :check_mark: | :cross_mark: |  |
| Single clone conditions:<br>- Projects
- Issue types
- Status
- Roles
- Project category | :check_mark: | :check_mark:*. | *All supported in DC; Cloud supports all except **Project category**. Roles are supported based on the user groups defined on the **Settings **page. |
| Bulk clone conditions:<br>- Projects
- Roles | :check_mark:<br>Supports all bulk clone conditions for Data Center only. | :check_mark:<br>Roles are supported based on the user groups defined on the **Settings **page. |  |
| Clone properties:<br>- fieldExcludes
- fieldIncludes
- ignoreFields
- projectIncludes
- issueTypeIncludes
- retainCommentsOriginalDate
- retainWorklogsOriginalDate
- epicIssueTypesIncludes | :check_mark: | :check_mark:* | *DC supports all properties. Cloud supports only:<br>- Ignore fields (Not applicable to subtasks)
- Field excludes
- Project includes
- Issue type includes
- Keep original comment date<br>> ℹ️ The **Keep original comment date **option** **should be manually selected on the *Clone Plus for Jira* page. |
| Post cloning processing | :check_mark: | :check_mark: | *Both function as expected. |
| Bulk Clone | :check_mark: | :check_mark: |  |
| Localization | :cross_mark: | :check_mark: (in Spanish, French, German, and Italian.) |  |
| Advanced field type - User Picker (multiple users) | :check_mark: | :check_mark: |  |

# Problem reporting

If you experience any problems or behavior changes that are unexpected, refer to[ ](https://appfire.atlassian.net/l/cp/MTZ1VhAs)[Troubleshooting](https://appfire.atlassian.net/l/cp/BZFNJbUc) or open a ticket with us. This helps us identify and prioritize fixes and improvements.