---
title: "Migration from Data Center to cloud"
canonical: "https://support.appfire.com/space/CSOT/68747976/Migration%20from%20Data%20Center%20to%20cloud"
format: markdown
---
> Macro (aura-html)

This page explains the migration support details for the app content from Data Center to cloud.

## Prerequisites

You must have **Create on Transition for Jira**, version 7.7 or later, and [Jira Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?hosting=server&tab=overview) on the Data Center instance.

## Migration process

1. Install and configure [Create on Transition for Jira](https://marketplace.atlassian.com/apps/697735/create-on-transition-for-jira?hosting=cloud&tab=overview) on your cloud instance.
2. Install [Jira Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?hosting=server&tab=overview) on the Data Center instance that contains the Create on Transition for Jira workflow and app configurations you want to migrate.
3. Use **System** > **IMPORT AND EXPORT** > **Migrate to cloud** to navigate to the migration screen, where you can migrate global app configurations, workflow configurations, or users and groups as required. For more information, see [Atlassian's JCMA documentation](https://confluence.atlassian.com/cloud/use-the-jira-cloud-migration-assistant-to-migrate-from-server-to-cloud-993925215.html).

## Differences between Data Center and Cloud versions of the app

> ℹ️ Refer to [DC to cloud feature comparison](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/2495315985) page to see the differences between the DC and cloud versions of the app.

## Limitations

When you configure the Acting user field in the post functions, the field isn’t migrated. You must update it manually.

It is recommended that the administrator create the following field entities if they have not been migrated by JCMA:

- Components
- Fix versions
- Affected versions
- Labels
- Reporter
- Assignee
- Watchers

## Custom field names during migration

Custom field names in Create on Transition workflow configurations are matched by name during migration. If a field name in your Data Center instance doesn't exactly match the corresponding field in Cloud, the migration may not resolve the field correctly.

### Current behavior

If a custom field name from the Data Center workflow can't be matched in Cloud (for example, due to leading or trailing spaces, or other differences in the field name), the migrated workflow may still contain the original text. A dedicated warning may not always appear for that specific mismatch.

### What you should do before migrating

> ⚠️ Before migrating, review the custom field names used in your Create on Transition post functions. Ensure each field name matches the Cloud field name exactly, with no extra spaces or other differences. Compare the field name in your workflow configuration with how it appears in **Jira administration** > **Issues** > **Custom fields**.

### Planned improvement

A future update will provide clearer handling so you are explicitly informed when a field name can't be resolved, instead of silently passing values through. This improvement is tracked internally.

## Substitution variables processing

### Custom fields

- 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:
  - entry_customfield_*<issue key>*
  - values_customfield_*<custom field id>*
  - values_customfield_*<issue key>*(entry)
  - transition_customfield_*<custom field id>*
- In the add custom field section, if the Data Center instance has substitution variables, then they will not be migrated. Only selected values will be set.

### Others

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:

- JQL query
- Acting user