With Jira Data Center nearing its end of life (okay, it’s still a bit far off, but 2029 will creep up on us), many teams are gearing up for the move to Jira Cloud. Just like with Server’s EOL, it raises the same question: What’s the best way to migrate to Jira Cloud?
A one-time push using the lift-and-shift method can be fast, and it’s actually the approach Atlassian recommends. But it also leaves plenty of room for surprises - downtime, missing and unnecessary data, and users trying to adjust all at once.
A phased migration, on the other hand, takes a different approach. Moving project by project while running DC and Cloud in parallel gives teams room to test, adapt, and build confidence before tackling the next step. It feels more predictable and under control.
If you want to dive deeper, check out our previous article exploring phased migration in detail, titled “Jira Cloud Migration Giving You Nightmares? Rest Easy by Moving in Phases.”
But here’s what we’re curious about.
Running Cloud and Data Center side by side during a phased move can get tricky. Some work shifts to Cloud early, some stays on-premise, and people start asking, “Where’s the latest version of this work item?” (or do you still call them issues?)
Many teams build temporary workflows, others lean on automation, and others find creative ways to keep both sides aligned. Everyone seems to approach the challenge a little differently.
Share your experience in the comments - we’re genuinely curious how you're approaching this, especially if you're using a phased migration approach. And if you want to go deeper, we’re hosting a live session to dig into the big questions:
How teams are choosing between migration strategies, what’s working, where the pain points are, and where apps like Backbone Work Sync fit into the picture.
If you’re planning your own move - or already in the middle of one - we’d love to have you join and share your thoughts.
RSVP here for free →
Umer Sohail _K15t_
Product Marketing Manager
K15t
Germany
1 accepted answer
0 comments