Deploying projects multiple times using Configuration Manager

[Tony Rice]

We have a few dozen projects of varying sizes and complexities that need to be migrated from an old Jira server to a new Jira Data Center server.

Would it be possible to create a snapshot, deploy that into the new JDC instance, then create another snapshot with just the issues that changed since the last snapshot was created as deploy that to call it "migrated"?

This would give us the time needed to do the migration without a days long downtime for the service.

[Stephen Wright _Elabor8_]

Hi @Tony Rice 

I'm not sure if this is technically feasible using CMJ specifically - I'd probably recommend contacting the vendor directly, or checking out their documentation.

---

But, it's not something I'd necessarily try either during a migration - unless there's a good reason to do it, such as the DC Launch being in the future for all users simultaneously.

I'd recommend:

• Migrating in phases, to avoid this issue. Split the Projects into Groups and migrate them once, along with launching the impacted users into the new instance.
• Migrating on the weekend, and have a clean split from the previous Server instance.
• Look to mitigate complexities - for example, if the Projects' configuration is being simplified as part of this process, make these changes in the Server instance and avoid unnecessary mid/post-migration steps.

---

Or, if you must do this - I'd look to create a (real-time) link between the Issues in Server and DC, and allow this to manage Issue updates, etc - until you're ready to complete each move across to DC.

I've seen this done before using either...

• Automation, using web hooks
• External System Import, using CSV. This is a more manual option, and just requires a unique identifier to exist between the two instances. This could be Issue Key, or a custom field with a UID in it (used in Excel to map the field values).
• Use an Issue Sync App - check the Marketplace for options

---

But, some of these options might not offer support for all Issue components, such as the Issue History - which is why I'd usually avoid the need to do this unless absolutely necessary.

Ste