Atlassian Cloud Migration Checklist for Jira & Confluence
A practical checklist for planning Jira and Confluence Data Center to Cloud or Cloud-to-Cloud migration.
1. Inventory the environment
List Jira projects, Confluence spaces, users, groups, authentication, Marketplace apps, integrations, automation, custom scripts and reporting dependencies.
2. Assess configuration debt
Identify duplicate fields, unused workflows, permission complexity and stale content. Do not migrate technical debt blindly when it can be simplified first.
3. Review Marketplace apps
Confirm cloud availability, data-migration options, functional differences, licensing and replacement options for every critical app.
4. Map identity and permissions
Define users, groups, managed accounts, authentication and permission mappings in the target environment.
5. Test integrations
Document APIs, webhooks, scripts and external systems, then test authentication, endpoints, data mapping and error handling in the target.
6. Define test cycles
Use representative projects and spaces, validate business-critical workflows and record acceptance criteria before production cutover.
7. Build the cutover runbook
Document freeze windows, final migration steps, validation owners, rollback decisions, communications and post-launch support.
8. Plan post-migration optimization
Cloud migration should end with governance, admin training and cleanup — not simply a successful data transfer.