Two enterprise Atlassian consolidations delivered at a US managed service provider, a year apart.

2025, an acquisition. The acquired company's Jira Cloud instance moved into the parent organisation's 2,000-seat enterprise tenant. 83,722 issues landed in one production cutover window, recorded as SUCCESS and confirmed by the vendor's own post-migration reports rather than by a progress note alone. The runbook was designed and proved across four sandbox rehearsals before production, covering migration plan configuration, project-key remapping, permission, notification and role scheme teardown, and identity remapping with review of every account flagged as needing attention. It was then executed unchanged at cutover. The client called the execution smooth and the delivery on time.

2024, a consolidation of two estates into one cloud organisation over 3.5 months as sole delivery engineer, 224.66 of the project's 260.16 hours delivered personally. The Jira half could not use the vendor's supported tool, which proved unusable against the source instance, so the path was engineered by hand: 133,331 issues moved off an unsupported on-premises Jira Server, 126,150 in the larger project across 24 chunks and 7,181 in the smaller one, with Python CSV preprocessing, attachments extracted in bulk and staged in S3 and their URLs rewritten inside the import files. Each of the 24 chunks needed its own field mapping and every one was tracked to closure across three reimport passes for issue links, parent issue ID and example links. The Confluence half moved 25,790 objects across 132 spaces with no partial loss in the vendor's report.

Honest limits, and on a migration they matter more than anywhere. Neither of these is called clean, complete, flawless or lossless. The 2025 vendor reports record 2,100 in-scope issues not migrated in one project with no reason given, and 66,393 of 1,683,860 entities not migrated in production against 23 in the final rehearsal, mostly change history, parent links, comments and watchers. 133,331 is a count of issue keys prepared and loaded, not a destination-side reconciliation, so it is written as migrated and never as verified in the destination. Zero reported loss on Confluence measures the vendor's copy operation and not what the estate was like to use afterwards: the same record carries three weeks of post-migration remediation for broken links, duplicate personal spaces, page ownership and permissions, and the two belong in the same sentence. 98 of those 132 spaces are personal spaces, so 132 spaces is not 132 team wikis. Decommissioning of the old instances was still pending at the close of the 2024 engagement. On the 2025 cutover a second engineer was resourced on the export and relink work, so the claim there is led, never sole.