Talk to us
  • CASE STUDY | MEDICAL TECHNOLOGY / HEALTHCARE

Two Cloud sites merged into one. 5,800 issues migrated, zero data loss.

A global medical device company operating across 150+ countries consolidated a standalone engineering Atlassian Cloud site into its unified enterprise environment. Trundl migrated 4 Jira projects and 1 Confluence space using Atlassian Cloud Migration Assistants, completing the engagement within the 4-month fixed-bid window.

Talk to us
~5,800 issues migrated
4 Jira projects
1 Confluence spac
4 months Jan to Apr 2026
0 data loss
  • ON THIS PAGE
Industry Medical Technology / Healthcare
Solution Atlassian Cloud-to-Cloud Migration (JCMA / CCMA)
Scope 4 Jira projects, 1 Confluence space, ~5,800 issues
Timeline January to April 2026
Partner Tier Atlassian Platinum Solution Partner
Talk to us
  • THE CLIENT

Who is the client?

A global medical device company operating in over 150 countries needed to consolidate a standalone engineering Cloud instance into its enterprise Atlassian environment. As a highly regulated entity, maintaining data integrity and consistent governance across its software development lifecycle was critical to the project’s success.

  • THE BUSINESS CHALLENGE

Operational silos from a fragmented Atlassian footprint.

01

Operational Inefficiency

Managing separate users, permissions, and billing across two Cloud sites increased administrative burden.

02

Governance Gap

Consistent security policies and workflow standards were difficult to maintain across disparate Atlassian environments

03

Collaboration Barriers

Enterprise teams had limited visibility into the standalone engineering project data, hindering cross-functional work.

04

Compliance Requirements

As a regulated entity, maintaining data integrity throughout migration was non-negotiable.

  • PROJECT OBJECTIVES

One site. One standard. Full fidelity.

01

Consolidation

Merge 4 Jira projects and 1 Confluence space into the target enterprise site with full data fidelity.

02

Cost Reduction

Centralize licensing and eliminate redundant administration overhead

03

Governance

Implement a unified framework for issue types, workflows, and access management

04

Repeatability

Establish a validated migration methodology for future business unit integrations.

  • THE TRUNDL SOLUTION

A structured Cloud-to-Cloud migration methodology.

01

Environmental Analysis and Discovery

Mapped all configurations, identified app dependencies, and uncovered legacy group structures needing alignment with the organization's identity provider before any data moved.

02

Test Migration and UAT

Ran a full-scale test migration to validate the runbook, confirming data accuracy and functional parity with stakeholders before production execution.

03

Production Execution

Used Atlassian Cloud Migration Assistants (JCMA and CCMA) to migrate approximately 5,800 issues over a targeted weekend window, preserving history, attachments, and links.

04

Hypercare and Optimization

Resolved post-migration access issues and provisioned global partner teams within the enterprise security framework before closing the engagement.

  • DELIVERY HIGHLIGHTS
QUALITY Full fidelity

All 5,800 issues migrated with history, attachments, and cross-links intact. Immediate workflow standardization on arrival in the enterprise site.

TIME TO MARKET 4 months

January to April 2026. Completed on schedule and within the fixed-bid budget.

VALUE ADD One site, one standard

Centralized licensing, unified governance, and a repeatable migration framework ready for the next business unit integration.

  • FAQ

Frequently asked questions.

How was global vendor access managed during migration?

Trundl’s hypercare phase specifically addressed vendor provisioning, ensuring global partners were correctly configured within the enterprise identity framework before the standalone site was decommissioned.

Was Confluence included in the migration?

Yes. The relevant engineering documentation space was fully migrated, with pages correctly mapped to the enterprise Confluence environment.

How does this engagement serve as a template for future migrations?

Trundl documented the full runbook, UAT protocol, and post-migration validation steps so that future business unit migrations follow the same proven methodology without restarting discovery.