migration from Jira instance to another

[Wassim Abdallah]

Hi,

we have a migration activity for a tier 1 account in GCC with below requirements:

1- migration one project form a Jira instance A on version x and DB version y. This instance also contains other projects with sensitive data and cannot be exposed.

2- migration of this project will need to be applied to another jira instance B on version w and DB z.

what we suggested is the following:

1- replicate Jira Instance A

2- remote sensitive data from Jira instance A

3- align both jira instance and DB.

4- Complete the migration.

This approach is not technically feasible at the current stage and we are being requested to explore other options. 

Note that export/import is not an option given that some workflows/features/attachments might be broken

[Diana_Architect_ZigiWave]

@Wassim Abdallah hello. If you're open to exploring 3rd party solutions, check out ZigiOps. It's a fully no-code solution that will connect your instances and allow you to tailor the data you want to migrate from one Jira to another Jira instance. There is no limitation to the amount of data migrated, plus ZigiOps does not save any of the transferred data (100% security). Feel free to check it out and drop the tech team a line, in case you want to know more or simply want to discuss the use case.

Regards, Diana (ZigiOps team)

[Brad Peterson]

Hi @Wassim Abdallah 

What we understand is you want to migrate just one project from Jira instance A to Jira instance B, where the versions of both Jira instances are not same. OpsHub can help implement this migration use case. It will ensure that the other sensitive projects are not touched and only the required projects are taken over to another project, while keeping all data intact. OpsHub, has an extensive experience in undertaking complex migration projects ensures zero downtime, no data loss, complete date integrity and full ownership of the migration process can be a good choice for the given job.

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

Thanks,

Brad

[Wassim Abdallah]

Hi Brad,

the instances are on datacenter not cloud.

[Karim ABO HASHISH]

hi @Wassim Abdallah 

Proposing an alternative will depend on the complexity and level of details within your project. so let me have better understanding on the below points to better assist you with a solution.

1- How many workflows do you have in your project, how many status per each workflow and how many post-functions. just a rough estimate.

2- How many screens and fields used.

3- Is there any plugins used to extend the project functionality like script-runner behaviors, jobs , scripted fields or workflows post-functions.

4- how many issues and attachments you have in your project.

5- How many filters and boards.

Awaiting your return.

Cheers,

Karim

[Wassim Abdallah]

Hi @Karim ABO HASHISH ,

we are talking about :

1 project

9 Workflows (10 status in each)

16 Issue Types

3 Roles

20 filters

number of issues: < 50k

1 Permissions Schema

[Prince Nyeche]

I would suggest focusing on each project and collectively migrating them between each instance. You always have two options (CSV or JSON) if the DB are incompatible. The other aspect of the migration such as custom fields, workflow, screen etc can be created manually in the destination instance. Once that is achieved, then you can migrate project by project or simply just move everything based on the two options mentioned above. Once that is achieved, then migrate the attachment part last. In summary, the entire migration should be done in stages with each stage as a milestone to the ultimate goal.

[Wassim Abdallah]

hi Prince,

This is our approach but not feasible to the customer at the moment.