# Jira Migration Readiness Checklist: 50 Items to Audit Before Cloud Migration Migrating Jira from Data Center to Cloud is not a simple lift-and-shift. Years of configuration have created complexity that can break your migration if not addressed beforehand. This checklist covers 50 critical items to audit before you begin. ## Why Use This Checklist Atlassian's Data Center end-of-life in March 2029 means every enterprise must migrate. But rushing without proper preparation leads to: - **Failed migrations** when incompatible configurations are encountered - **Data loss** when custom fields don't map correctly - **Performance issues** when unused configurations slow down Cloud - **Compliance gaps** when permissions aren't properly migrated MigrationMonitor automates many of these checks, but this checklist provides the complete picture. --- ## Custom Fields (12 Items) - [ ] **1. Inventory all custom fields** - Document every custom field in your instance - [ ] **2. Identify unused fields** - Fields with zero screen assignments can be deleted - [ ] **3. Check ScriptRunner dependencies** - Fields created by ScriptRunner need special handling - [ ] **4. Review field types** - Some DC field types don't exist in Cloud - [ ] **5. Check field contexts** - Understand which projects use each field - [ ] **6. Review screen schemes** - Map fields to screens for migration - [ ] **7. Identify duplicate fields** - Merge similar fields before migration - [ ] **8. Check field descriptions** - Add descriptions for fields that will migrate - [ ] **9. Review field configurations** - Understand default values and requirements - [ ] **10. Check custom field keys** - Document customfield_XXXXX identifiers - [ ] **11. Review field usage trends** - Fields used rarely may not need migration - [ ] **12. Plan field cleanup** - Create a cleanup schedule before migration ## Workflows (8 Items) - [ ] **13. Inventory all workflows** - Document every workflow in your instance - [ ] **14. Check workflow complexity** - Workflows with many transitions need attention - [ ] **15. Review workflow conditions** - Some DC conditions don't exist in Cloud - [ ] **16. Check workflow validators** - Map DC validators to Cloud equivalents - [ ] **17. Review workflow post-functions** - Some DC post-functions need Cloud alternatives - [ ] **18. Check workflow permissions** - Understand who can execute transitions - [ ] **19. Review workflow descriptions** - Add documentation for complex workflows - [ ] **20. Identify inactive workflows** - Workflows not assigned to projects can be archived ## Projects (7 Items) - [ ] **21. Inventory all projects** - Document every project in your instance - [ ] **22. Identify dead projects** - Projects with no recent activity - [ ] **23. Check project ownership** - Ensure every project has a lead - [ ] **24. Review project categories** - Organize projects for migration waves - [ ] **25. Check project schemas** - Understand issue type schemes per project - [ ] **26. Review project permissions** - Map project-level permissions - [ ] **27. Check project components** - Components with no issues may be archived ## Permissions (8 Items) - [ ] **28. Inventory permission schemes** - Document all permission schemes - [ ] **29. Check scheme assignments** - Which projects use which schemes - [ ] **30. Review global permissions** - Understand instance-wide access - [ ] **31. Check role memberships** - Review project role assignments - [ ] **32. Review group memberships** - Clean up unused groups - [ ] **33. Check anonymous access** - Ensure anonymous access is configured correctly - [ ] **34. Review permission conflicts** - Identify overlapping permissions - [ ] **35. Check scheme descriptions** - Add documentation for each scheme ## Issue Types (5 Items) - [ ] **36. Inventory issue type schemes** - Document all schemes - [ ] **37. Check sub-task types** - Sub-task configuration differs between DC and Cloud - [ ] **38. Review issue type hierarchy** - Understand parent-child relationships - [ ] **39. Check issue type icons** - Custom icons need to be migrated - [ ] **40. Review issue type descriptions** - Add documentation ## Notifications (4 Items) - [ ] **41. Review notification schemes** - Document all schemes - [ ] **42. Check notification recipients** - Understand who gets notified - [ ] **43. Review custom notifications** - Custom notification templates need migration - [ ] **44. Check notification timing** - Immediate vs. scheduled notifications ## Automation (3 Items) - [ ] **45. Inventory automation rules** - Document all DC automation - [ ] **46. Check automation triggers** - Some DC triggers differ in Cloud - [ ] **47. Review automation actions** - Map DC actions to Cloud equivalents ## Integrations (3 Items) - [ ] **48. Inventory Marketplace apps** - Check which apps are Cloud-compatible - [ ] **49. Review API integrations** - External systems connecting to Jira - [ ] **50. Check webhook configurations** - Webhooks need to be recreated in Cloud --- ## How MigrationMonitor Helps MigrationMonitor automates checks for items 1-12, 13-20, 21-27, and 28-35. Our app provides: - **Automated inventory** of custom fields, workflows, projects, and permissions - **Complexity scoring** for workflows and fields - **Usage analysis** to identify unused configurations - **Change tracking** across migration waves - **Export reports** for stakeholder sign-off **[Try MigrationMonitor Free](/migration-monitor/)** - Run your first scan in minutes and see exactly what needs attention. --- ## Next Steps 1. **Install MigrationMonitor** from the Atlassian Marketplace 2. **Run your first scan** to get automated results for most checklist items 3. **Review the gaps** - Use this checklist for items the app doesn't cover 4. **Create a cleanup plan** - Prioritize high-risk items 5. **Schedule migration waves** - Use snapshots to track progress The best time to start preparing is now. Don't wait until 2028. --- *MigrationMonitor is a Jira Cloud Forge app that provides migration readiness analysis and change tracking. It helps enterprises quantify migration risk, identify cleanup opportunities, and track configuration changes across migration waves.*