...
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 be affecting the performance of Azure Kubernetes Service (AKS) based deployments.
...
Exclude Attachments from Snapshots: Given the large size of attachments, exclude them from the snapshot. Instead, migrate attachments separately, following best practices outlined in the Move Attachments.
Chunking the Migration: Instead of migrating the entire instance simultaneously, divide the data into smaller, manageable chunks. For example, split the projects into groups based on issue volume and migrate them sequentially. While not faster, this approach makes the process more manageable and allows partial completion within a weekend. Detailed guidance on chunking can be found in the CMJ documentation How to deal with big snapshot deployments to optimize performance.
2. Improving Performance and Reducing Re-indexing Time
...
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 here 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.
...