DC to Cloud and Cloud to Cloud, plus the audit that proves it worked.
A migration that reports success is not the same as a migration that worked. Filters arrive pointing at fields that no longer exist. Automation rules arrive enabled and scoped to the wrong project, and Jira quietly rewrites the trigger so a source-to-target diff passes. Attachment downloads redirect somewhere your script does not follow. None of it shows up in the migration report.
Two series run through this hub. Atlassian Migrations is the planning half, in order, and it spends most of its time on the work nobody is paid to do before the cutover. Auditing a Migration is the other half — what to run afterwards to find the damage while you still have the source system to compare against.
The end-to-end path of a Data-Center-to-Cloud move, in the order the problems actually arrive.
What to re-count on the far side, and the four places a migration reports success while something is quietly broken.