You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We (Company XYZ) are going through a spin-off where part of our company is going to be operating under a different and totally independent legal entity (Company ABC). We currently have a cloud hosted solution under the domain (companyxyz) with Jira and Confluence products.
Both companies want to retain all content we have in Jira and Confluence in their own separate instances of Jira and Confluence with the idea that Company ABC will, over time, modify the content to map to their needs. It is important that the separate instances are totally separated out from an access standpoint.
Does anyone have any tips on how to accomplish such a duplication of content across two different domains (i.e., duplicate content from companyxyz domain to companyabc domain?
This is Dhiren from Exalate.
Exalate, provides a fully bi-directional synchronization between Jira(Cloud,Server,Data Center) and Jira(Cloud,Server,Data Center) among other ITSM systems that is fully customizable. It is easy to set up and the entire customization can be configured using a no-code interface. It also provides a Groovy based scripting engine for limitless customizability.
You can even integrate between Jira Software, Jira Service Management (Service Desk) and sync issues inside projects back and forth to achieve your integration requirements.
Exalate provides a flexible synchronization engine such that issues are automatically and securely synced - between multiple Jira's - wherever hosted. Benefit from a unified view and integrated workflow!
Use cases supported:
If you would like to see a customized demo of the product in action, feel free to book a slot with us.
Hi @Vivek Karnik
Thank you for your question.
If you want to migrate your Jira issues from one instance to another, I would recommend you to use a phased migration strategy. This means that you don't copy and migrate all projects in one go, but in segments so you can detect and fix any problems early in the process and not lose any data.
And to make that happen, you could use a plug-in such as Backbone Issue Sync for Jira.
Backbone can help you link and copy all Jira tickets and projects on one instance to the other. This also includes Jira data like issue status, comments, components, custom fields, etc. And you can get full control over the privacy and security of your instance and can configure access control to the Jira instances.
If you want to learn more about how the migration process works, my team can give you a free demo of the app and answer all your questions. Reach out to us at firstname.lastname@example.org.
Product Marketing Manager,
@Vivek Karnik hi there! ZigiOps can help you easily migrate data from one Jira instance to another (be it Jira Cloud, Service Management, or Server) without losing any valuable info. It allows customization so you can tweak it to migrate just the data you need (not all that's available) like attachments, comments, custom and default fields, statutes..
ZigiOps also allows you to control the level of security (which data is visible and to whom, and which is not). This helps with keeping the two instances (and their information) private to their users. Give it a look and if you're interested in learning how it can handle your use case in practice, do not hesitate to book a demo.
Regards, Diana (ZigiWave)
Thank you all for your inputs. I'll do a quick assessment of the various suggested products.