Planning your migration to Cloud | Elements Documentation

⏲️

Elements Connect migration to Cloud timeline may vary widely depending on several factors, including the size of the instance, the complexity of the data, the number of users, and whether apps are involved. Below is an overview of the timeframes we recommend for migrating with Elements Connect:

DC configuration analysis and compatibility check: 1–3 weeks
Fields value migration: several hours, depending on the volume of data you have to migrate
- 500,000 values ==> ~ 2 hours
Fields configuration and testing: 1-3 weeks

If you think you will need help in your migration process, we highly recommend that you reach us as soon as your migration has been decided.

👉 Ask for help!

Before starting your migration to Elements Connect Cloud, ensure you have all the necessary information and a comprehensive understanding of the process. Proper preparation will help you avoid unexpected challenges and streamline the migration experience.

Understand available fields types on Cloud and how they work

Elements Connect Cloud offers 2 types of connected fields; connected custom fields and connected items.

Only Connected custom fields are supported by our JCMA Migration tool.

Here is the difference between these field types:

Feature/Capability	Connected Custom Fields	Connected Items
Usage in Jira Service Management	Available on request creation forms in the customer portal 🆕 Dependency to request context is available	Available on request creation forms in the customer portal Dependency to request context is available
Usage in Jira projects	Available Dependency to issue context	Usable in view screens of any project type, but not on issue creation screens Dependency to issue context is unavailable
Live fields	Available	Not available
Advanced customization of display	Not available	Available, see our Template guide
Integration with workflow validators	Available	Not available
Integration with advanced reports created with native JQL	Available	Not available
Integration with Automation and 3rd-party apps	Available	Not available
Populate migrated data from Elements Connect Data Center	Available	Not available

For more details about different fields types, please refer to this page.

Assess your Data Center configurations

After having an overview of available field types on the Cloud and functionalities they support, it’s time to analyze your Elements Connect Data Center configuration.

Some use cases can be translated seamlessly to Cloud, while others may not yet be available, or you need to implement a different approach to achieve the same that you have done in your Jira Data Center environment.

A careful analysis of your Data Center configuration will help you in planning workarounds or adjustments as needed.

Datasource assessment:

Determine data sources you use in Elements Connect Data Center and if they’re supported in Cloud (click here for list of supported datasources in Cloud).

Here are some identified problematic use-cases and suggested workarounds (when possible):

Feature in Elements Connect Data Center	Availability in Elements Connect Cloud	Suggested workaround
Data source in one of the following: Jira SQL, Jira JQL	Currently unavailable	Connect to your local Jira instance by creating a REST API datasource.
Data source is a file	Currently unavailable	Switch the Data (if possible) into a Database or a REST API datasource
Data source is a REST API but response type is not JSON (XML, CSV…)	Currently unavailable	Update the Datasource response (if possible) to JSON.
Data source authentication mode: MTLS	Currently unavailable	N/A
Database connected via VPN	Currently unavailable	Expose API or use an intermediate proxy.

Fields assessment

Identify all custom fields in Elements Connect Data Center (we encourage you to clean unused fields to simplify your migration).
Check for complex queries
Check for complex templates
Identify used dependencies and check whether they are supported or not (for a complete list of available dependencies, click 👉 here).

Here are some identified problematic use-cases and suggested workarounds (when possible):

Feature in Elements Connect Data Center	Availability in Elements Connect Cloud	Suggested workaround
Fields relying on HTML in templates	Currently unavailable in Cloud for Custom Fields. HTML templating available for Connected Items	For complex and mandatory displayed templates, use Connected Items. Having FreeMarker in Custom Fields is in our mid-term roadmap.
Fields plugged with a Jira JQL data source	A workaround for Local Jira data source creation exists: How to configure a local Jira instance as a datasource Field values migrated to Cloud will be issue ids, and not issue keys. Issue ids are often not the same between DC instance and Cloud site.	Contact Support team in order they can help you to set a workaround in order to migrate fields values plugged on this type of datasource.
Date time field	Not available in Cloud

Feature in Elements Connect Data Center

Availability in Elements Connect Cloud

Suggested workaround

Fields relying on HTML in templates

cross mark Currently unavailable in Cloud for Custom Fields.

check mark HTML templating available for Connected Items

For complex and mandatory displayed templates, use Connected Items.

info Having FreeMarker in Custom Fields is in our mid-term roadmap.

Fields plugged with a Jira JQL data source

check mark A workaround for Local Jira data source creation exists: How to configure a local Jira instance as a datasource

warning Field values migrated to Cloud will be issue ids, and not issue keys. Issue ids are often not the same between DC instance and Cloud site.

Contact Support team in order they can help you to set a workaround in order to migrate fields values plugged on this type of datasource.

Date time field

Not available in Cloud

Discover full feature parity table here!

Ready to take the next step? Discover the detailed migration path here: Migration path.