Cloud migration
From Atlassian Data Center to Cloud in 90 days: IPF International Limited migration story
Client
IPF International Limited
Industry
Finance
Technology
Jira Cloud
Outcome
Migration from Atlassian Data Center to Cloud in 3 months
Summary
Deviniti supported IPF International Limited in a Data Center to Cloud transformation delivered with Atlassian’s FastShift program. The project combined migration execution, scope optimization, data cleanup recommendations, plugin analysis, permission and account-management work, two test migrations, UAT support, production cutover, and post-migration enablement.
- The result was a cloud-native Jira and Confluence environment tailored to IPF International Limited’s needs, delivered within the target three-month migration window.
- The project also reduced the Marketplace app footprint from 37 apps to 15,
- introduced a dedicated Cloud setup,
- supported security improvements through SSO and 2FA coverage.
Client background
IPF International Limited operates in the financial services and consumer credit sector. Its Atlassian environment supported daily operational work across Jira and Confluence.
They needed one Enterprise Cloud foundation, clearer ownership of licensing and administration, and an environment that could support future governance decisions.
The challenge: cost, control, and continuity in one migration
Before the migration could start, Deviniti had to turn a complex Atlassian setup into a clear and safe Cloud migration plan.
- Fragmented platform ownership:
IPF International Limited operated across multiple separate Atlassian environments (one Cloud, two Data Center), which complicated licensing decisions, cost transparency, administration, and access governance. - Large configuration footprint:
The source environment included 117 projects, 588 custom fields, 147 workflows, and 35 permission schemes before migration. - Marketplace app complexity:
37 apps had to be assessed, with decisions needed on what to migrate, replace, retire, or troubleshoot. - Compressed validation window:
Two test migrations and UAT cycles had to be completed before production cutover. - Security and account considerations:
Internal users, external users, shared permissions, SSO, and 2FA all had to be reviewed as part of the Cloud operating model.
The problem: cost, control, and cloud readiness
The client needed to solve a business problem that many enterprise Atlassian customers recognize: how to reduce the total cost and complexity of multiple Atlassian environments, gain clearer ownership of licenses and administration, and consolidate daily work into one Enterprise Cloud environment without putting operations at risk.
- UAT complexity: two test migrations and two UAT sessions had to be run in a compressed schedule, creating parallel workstreams and potential confusion between sandboxes.
- Strict migration timeline: the FastShift model required the project to be completed within approximately three months.
- Budget pressure: the project scope and delivery model had to be adjusted to meet the client’s cost expectations.
- Plugin complexity: selected Marketplace apps required additional analysis, troubleshooting, and migration decisions.
- Permissions and accounts: shared permissions, accounts, external users, and authentication required careful coordination.
The solution
The project involved IPF International Limited stakeholders, Deviniti’s delivery and sales teams, Atlassian’s Cloud Migration Manager and Migration Support Engineers, and selected app vendors where needed.
Deviniti helped IPF International Limited reshape the migration into an outcome-oriented delivery plan. Instead of treating the project as a standard lift-and-shift, the team focused on reducing scope, simplifying the environment, and protecting the migration date.
The migration covered:
- Jira and Confluence migration assessment, planning, and execution support.
- Source-environment cleanup recommendations and migration-scope optimization.
- Marketplace app review, rationalization, and vendor coordination where needed.
- Two test migrations to validate the target Cloud environment before production cutover.
- UAT support to help business users confirm that migrated content, permissions, and workflows were ready.
- Account, permission, SSO, and external-user analysis for the Cloud target model.
- Production cutover support and post-migration enablement.
- Additional Jira and Confluence training sessions for users.
IPF International Limited needed a partner that could keep the migration moving even when scope, budget, technical constraints, and FastShift requirements had to be managed together.
“We needed a clear and controlled path to Cloud migration. Deviniti team helped us simplify where possible, address app and permission complexity, and keep the business moving with confidence throughout the transition.”
Delivery timeline
| Assessment and planning | 4 weeks | Understand the Data Center source environment and migration constraints. | Migration assessment, app review, user and permission analysis, and initial scope decisions. | Created a realistic migration path instead of carrying unnecessary complexity into Cloud. |
| Scope optimization and cleanup | 2 weeks | Reduce migration risk before test migrations. | Recommendations for cleanup across apps, projects, custom fields, workflows, and permission schemes. | Lowered technical debt and helped keep the project aligned with the three-month window. |
| Test migrations and UAT | 8 weeks | Validate Cloud readiness with business users. | Two test migrations, UAT support, issue analysis, and sandbox validation. | Reduced cutover uncertainty and gave stakeholders evidence before production migration. |
| Production cutover | 3 days | Move Jira and Confluence into the dedicated Cloud environment. | Production migration support, access validation, app follow-up, and post-migration checks. | Delivered the dedicated Cloud platform within the target FastShift window. |
| Enablement | 2 weeks | Help users adopt the new Cloud environment. | Jira and Confluence training sessions and post-migration support. | Helped users transition from the old Data Center model to Cloud ways of working. |
Business impact: a dedicated Cloud foundation
By the end of the project, IPF International Limited had one Enterprise Cloud environment, a smaller app footprint, clearer licensing ownership, and a cleaner configuration baseline.
The migration also gave IPF International Limited a stronger foundation for future Atlassian governance. The company can now make Cloud roadmap, access, licensing, and administration decisions around one Enterprise Cloud platform aligned with its own needs.
| Improvement area | Before migration | After migration | Business value |
|---|---|---|---|
| Platform model | One Cloud and two Data Center environments before consolidation | Independent Atlassian Cloud environment tailored to IPF International Limited’s scope | More control over ownership, governance, administration, and future roadmap decisions. |
| Migration timeline | FastShift migration had to fit a strict three-month delivery window | Migration delivered within the target three-month window | Modernization achieved without a long, open-ended transformation program. |
| Marketplace app footprint | 37 Marketplace apps in the landscape. | 15 Marketplace apps after rationalization | 22 fewer apps to manage, assess, migrate, and maintain. |
| Jira custom fields | 588 custom fields | 414 custom fields | 174 fewer custom fields, supporting a cleaner and easier-to-govern Jira configuration. |
| Workflows | 147 workflows, all active | 136 workflows, including 132 active workflows | 11 fewer workflows overall and 15 fewer active workflows to maintain. |
| Projects | 117 projects, including 23 dead or inactive projects | 67 projects, including 10 dead or inactive projects. | 50 fewer projects overall and 13 fewer inactive projects carried into the new environment. |
| Permission schemes | 35 permission schemes | 20 permission schemes. | 15 fewer schemes, reducing access-management complexity. |
| Licensing | Jira and Confluence operated across one Cloud and two Data Center environments before consolidation. | Jira: 1678 / 1800 users. Confluence: 944 / 1000 users. Jira user tier limit reduced by 200 | Dedicated Cloud setup with a more right-sized Jira tier and clearer budget ownership. |
| Security and access | Shared permissions, accounts, and external users required additional analysis | ADFS SSO for users with company email and daily email 2FA for external users | More consistent access control and stronger authentication coverage. |
| Business continuity | High-pressure production cutover with business risk | Target KPI: zero critical downtime during cutover. Final confirmation still required | A controlled transition path designed to protect users and daily operations. |
“The project was successful because both teams stayed focused on the same goal: delivering a Cloud environment that worked for IPF International Limited’s needs, not just completing a technical migration.”
Goals and success metrics
| Business goal | Real outcome |
|---|---|
| Reduce Total Cost of Ownership | IPF International Limited improved its operating model by moving to Atlassian Cloud, rationalizing apps, simplifying administration, and establishing cleaner ways of working. |
| Optimize licensing and budget ownership | Jira moved from a 2000-user tier to an 1800-user tier, while IPF International Limited gained clearer ownership of licensing decisions in Cloud. |
| Modernize daily work in Atlassian Cloud | The migration created an Atlassian Cloud foundation tailored to IPF International Limited’s processes, users, security model, and future growth. |
| Deliver transformation within a strict timeline | Deviniti adjusted the delivery model, narrowed scope with the client, and supported two test migrations and UAT cycles to protect the final cutover date. |
| Protect business continuity and adoption | IPF International Limited maintained business continuity during production cutover and achieved strong user adoption after migration. |
