I wanted to Migrate Only 30% of Server data to Cloud Instance

[Sudharsan]

My Organization Is divided, and  Team A Decided to go to Cloud and Team B is decided to Move to DC.

What is the Best way to Move Team A's Data to Cloud, All Suggestions will really help me.

Regards,

Sudharsan.G

[Mayur Jadhav · Accepted solution]

Hello @Sudharsan , 

Hope you are doing well!!

If you want to migrate half of the data (projects) then I think JCMA would be the best option to migrate from the server cloud.

JCMA supports single project migration to the cloud.

To more about how JCMA works please have a look at Use the Jira Cloud Migration Assistant to migrate.

Regards,
Mayur

[Sudharsan]

Thanks @Mayur Jadhav 

[Sudharsan]

How this will work for Attachments ?

[Mayur Jadhav]

1. When you create migration profile and selects project JCMA will also consider attachment for Migration.

2. Or even you ca migrate attachment's well ahead through JCMA as well.

[Brad Peterson]

Hello @Sudharsan,

The best way to migrate project (A) data from JIRA Server to JIRA Cloud is through a third-party migration tool. Although there is a native tool, Jira Cloud Migration Assistant(JCMA) which supports this migration, it has its own shortcomings. There can be some downtime during the migration of project(A), due to the extended period of the Jira instance being in read-only mode. This can seriously impact the project operations of Team B and any other teams. 

Migration projects are typically complex and require careful planning and strategy. You can consider the following criteria while evaluating a third-party Migration tool.

• Project key restrictions: JIRA Server allows underscore (_) and few other characters in the project key, whereas on-cloud allows only letters in the project key. Any migration needs to factor in strategy to address these differences.
• Field Template In-consistency: Analyze if there is any field scheme configuration difference between your Server and on-cloud instance. Make sure you have a strategy for bridging those differences if needed.
• Plugin entity context and handling: If you are using plug-ins, those may require additional/special handling. Any such activities should be planned as a part of the migration plan.
• Impact on JIRA: Migration activities will result in additional load on Jira servers. Proper planning should be done to ensure appropriate scaling of the Jira server and isolation of migration load so that the regular activities are not impacted.

OpsHub, an Atlassian partner with extensive experience in undertaking complex migration projects ensuring zero downtime, no data loss, systematic cut-over, and a factory approach, can be a good choice for the given job. It supports the migration of all System & Custom Issue Types, Sub-Task Types, Version and Worklog, etc. from Jira Server to Jira Cloud.

Please reach out to OpsHub’s Migration Experts, for an initial free consultation on migration planning.

Thanks

Brad