---
title: "Migration to cloud from server/DC"
canonical: "https://support.appfire.com/space/CSOT/68750398/Migration%20to%20cloud%20from%20server%2FDC"
format: markdown
---
# <span style="color: #333333">Description</span>

This page explains:

- <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 </span><span style="color: #000000">*Create on Transition for Jira*</span><span style="color: #000000">, version 7.7 or newer, 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"> on the server/ DC instance.</span>

# Migration process

1. <span style="color: #000000">Install (and configure) </span><span style="color: #008000">[Create on Transition for Jira](https://marketplace.atlassian.com/apps/697735/create-on-transition-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 Create on Transition for Jira workflow and app configurations. </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, workflow 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>

# Differences between Server/DC and Cloud versions of the app

<span style="color: #333333">The following table lists the feature differences between the Server/DC and Cloud versions of the app.</span>

| <span style="color: #333333">**Parameter/Feature**</span> | <span style="color: #333333">**Server/DC**</span> | <span style="color: #333333">**Cloud**</span> |
| --- | --- | --- |
| Features | Supported post functions:<br>- Create Issue(s)
- Creat Sub-task(s) | Supported post functions:<br>- Create Issue
- Create Subtask
- Update Issue<br>Supported validators: Conditioned Validator |
| <span style="color: #333333">Conditions based on substitution variables</span> | JQL supported for validators | JQL is not supported for validators. [Jira expressions](https://developer.atlassian.com/cloud/jira/platform/jira-expressions/) are supported instead. |
| Copy issues in epic | Supported | Not supported |
| Copy attachments | Supported | Supported with a limitation of user not being able to add attachments during workflow transitions |
| <span style="color: #172b4d">Conditions for subtask default handling</span> | Supported | Not supported |
| - <span style="color: #333333">Issue fields</span>
  - <span style="color: #333333">Due date offset </span>
  - <span style="color: #333333">Target issue status (Update Issue only)</span>
  - <span style="color: #333333">Remote link(s) - Link types</span>
- <span style="color: #333333">Optional rules</span>  
<span style="color: #333333">Regular expression pattern (for </span><span style="color: #333333">***Conditions & Configuration > Create multiple issues***</span><span style="color: #333333">*)*</span> | Supported | Not supported<br>> ⚠️ - <span style="color: #333333">All Confluence links are copied to the issue being created or updated as web links.</span>
> ⚠️ - <span style="color: #333333">The following result in a broken image in the issue being created or updated: </span>
> ⚠️   - <span style="color: #333333">Any media (image or GIF etc..) embedded in the original or parent issue's comments.</span>
> ⚠️   - <span style="color: #333333">Any non-image media files or attachments such as GIF etc., in the description or environment fields.</span>
> ⚠️ - <span style="color: #333333">*Create multiple issues *</span><span style="color: #333333">in the </span><span style="color: #333333">*Conditions & Configuration*</span><span style="color: #333333"> tab does not support the use of regular expressions.</span>
> ⚠️ - <span style="color: #333333">*Copy attachments*</span><span style="color: #333333"> and </span><span style="color: #333333">*Copy links*</span><span style="color: #333333"> are not supported while creating multiple issues or subtasks.</span> |

> 📝 In the Cloud version, you notice that the features supported by [Update on Transition for Jira](https://appfire.atlassian.net/l/cp/U2GsFSuL) are combined with [Create on Transition for Jira](https://appfire.atlassian.net/l/cp/gXP5LV2i).

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

<span style="color: #000000">It is recommended that the administrator creates the following field entities if they have not been migrated by JCMA:</span>

- <span style="color: #000000">Components</span>
- <span style="color: #000000">Fix versions</span>
- <span style="color: #000000">Affected versions</span>
- <span style="color: #000000">Labels</span>
- <span style="color: #000000">Reporter</span>
- <span style="color: #000000">Assignee</span>
- <span style="color: #000000">Watchers</span>

> 📝 When migrating from Jira Server/DC to Jira Cloud using the JCMA, draft workflows are not automatically included in the migration. Due to the tool's default behavior, only active workflows are migrated, excluding any workflows in draft mode. To ensure that these workflows are available in the Jira Cloud environment, publish the draft workflows before migration or copy the draft workflows manually.

## <span style="color: #000000">Substitution variables processing</span>

### <span style="color: #000000">Custom fields</span>

- <span style="color: #000000">When substitution variables are used to set custom fields in the source instance, the following representations are not currently supported in workflow post function migrations:</span>
  - <span style="color: #000000">entry_customfield_</span><span style="color: #000000">*<issue key>*</span>
  - <span style="color: #000000">values_customfield_</span><span style="color: #000000">*<custom field id>*</span>
  - <span style="color: #000000">values_customfield_</span><span style="color: #000000">*<issue key>*</span><span style="color: #000000">(entry)</span>
  - <span style="color: #000000">transition_customfield_</span><span style="color: #000000">*<custom field id>*</span>

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

<span style="color: #000000">When the following fields are defined using substitution variables in the source instance, they are not processed and are copied as-is to the target instance:</span>

- <span style="color: #000000">JQL query</span>
- <span style="color: #000000">Acting user</span>

# <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: #333333">[Help](https://appfire.atlassian.net/l/cp/P1KCmf63)</span><span style="color: #333333"> and open a ticket with us. This helps us identify and prioritize fixes and improvements.</span>