---
title: "Migration from Cloud to Server/Data Center"
canonical: "https://support.appfire.com/space/JCPP/71274907/Migration%20from%20Cloud%20to%20Server%2FData%20Center"
format: markdown
---
# <span style="color: #333333">Description</span>

<span style="color: #000000">This page explains:</span>

- <span style="color: #000000">Migration support details for the app content from server/DC to cloud</span>
- <span style="color: #000000">Differences between the server/DC and cloud version of the app</span>

## <span style="color: #000000">Pre-requisites</span>

<span style="color: #000000">Ensure to:</span>

- <span style="color: #000000">Install latest version of </span><span style="color: #000000">*Clone Plus for Jira *</span><span style="color: #000000">and </span><span style="color: #008000">[Jira Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?hosting=server&tab=overview)</span><span style="color: #000000"> (once JCMA supports migration) on the server/DC instance.</span>
- <span style="color: #000000">Comment out any custom clone operation(s) from the</span><span style="color: #008000"> </span><span style="color: #008000">[clone properties](https://appfire.atlassian.net/l/cp/MTZ1VhAs)</span><span style="color: #000000"> file in server/DC, if you do not intend to migrate the respective clone operation(s) to cloud.</span>

> ⚠️ - <span style="color: #000000">If you intend to migrate only users and groups from server/DC to cloud, </span><span style="color: #000000">*do not*</span><span style="color: #000000"> select the </span><span style="color: #000000">*Clone Plus for Jira*</span><span style="color: #000000"> app in the migration screen while using JCMA. Keep in mind that not all the mappings are available when the Clone Plus properties file is migrated. This can result in unusable mappings in-app data. For example, project data and configurations are not migrated.</span>
> ⚠️ - <span style="color: #000000">When you migrate clone customizations from:</span>
> ⚠️   - <span style="color: #000000">The same server instance to that of cloud more than once, the app data is overwritten in the cloud instance after the latest migration.</span>
> ⚠️   - <span style="color: #000000">Multiple server instances to the same cloud instance, multiple default clone operations (or multiple clone operations with the same name) are shown on cloud. Note that each of such configurations can be unique though the name and description are the same.</span>

# Migration process

1. <span style="color: #000000">Install (and configure) </span><span style="color: #008000">[Clone Plus for Jira](https://marketplace.atlassian.com/apps/44043/clone-plus-for-jira?hosting=cloud&tab=overview)</span><span style="color: #008000"> </span><span style="color: #000000">on your cloud instance.</span>
2. <span style="color: #000000">Install</span><span style="color: #008000"> </span><span style="color: #008000">[Jira Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?hosting=server&tab=overview)</span><span style="color: #008000"> </span><span style="color: #000000">on the server/DC instance from which you intend to migrate the Clone Plus for Jira app configurations. (This step is applicable once JCMA supports migration.)</span>
3. <span style="color: #000000">Use </span><span style="color: #000000">***System > IMPORT AND EXPORT > Migrate to cloud ***</span><span style="color: #000000">to navigate to the migration screen where you can migrate global app configurations, Clone Properties file configurations, and/or users and groups, as required. For more information, refer to</span><span style="color: #008000"> </span><span style="color: #008000">[this page](https://confluence.atlassian.com/cloud/use-the-jira-cloud-migration-assistant-to-migrate-from-server-to-cloud-993925215.html)</span><span style="color: #000000">.</span>

> ℹ️ - <span style="color: #000000">It is recommended to retain the clone operations (do not edit or delete) on the cloud instance as-is while the migration process in progress. Once the migration is complete, verify if the custom clone operations from the server/DC instance are migrated as expected to the cloud instance before editing or deleting any migrated clone operation on cloud.</span>
> ℹ️ - <span style="color: #000000">Global configuration settings such as analytical data settings from server/DC override the respective settings on cloud.</span>
> ℹ️ - <span style="color: #000000">The </span><span style="color: #000000">*Bulk Clone*</span><span style="color: #000000"> feature is turned ON for all the clone operations once they are migrated to cloud from server.</span>

# <span style="color: #000000">Limitations</span>

<span style="color: #000000">The following fields are not supported during migration:</span>

- <span style="color: #000000">username or user ID for user fields such as </span><span style="color: #000000">*Assignee, Reporter, *</span><span style="color: #000000">and so on</span>
- <span style="color: #000000">specific components</span>
- <span style="color: #000000">*Versions *</span>
- <span style="color: #000000">Issue s</span><span style="color: #000000">*ecurity levels*</span>
- <span style="color: #000000">*Status*</span>
- <span style="color: #000000">*Labels*</span>
- <span style="color: #000000">specific values in </span><span style="color: #000000">*custom fields*</span>
- <span style="color: #000000">*entry *</span><span style="color: #000000">substitution variable</span>
- <span style="color: #000000">*Epic issue type includes*</span>
- <span style="color: #000000">All the above mentioned fields for subtask cloning</span>

# <span style="color: #333333">Differences between server/ DC and cloud versions of the app</span>

<span style="color: #333333">The following table lists the differences between server and cloud versions of the app:</span>  


| <span style="color: #333333">Feature</span> | <span style="color: #333333">Server/DC</span> | <span style="color: #333333">Cloud</span> |
| --- | --- | --- |
| <span style="color: #333333">Clone behavior configuration</span> | <span style="color: #333333">Supports a property file based configuration</span> | <span style="color: #333333">Provides easy to use </span><span style="color: #333333">[configuration](https://appfire.atlassian.net/wiki/spaces/JCPP/pages/71274379)</span><span style="color: #333333"> screen to define clone operations that control the clone behavior</span> |
| <span style="color: #333333">Custom clone operations</span> | <span style="color: #333333">Supports a maximum of 16</span> | <span style="color: #333333">Supports any number of clone operations</span> |
| <span style="color: #333333">Clone options</span><br>- <span style="color: #333333">copy attachments</span>
- <span style="color: #333333">copy watchers</span>
- <span style="color: #333333">copy worklogs</span>
- <span style="color: #333333">copy comments</span>
- <span style="color: #333333">copy subtasks</span>
- <span style="color: #333333">copy subtask estimates</span>
- <span style="color: #333333">copy parent reporter</span>
- <span style="color: #333333">copy parent versions</span>
- <span style="color: #333333">copy links</span>
- <span style="color: #333333">copy epic issues</span>
- <span style="color: #333333">copy epic issue subtasks</span>
- <span style="color: #333333">copy epic issue subtask estimates</span> | <span style="color: #333333">Supports all the clone options</span> | <span style="color: #333333">Supports all the clone options</span><br>> ⚠️ <span style="color: #333333">Images or any form of media added to rich text editor issue fields are copied to the cloned issue only if </span>*Copy attachments *<span style="color: #333333">is selected. If not, a broken image is displayed in the respective field of the cloned issue.</span> |
| 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 | <span style="color: #333333">Supports mapping all issue fields</span><br><span style="color: #333333">For more information, refer to the </span><span style="color: #333333">*mapping keys *</span><span style="color: #333333">section in</span> [Clone properties](https://appfire.atlassian.net/wiki/spaces/JCPP/pages/71275018) | <span style="color: #333333">Supports mapping all issue fields</span> |
| <span style="color: #333333">Setting standard and custom fields for </span><u><span style="color: #333333">**subtasks**</span></u> | <span style="color: #333333">Supported</span> | Not supported |
| Single clone conditions<br>- Projects
- Issue types
- Status
- Roles
- Project category | Supports all single clone conditions | Supports all clone conditions except *Roles* and* Project category*. |
| Bulk clone conditions:<br>- Projects | Supports all bulk clone conditions for Data Center only. | Not supported |
| <span style="color: #333333">Clone properties</span><br>- fieldExcludes
- fieldIncludes
- ignoreFields
- projectIncludes
- issueTypeIncludes
- retainCommentsOriginalDate
- retainWorklogsOriginalDate
- epicIssueTypesIncludes | Supports all clone properties | Supports only:<br>- Ignore fields <span style="color: #333333">(Not applicable to subtasks)</span>
- Field excludes
- Project includes
- Issue type includes |
| <span style="color: #091e42">Post cloning processing</span> | <span style="color: #091e42">Functions as expected</span> | <span style="color: #333333">Functions as expected.</span> |
| Bulk Clone | Supported for Data Center only | Supported |
| Localization | Not supported | Supported in Spanish, French, German, and Italian. |
| Advanced field type - User Picker (multiple users) | Supported | Not supported |

# <span style="color: #333333">Problem reporting</span>

<span style="color: #333333">If you experience any problems or behavior changes that are unexpected, refer to</span><span style="color: #091e42">[ ](https://appfire.atlassian.net/l/cp/MTZ1VhAs)</span>[Help](https://appfire.atlassian.net/l/cp/BZFNJbUc) and open a ticket with us<span style="color: #091e42">. This helps us identify and prioritize fixes and improvements.</span>