Migration is hard. There's no getting around that. The good news is that most problems are predictable and solvable with the right approach. I've done this enough times to know where things go wrong and how to avoid the common pitfalls.
Atlassian has announced that Data Center will reach end-of-life in March 2029. For most organizations, this isn't a question of "if" you migrate—it's a question of "when" and "how."
The timeline might seem distant, but migrations at scale take time. Large enterprises typically need 12-16 months from start to finish, and that's when things go smoothly. When they don't, you're looking at significant delays and unexpected costs.
March 30, 2026
No new Data Center licenses for new customers
March 30, 2028
End of license sales for existing customers
March 28, 2029
Data Center becomes read-only
According to industry research, nearly half of cloud migrations fail to achieve their objectives.
Most organizations underestimate the complexity and resource requirements.
Cloud licenses typically cost more than Data Center, especially at scale.
Typical timeframe when everything goes according to plan.
The good news is that most failures are predictable. With proper planning and experience, you can avoid the common pitfalls.
This isn't about finding a vendor who promises it will be easy. It's about finding someone who's done it before and knows what to expect.
Most migration failures aren't due to technical limitations. They're due to predictable mistakes that organizations make over and over again.
Rushing into migration without comprehensive assessment leads to data loss, application downtime, and user dissatisfaction.
Many Data Center Marketplace apps don't have Cloud equivalents. Discovering this mid-migration forces costly workarounds or rollbacks.
Wrong data residency choices, missing audit logs, and misconfigured IAM policies lead to regulatory fines and security breaches.
Underestimating data volume, network bandwidth, or complexity leads to incomplete migrations and data corruption.
Failing to document and replicate custom workflows, scripts, and configurations causes process disruptions post-migration.
Poor communication and training leads to employee resistance, reduced productivity, and failed adoption.
European Enterprise
Faced GDPR fines after migrating to non-compliant data residency region.
Global Tech Company
Lost 12 hours productivity due to legacy SSO configuration issues during migration.
Financial Services Firm
Rolled back migration after discovering compliance app wasn't cloud-ready.
Healthcare Provider
Failed HIPAA audit after not enabling audit logging in Cloud.
Different organizations face different challenges. I've worked across all migration scenarios.
Moving from self-hosted Data Center or Server instances to Atlassian Cloud. This is the most common migration type as organizations respond to the Data Center EOL.
Merging multiple Cloud instances, typically after mergers, acquisitions, or organizational restructuring. More complex than it initially appears.
Migrating from other project management platforms like Monday, Trello, or Asana to Jira. Often involves significant data mapping and workflow re-engineering.
These aren't just numbers on a slide. Each project came with its own set of challenges and required creative problem-solving.
9,500 Users - UBS
Full Jira/Confluence/Bitbucket migration with zero downtime. Global financial institution with complex compliance requirements across multiple regions.
8,500 Users - SolarEdge
EMEA-wide migration with embedded compliance for privacy regulations. Required careful data residency planning and extensive stakeholder communication.
1,200 Users - McLaren
Cloud-to-cloud consolidation following organizational restructuring. Merged multiple instances into unified environment while maintaining operational continuity.
1,200 Users - Aer Lingus
Advanced automation implementation reducing manual admin workload by 60%. Focused on ScriptRunner customizations and API-driven workflows.
800 Users - Zyter
JSM adoption replacing Salesforce. Improved service efficiency through better integration with existing healthcare workflows.
400 Users - Netcentric
Seamless cloud transition with performance optimization for distributed teams across multiple time zones.
1,800 Users - Diconium
CMDB and Assets implementation and migration for a digital transformation company within the Volkswagen Group ecosystem. Complex configuration management across distributed teams.
38,000 Users - OpenBet
Dual instance migration plus Bitbucket from on-premises to cloud. Complex multi-platform migration involving legacy systems, high-availability requirements, and extensive user coordination across the organization.
250 Users - ABSLBS
Confluence migration completed, Jira migration currently in progress. Focused on clean data transfer and minimal disruption to daily workflows.
Migrations require a specific set of skills. I've developed expertise across the Atlassian ecosystem through years of hands-on experience.
For regulated industries, compliance isn't optional. Security isn't a nice-to-have. These are non-negotiable requirements that must be addressed from day one.
Migration isn't just a technical project. It's a business transformation that affects how teams work every day.
Eliminate dedicated DevOps overhead for on-prem infrastructure. Reduce maintenance burden and free up resources for innovation.
Reduction in admin workload
Access to Atlassian Intelligence (AI), new features, and integrations that only ship to Cloud. Stay ahead of the curve.
Cloud features released in 2024
Enterprise-grade security features, compliance certifications, and automated security updates. Focus on your business, not security patching.
Of customers on Cloud
I won't tell you migration is easy or that everything will be perfect. I've been in the trenches when things go wrong.
But I will tell you that with proper planning, realistic expectations, and experience to draw from, migrations can succeed. The organizations I've worked with are now operating in Cloud and benefitting from the platform's capabilities.
Migration is hard, but you don't have to do it alone.
Migration doesn't have to disrupt your business. With the right expertise, it becomes an opportunity to optimize and modernize your Atlassian ecosystem.
I don't work with everyone. I focus on organizations where I can make a meaningful difference.
You need more than a migration tool vendor
Atlassian provides migration assistants. What you need is someone who's used them in production and knows their limitations.
You have complex requirements
Regulated industries, large user counts, custom integrations, strict compliance requirements. These aren't edge cases—they're what I specialize in.
You value experience over marketing
I'm not trying to sell you on Cloud. I'm helping you get there with minimal disruption and maximum success.
You're willing to invest in doing it right
Proper planning takes time. Rushing migration saves weeks upfront and costs months later.
The best way to understand what migration looks like for your organization is to have a conversation. No sales pitch, no pressure. Just a discussion about your situation and whether I can help.
Or join the community and ask questions about your migration challenges.