Client transformation
Moving a large Atlassian Data Center platform to Cloud
Lessons from large-scale Atlassian migrations, from the Data Center inventory through Cloud stabilisation.
- Status
- Completed
- Period
- Several migrations, from 2 weeks to more than 3 months
- Ovyka contribution
- Scoping, preparation, migration rehearsals, cutover and hypercare depending on scope
Ovyka has supported major French companies and their international teams across Jira, Confluence and Jira Service Management transformation programmes. This experience ranges from complete Cloud migrations involving more than 1,000 users to supporting part of the Cloud migration of a Data Center platform serving 15,000 users.
At this scale, the challenge goes beyond technical transfer: a platform used for several years is a complete system of work. Its data matters, but so do its workflows, permissions, apps, integrations and user practices.
Decide before moving
An inventory makes dependencies visible: projects and spaces, data, apps, identities, integrations, owners and critical use cases. It then becomes possible to decide what should be retained, rationalised, transformed or retired.
A Cloud target gains nothing from reproducing all the debt accumulated in Data Center. Standards, responsibilities, security and the future governance model need to be part of its definition from the outset.
Turn unknowns into verifiable decisions
Ovyka’s published approach connects several complementary stages:
- map the platform and its dependencies;
- define the target and decide how to handle each app or integration;
- clean and transform data, rehearse migrations and test critical business journeys;
- cut over in waves, check completeness and stabilise through hypercare.
Rehearsals do more than measure transfer time. They test decisions, reveal gaps and produce a runbook that business and technical teams can both understand.
A path proportionate to risk
The published work ranges from two weeks for targeted environments to more than three months for the most structural programmes. What must remain constant is not the timeline, but the continuity of critical journeys, control of dependencies and the ability to operate the target sustainably.
This method also informs how to move to Cloud without moving all the debt. The full case published by Ovyka (s’ouvre dans un nouvel onglet) (opens in a new tab) presents several situations, the approach and observed outcomes.