Field mapping during migration

When creating Elements Connect custom fields on Jira Cloud, fields are preconfigured based on their Data Center configuration:

Name
Main type (Text, User, Date)
Single or Multi value
Storage type mapping:

Connect Data Center Field type	Connect Data Center storage	Connect Cloud field type after migration	Connect Cloud storage after migration
Live Text - Single	CODE `["KEY"]`	Text - Object - Single	CODE `{ "id":"KEY", "value":"KEY" }` see Live Text warning below
Live Text - Multi	CODE `[ "KEY-1", "KEY-2", "KEY-N" ]`	Text - Object - Multi	CODE `{ "ids": [ "KEY-1", "KEY-2", "KEY-N" ], "values": [ "KEY-1", "KEY-2", "KEY-N" ] }` see Live Text warning below
Snapshot Text - Single	CODE `["The value as seen in the issue"]`	Text - Snapshot - Single	CODE `"The value as seen in the issue"`
Live User - Single	CODE `[ { <JIRA DC USER STORAGE> } ]`	User - Single	CODE `[ { <JIRA CLOUD USER STORAGE> } ]`
Live User - Multi	CODE `[ { <JIRA DC USER-1 STORAGE> }, { <JIRA DC USER-2 STORAGE> } ]`	User - Multi	CODE `[ { <JIRA CLOUD USER-1 STORAGE> }, { <JIRA CLOUD USER-2 STORAGE> } ]`
Date	CODE `"2025-02-02"`	Date	CODE `"2025-02-02"`
Datetime	CODE `"2025-02-02T08:10:00.000+0000"`	Date	CODE `"2025-02-02"`

👉 see 3 - Customize look & feel of custom fields to understand difference between these storage types.

Live Text warning

During the migration of Live - Text fields, the key will be migrated, but the displayed value will have to be calculated via Elements Connect Cloud.
This will be possible by 2 different ways:

if you configure “Live update” on your target Connected custom fields, the displayed value of the field on a specific issue will be calculated when this issue is viewed by a user.
if you need all your migrated fields to store the correct displayed value because this value appears on dashboards or on JQL filters, we are working on a feature which will enable to trigger a bulk update of Elements Connect fields on a list of issues.
Note: it will update the modification date of all these issues.