Cloning an Entire Site to Another Site
Pre-Migration Steps Required for Destination Site - Before migrating your entire site, certain preparatory steps need to be completed on the destination site to ensure a smooth and successful migration.
These steps include:
Setting Up Required Configurations – Ensure that necessary user roles, permissions, and configurations are in place.
Users - Make sure that all the users are same as source site.
Groups - Make sure all the groups are same as source site.
Sub-tasks - Sub-tasks should be enabled on destination site.
Hierarchy levels of issue types should be consistent on source and destination site.
Install Required Apps & Dependencies – If third-party apps are involved, they need to be installed and configured before data migration.
Example: Atlassian plugins ( Tempo, Scriptrunner, JWME etc) on destination site.
Creating a Backup of Existing Data – We recommend taking a full backup of the destination site to avoid any potential data loss.
What you want to do?Restore bulk issues or Granular restore of issues on another site- Configuration of source and destination project should be same.
Issue types in issue type scheme
Fields in screens
Workflows
Permission scheme
Field configuration
Clone all the Configurations on another site
Clone all configurations with the help of Jira configuration clone feature.
Clone all the projects on another site
Clone all the projects using Project clone feature.
Once these steps are completed, you can proceed with the full site migration.