Discover our story, vision, and impact.

By Role

DevOps Leaders

Accelerate delivery with clear insights

By Initiative

By Domain

The Coming Divide in Defense: Federation or Fallout Under DoDI 5000.97

Share: The defense industry is entering a pivotal phase of transformation. With the release of DoDI 5000.97, the U.S. Department of Defense (DoD) has made

Case Study

How a Global Supply Chain Leader Migrated from Jira Data Center to Jira Cloud without Slowing a Single Business Day

The Business Challenge

Client: A global leader in supply chain and logistics

Industry: Logistics, warehousing, multi-region transport operations

Team Size: 10,000+ Jira users across product, engineering, QA, support, and compliance

Instance Complexity: 2800+ Jira Data Center projects, 300K+ issues, 3M+ change events

As part of its enterprise-wide modernization initiative, the client needed to migrate from a legacy Jira Data Center (DC) instance to Jira Cloud – without disrupting global operations, ongoing releases, or SLA-driven support teams.

All this, with zero tolerance for:

Defects

0 K+

Requirements

0 K+

Test Cases

0 K+

Artifacts

0 K+

What the Client Needed

Ensure uninterrupted operations

Teams needed to keep working in Jira DC – planning, developing, resolving issues – even while data was being migrated in the background. No disruption to sprints. No access delays. No user rework.

Guarantee full-fidelity migration – beyond just issues

Everything had to come across:

Standard + custom issue types (including test cases, features, epics, subtasks)
Attachments, comments, changelogs, story points, custom field values
Sprint history, release versions, workflows, SLAs, and labels
Cross-project references and issue links
Data from add-ons like XRay and JSM

Adapt and transform data on the fly

The Jira Cloud target used newer field templates, statuses, and workflows. The migration needed to:

Preserve auditability while masking PII

Several legacy Jira projects contained embedded PII in descriptions, custom fields, and comments. The client needed:

Keep source and target environments in sync

Since teams were split – some already piloting Jira Cloud, others still on DC – the solution leveraged OpsHub’s patented reverse sync technology to:

Marketplace tools and internal scripts couldn’t handle these conditions. They lacked:

That’s where OpsHub stepped in.

OpsHub’s Migration Strategy: For a risk-free Jira Data Center to Jira Cloud migration

In high-stakes migrations like this one, OpsHub doesn’t apply a one-size-fits-all approach. Instead, based on data sensitivity, compliance needs, and timeline constraints, the right migration strategy is selected per project set.

For this client, OpsHub used a combination of Full History and History without Impersonation – allowing the migration to balance:

Below is a snapshot of OpsHub’s three-tiered migration strategies:

Migration Approach	History Preserved	Author Attribution	Issue Key Retention	Comments Handling	Complexity	Use Case
Current State Migration	❌	Service account	❌	✅Preserved in body, not metadata	Low	Fast migrations, Limited audit requirements
History w/o Impersonation	✅(via custom fields)	Service account	✅(custom field only)	✅Preserved in body with original metadata	Moderate	For semi regulated industries
Full History Migration	✅	Original user + date	✅	✅Fully migrated with source metadata intact	High	Compliance-driven, audit-critical

For projects with strict audit and traceability requirements – including QA, compliance, and support functions – OpsHub applied it’s patented Live++ migration approach, which included Full History Migration to retain every field change, comment, and transition with original issue id, history, user attribution and timestamps intact.

The OpsHub Solution

To meet the client’s mandate – move hundreds of Jira projects from Data Center to Cloud without pausing development, compromising compliance, or breaking reference integrity – OpsHub implemented its patented Live++ data migration approach tailored for high-velocity enterprise environments.

At the heart of this approach was OpsHub Migration Manager (OMM), which enabled:

Active Migration Without Handcuffing DC Users

Throughout the migration window, Jira DC users continued using the system as they always had – creating issues, editing them, deleting unwanted tickets, and even reorganizing items across issue types and projects.

OpsHub’s migration platform tracked these changes in real time, ensuring that the Cloud environment always reflected the latest structure and activity – no conflicts, no manual rework.

