...
Extended Migration Time: Snapshot creation and deployment times are taking significantly longer than expected.
High Resource Utilization: Despite using high-tier compute resources, migration processes consume considerable time, especially during the snapshot creation and deployment phases.
Re-indexing Delays: The re-indexing process, particularly after deployment, adds additional time to the overall migration. For a large number of projects and issues, it is recommended to check the box “Do not perform re-indexing during the deployment” to skip the re-indexing process after the issue data is imported. The deployment time will be considerably reduced, but re-indexing will need to be manually triggered afterwards.
Network and Storage Concerns: Possible network or storage latency issues could affect performance-based deployments.
...
Skip Re-indexing During Deployment: To reduce time, skip re-indexing during deployment. Re-indexing can be performed manually after the data import is complete, as per the guidelines here..
For many projects and issues, it is recommended to check the box “Do not perform re-indexing during the deployment” to skip the re-indexing process after the issue data is imported. The deployment time will be considerably reduced, but re-indexing must be manually triggered afterward.Increase Compute Resources: Although already using high-tier resources, consider deploying a dedicated node in the Jira Data Center cluster exclusively for CMJ operations. This setup can isolate CMJ processes and potentially reduce bottlenecks caused by shared resources.
...
Automate the Migration Process: Utilize CMJ's REST API to automate repetitive tasks such as issue key extraction, chunking, and snapshot creation. More information on automating these tasks can be found in REST API Automation.
Conclusion
Migrating large Jira instances within a limited time frame is challenging but manageable with proper planning and optimization. The migration time can be significantly reduced by excluding attachments from snapshots, chunking the migration, skipping re-indexing, optimizing storage and network configurations, and leveraging automation. Implementing these best practices will help ensure a smoother and faster migration process.
...