---
title: "DC to Cloud migration"
canonical: "https://support.appfire.com/space/AIPC/2756772026/DC%20to%20Cloud%20migration"
format: markdown
---
> Macro (aura-html)
This page explains how to migrate your Assets and Inventory Plugin (AIP) data from Jira Data Center to Jira Cloud.
AIP currently does not provide a JCMA (Jira Cloud Migration Assistant) path. Instead, you can migrate by:
1. Creating the same asset structure in Cloud, then
2. Exporting assets from Data Center in Cloud format, and
3. Importing the exported CSV file into Cloud.
## Before you start
### Prerequisites
- Before starting the migration, review the [DC to Cloud feature comparison](https://appfire.atlassian.net/wiki/spaces/AIPC/pages/797081992/DC+to+Cloud+feature+comparison?atl_f=PAGETREE) page to understand what is and isn’t supported in Jira Cloud. This helps you:
- confirm which asset attributes can be migrated as-is,
- identify unsupported attribute types early, and
- adjust your Cloud configuration or use cases before exporting data.
- Admin permissions for AIP in both Jira Data Center and Jira Cloud.
- Access to your Data Center asset repository.
- A Cloud environment where you can create asset structure (collections, types, attributes).
### Important notes and limitations
- Asset type collections, asset types, and attributes are not created automatically during import.
**You must create them in Jira Cloud** before importing assets.
- Not all Data Center attribute types are supported in Jira Cloud. Check the [feature comparison](https://appfire.atlassian.net/wiki/spaces/AIPC/pages/797081992/DC+to+Cloud+feature+comparison?atl_f=PAGETREE) page and:
- create the closest supported attribute type in Cloud, or
- adjust your use case before exporting data.
- System fields (global attributes) such as **Location** are not supported in Cloud.
- Use a workaround (for example, a **Select list** attribute).
- This may require changes both in Data Center and in the exported CSV.
- Asset links (references between assets) are not migrated automatically via CSV import.
- Asset custom fields and their values from Jira work items are not migrated as part of this process.
- Plan your scope:
- If you want to migrate everything, make sure your Asset Navigator search includes all assets.
- If you only want a subset, filter first and export only what you need.
- Currently, you can import up to 1,000 assets per CSV file in Jira Cloud. If you have more assets:
- split your export into multiple files, or
- filter your Asset Navigator search accordingly.
## Video overview
If you prefer a visual walkthrough, watch the screen recording before you start.
## Step 1: Recreate your asset structure in Jira Cloud
Log in to your Jira Cloud instance and create the same structure and required fields you have in Data Center:
1. Asset type collections
2. Asset types (make sure they are in the correct collections)
3. Attributes (make sure each attribute is created under the correct asset type)
- Keep attribute names and types consistent with Data Center.
- If your attributes include references, statuses, or users, make sure the Cloud-side configurations are ready so the import can match values correctly.
> ℹ️ Before exporting data, double-check that:
> ℹ️
> ℹ️ - all required attributes exist in Cloud,
> ℹ️ - unsupported attribute types are replaced with supported alternatives, and
> ℹ️ - reference, user, and group attributes are configured in advance.
> ℹ️
> ℹ️ Missing or mismatched attributes will cause the import to fail.
## Step 2: Export assets from Jira Data Center in Cloud format
In Jira Data Center:
1. In the top navigation bar, go to **Asset Navigator**.
2. Refine your search to include the assets you want to migrate.
3. Open the **Export** menu and select **Export for Cloud**.
4. Select the delimiter, then click **Download**.
5. Save the generated file. This file is Cloud-compatible and is meant for On-Premise → Cloud import.
> ℹ️ **Important export considerations**
> ℹ️
> ℹ️ - After downloading the CSV, open it in a plain text editor (for example, TextEdit or Notepad) and check the separators used in the file:
> ℹ️ - **Field separator**: separates columns (for example, `,` or `;`)
> ℹ️ - **Decimal separator**: used in number values (for example, `.` or `,`)
> ℹ️ - **Multi-value separator**: separates multiple values in the same field
> ℹ️ These values must match the separators you configure during the import in Jira Cloud. Although the default field separator is usually a comma (,), some operating systems or spreadsheet tools save CSV files using a semicolon (;). If the separators don’t match, the import may fail or data may be mapped to the wrong fields.
> ℹ️ - If your assets contain reference attributes (links to other assets), you must decide how referenced assets are identified:
> ℹ️ - **By ID** – matches assets using their unique internal ID
> ℹ️ - **By name** – matches assets using the asset name
> ℹ️ Use the same method consistently during export and import. If asset names are not unique in your Data Center instance, exporting and importing references **by ID** is strongly recommended. Otherwise, the import may link assets incorrectly or fail to resolve references.
> ℹ️ For detailed instructions and explanations of import options and field mappings, you can refer to [this page](https://appfire.atlassian.net/wiki/spaces/AIP/pages/10257165).
You now have a Cloud-compatible CSV export from Data Center.
## Step 3: Import the exported CSV file into Jira Cloud
In Jira Cloud:
1. Open AIP and go to the **Import** flow (CSV import tool).
2. Upload the CSV you exported from Data Center.
3. Make sure your import settings match your file format (for example):
- **Character Set:** UTF-8
- **Separators:** field / decimal / multi-value (match what you used when exporting)
- **Date/time format:** must match Jira Cloud expectations
> ℹ️ **Reference, user, and group attributes**
> ℹ️
> ℹ️ - Referenced assets must already exist in Cloud at import time.
> ℹ️ You cannot set a reference to an asset that hasn’t been imported yet.
> ℹ️ - Configure the **Reference Asset Fetch Method** during import to match your export (ID or name).
> ℹ️ - If your attributes use Jira users or groups:
> ℹ️ - those users and groups must already exist in Jira Cloud,
> ℹ️ - migrate your Jira environment first, then migrate AIP data.
4. Continue through the import steps (**Upload **→** Review **→** Import**).
5. After the import finishes, review the summary to confirm:
- how many assets were imported successfully
- which assets failed and why
> ℹ️ For detailed instructions and explanations of import options and field mappings, you can refer to [this page](https://appfire.atlassian.net/wiki/spaces/AIPC/pages/197889938/Import+Export+assets?atl_f=PAGETREE).
Your assets are now available in AIP for Jira Cloud.
## What is not migrated
Keep in mind that the following are not migrated automatically:
- Asset type collections, types, and attributes
- Asset links (relationships)
- Asset custom fields on Jira work items
- Jira users and groups
## Troubleshooting
### Import fails because a field/attribute doesn’t exist
This usually means the **asset type attributes were not created (or don’t match)** in Cloud.
- Go back to **Step 1** and confirm:
- asset type collection exists
- asset type exists under the correct collection
- all required attributes exist and match the CSV columns
### “Group not found” error (even though the group exists)
This can happen because of **special characters or whitespace** in group names.
- Prefer group names without special characters.
- Note: Jira default groups often use `-` instead of spaces.
### Date/time values look wrong after import
Spreadsheet editors (especially Excel) can change date formats depending on OS settings.
- Confirm your CSV uses date/time formats accepted by Jira Cloud.
- Avoid re-saving the exported CSV through tools that auto-convert dates unless needed.