Anonymized customer story · Atlassian Cloud migration
Move a large Data Center platform to Cloud without losing control
Ovyka has delivered Atlassian Cloud migrations for major French companies with subsidiaries and teams around the world. Platforms combined Jira, Confluence and Jira Service Management, with more than 1,000 users in some environments and several hundred projects to assess, transform and secure.
- Products
- Jira, Confluence and Jira Service Management
- Scale
- More than 1,000 users and several hundred projects on some platforms
- Organization
- Major French companies with global subsidiaries and teams
- Timelines
- From two weeks to more than three months, using migration waves
Starting point
A migration affecting an entire system of work
These platforms had become shared foundations for delivery, support, documentation, coordination and control. Their value came from data as much as from workflows, permissions, apps, integrations and practices built over time.
The challenge was not to move projects and spaces mechanically. It was to decide what to retain, simplify, transform or retire, then organize a migration compatible with the operating constraints of subsidiaries across several time zones.
Volume and scope
Assess more than 1,000 users in some environments, several hundred projects, Confluence spaces, histories, attachments and content to archive.
Heterogeneous apps
Some apps offered an automated migration path; others required specific extraction, transformation or recovery operations.
Identity and security
Prepare accounts, groups, domains, SSO, external access and ownership without weakening teams during cutover.
Global continuity
Plan freezes, tests, waves, cutovers, controls and hypercare around subsidiaries and critical activities.
Ovyka approach
Turn every unknown into a testable decision
The method was adapted to each platform’s scale and complexity. Some targeted migrations were completed in two weeks; the most structural programmes ran for more than three months with progressive waves, team enablement and regular validation of user feedback.
- 01
Map the platform
Inventory products, users, projects, spaces, data, apps, integrations, identities and sensitive uses.
- Dependency map
- Volumes and owners
- Candidate scope and exclusions
- 02
Design the Cloud target
Decide between like-for-like migration, rationalization, replacement or retirement and define future platform standards.
- Target principles
- App and integration decisions
- Security and governance rules
- 03
Prepare and rehearse
Clean data, handle gaps, execute automated paths and transformation operations, then test critical journeys.
- Remediation backlog
- Test sets and rehearsals
- Go/no-go criteria
- 04
Migrate in waves and stabilize
Move projects or spaces progressively, support teams, gather feedback and correct gaps before following waves.
- Cutover runbooks
- Completeness controls
- Hypercare and team handover
Solution principles
Migrate less debt and more control
The Cloud target was not treated as a technical copy of Data Center. Decisions preserved critical use while reducing debt, standardizing where useful and preparing sustainable governance.
Rationalize before transfer
Archive low-value content, reduce redundant configuration and clarify ownership.
Two app strategies
Use automated migration paths when reliable; implement specific transformations when data or functions could not be transferred directly.
Journey-based tests
Validate end-to-end operations beyond basic data-presence checks.
Team-aware waves
Move spaces and projects progressively to limit risk, support users and incorporate their feedback.
Cloud governance in the target
Prepare roles, standards, change, access reviews and operations before go-live.
User-oriented stabilization
Provide enhanced support, rapid gap analysis and guidance on Data Center versus Cloud differences.
Outcomes
Risk-adjusted migrations, from targeted work to international programmes
Success was assessed through continuity of critical journeys, the quality of team feedback, control of dependencies and the ability to operate the Cloud target sustainably.
Context-driven schedule
Targeted migrations were completed in two weeks; the most complex platforms followed a path lasting more than three months.
Controlled dependencies
Automatable apps and specific transformations were identified and tested before production.
Supported adoption
Waves produced positive feedback and allowed the path to be adjusted with the teams involved.
More governable platform
Migration created leverage to rationalize debt and install sustainable Cloud standards.
Ovyka
Does your Data Center platform need to move to Cloud?
Share the products, volumes, apps and timing constraints. We will help build a controlled path.