Migrating On-prem to Cloud

[Kolawole Akeredolu]

We have done some migrations at the beginning of getting the Jira service management platform going but some data has been gathered on-prem since then and we would like to migrate the difference between what we had migrated earlier and what has been created since then. The question is, would the new data override the existing? We do not want to lose the configuration put into place and all the good stuff that we have done or does Jira intuitively does incremental capture since the last migration?    

[Diana_Architect_ZigiWave]

@Kolawole Akeredolu hey there. In case you're open to exploring the idea of using a 3rd party tool, check out ZigiOps. It connects systems bi-directionally, 100% code-free and customizable. It will help you migrate just the data you want (due to its advanced customization functionalities). It's easy to use and has no limitations on the data you want to transfer. Feel free to check it out and if you want to know more - drop us a line.

Regards, Diana (ZigiWave team)

[Brad Peterson]

Hi Kolawole,

Jira Service Management does not have built-in functionality for incremental data migration or automatic capture of changes since the last migration. When performing a data migration in Jira, it typically involves exporting data from the source instance and importing it into the target instance. This process replaces the existing data in the target instance with the data from the source instance.

If you want to migrate only the differences between the previously migrated data and the new data created on-prem, you can consider implementing your use case through a third-party migration tool, OpsHub Migration Manager. OpsHub is an Atlassian partner with extensive experience in undertaking complex migration projects ensuring zero downtime, no data loss, data Integrity and full ownership of the migration process which can be a good choice for the given job. It maintains the relations between related work items, during the migration.

OpsHub takes care of the following use cases also: 

•  Non-disruptive migration: Migration can cause massive disruptions to operations by not letting users use Jira while the migration is going on. Often the cost of disruption dominates all other explicit and hidden costs.  OpsHub minimizes disruption to all aspects of current operations. 
• Jira Software and JSM issue types:  Jira Software supports issue types, Epic, Bug, Story, Task, and Subtask and Jira Service Management (JSM) supports issue types, Change, IT help, Incident, New feature, Problem, Service request, etc. Due to the issue types being different, it is not straightforward to migrate from the Jira project to JSM processes. OpsHub makes it very simple to map the issue types and migrate the issues without any hassle.
•  Preservation of institutional knowledge: OpsHub preserves historical knowledge of Jira data.   

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

Thanks, 

Brad