Hi @Dharani Dharan D
Just to add to the helpful responses above. Since this is a Cloud to Cloud move in Jira Cloud, the Jira Cloud Migration Assistant usually doesn’t come into the picture. The Assistant is mainly used when teams are moving from Server or Data Center into Cloud. For Cloud-to-Cloud migrations, the data copy guidance mentioned in the earlier replies is generally the starting point.
A few additional things that may be useful to keep in mind while planning the move:
- Clarify the migration scope: Decide whether the entire site needs to move or only certain projects.
- Plan a controlled migration window: Many teams schedule the transfer during a maintenance window so they can review the copied data before users begin working in the new site.
- Check user and identity setup: Users should exist in the destination site, so issue history, comments, and activity attribution stay accurate.
- Review apps and configurations: Marketplace apps, automation rules, and integrations often need to be installed and configured again in the target environment.
- Validate the copied data: It helps to confirm issue counts, attachments, comments, and workflows after the transfer.
If more flexibility is needed, such as project-level transfers or preserving detailed issue history, then OpsHub Migration Manager (OMM) is worth checking. It supports phased or full migrations, preserves comments, attachments, relationships, and field mappings, and is designed to move data with no downtime, no disruption, and no data loss.
All the best!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.