Zero Downtime, Zero Service Disruption

There was no freeze window.

No users were logged out.
No support SLAs were missed.
Sprints continued. Releases shipped. Teams never paused - not even during cutover.
Cross-project references and issue links
Data from add-ons like XRay and JSM

Full-Fidelity Data Migration - with Add-On and History Preservation

OpsHub migrated more than just issues. The entire Jira DC context was rebuilt in Cloud – including:

Complete change history with every status transition, field change, and user action
Inline images, user mentions, and issue mentions - automatically transformed into Cloud-safe references with no deadlinks to the old DC URLs
Data from XRAY and JSM - moved at the entity level, not just as attachments
Comments, attachments, labels, issue links, versions, and sprint data - preserved and restructured for Cloud

On-the-Fly fields template transformation

Jira Cloud’s stricter validation model meant several legacy DC artifacts couldn’t be migrated 1:1.

OpsHub’s mapping engine handled:

Field template mismatches
Custom status and resolution mappings
Incompatible workflows (e.g., loops, transitions with invalid validators)
Cloud restrictions like “no issues in closed sprints”
Remapping user mentions from legacy domain aliases to current accounts

All of this was done without manual intervention – ensuring correctness at scale.

Reverse Sync for Coexistence and Reporting Stability

With reporting pipelines and customer service dashboards still pointing to DC, the client couldn’t afford inconsistent or incomplete data mid-migration. OpsHub enabled reverse sync, continuously mirroring Jira Cloud changes back to DC to:

How did we migrate Jira DC to Jira cloud?

Phase 1: Discovery & Migration Blueprint

Audited 2800+ projects, dependencies, and 100s of custom fields/workflows
Mapped legacy domains (@company.local → @company.com)
Assessed gaps across add-ons (XRAY, JSM, R4J) and Cloud equivalents
Identified PII risks embedded in fields/comments
Built precise field, user, and workflow mapping aligned with Jira Cloud architecture

Phase 2: Dry Runs & Staging Validation

Phase 3: Pilot Migration (400 Projects)

Phase 4: Production Rollout – Wave 1 (800 Projects)

Phase 5: Production Rollout – Wave 2 (1200 Projects)

Phase 6: Final Migration (400 Projects) + Stabilization

Results & Business Impact

Zero impact on engineering velocity - no sprint pauses, no access disruption, no SLA breaches
100% data fidelity - including sprint data, issue history, attachments, links, user mentions, and preserved issue IDs
Pll-safe, compliance-ready cloud transition - with inline redaction, audit logs, and traceability across all migrated projects

OpsHub delivered exactly what we needed - a no-noise migration. Our teams didn't even feel it happen.

DevOps Leaders

DevOps Leaders

Digital Engineering or Transformation Leaders

Enterprise Architects

Digital Thread for DoD

Cloud Migration & Digital Transformation

Digital Thread and Compliance

Smart Engineering for AI, Co-Pilot Initiatives

Software Development & Agile Engineering

IT Service Management & Customer Support

Product Lifecycle Management & Systems Engineering

Requirements Management for Regulated Industries

How a Global Supply Chain Leader Migrated from Jira Data Center to Jira Cloud without Slowing a Single Business Day

The Business Challenge

What the Client Needed

OpsHub’s Migration Strategy: For a risk-free Jira Data Center to Jira Cloud migration

The OpsHub Solution

Active Migration Without Handcuffing DC Users

Zero Downtime, Zero Service Disruption

Full-Fidelity Data Migration - with Add-On and History Preservation

On-the-Fly fields template transformation

Reverse Sync for Coexistence and Reporting Stability

How did we migrate Jira DC to Jira cloud?

Phase 1: Discovery & Migration Blueprint

Phase 2: Dry Runs & Staging Validation

Phase 3: Pilot Migration (400 Projects)

Phase 4: Production Rollout – Wave 1 (800 Projects)

Phase 5: Production Rollout – Wave 2 (1200 Projects)

Phase 6: Final Migration (400 Projects) + Stabilization

Results & Business Impact

Experience scalable, non-disruptive migration with OMM