.png)
How Getint and catworkx Migrated 300,000+ Records for a Global Logistics Leader
When a global transportation and logistics enterprise operating across six continents decided to consolidate its ITSM landscape into Jira Cloud, the decision wasn’t just technical. It was strategic.
For years, ServiceNow had powered critical operations across hundreds of business units. Incidents, service requests, change records, assets, custom forms — all deeply embedded in everyday workflows. The system contained hundreds of thousands of records and a long history of customization. Migrating that environment wasn’t about “moving data.” It was about protecting operational continuity while modernizing the foundation.
To deliver the transformation, the company partnered with catworkx, an Atlassian Platinum Partner responsible for preparing and structuring the Jira Cloud environment. For the migration itself — complex, security-heavy, and high-risk — Getint was brought in to lead execution.
What began as an urgent one-month effort to migrate 40,000 incidents quickly evolved into something much bigger.
A Project That Grew in Real Time
As internal alignment progressed and more teams recognized the opportunity to unify onto Jira Cloud, the scope expanded rapidly. The initial 40,000 incidents became more than 300,000 work items — spanning incidents, service requests, change requests, problem records, attachments, comments, assets, and highly customized ServiceNow forms.
At the same time, the timeline remained tight.
ServiceNow wasn’t paused. It remained fully operational throughout most of the project. New incidents were created daily. Existing records were updated. Business units continued working while the migration was being built around them.
And then there was security.
Because of strict internal policies, Getint had to operate entirely on-premises, behind the customer’s firewall. The migration environment was isolated, accessible only through VPN and controlled infrastructure. Every adjustment required coordination. Every change required discipline.
This was not a standard cloud migration. It was an engineering project.
One Team, Shared Ownership
From day one, catworkx and Getint operated as a single, blended team.
catworkx prepared Jira Cloud for scale — configuring projects, workflows, issue types, and governance structures aligned with the organization’s future ITSM model. Getint designed and executed the migration logic — mapping fields, transforming legacy data, handling custom forms, and ensuring attachments and comments retained integrity.
Instead of attempting a single large cutover, the teams adopted an iterative approach.
Over six months, more than 20 migration cycles were executed. Each run refined mappings, captured newly created records, adjusted for scope changes, and incorporated feedback from validation teams. As additional business units joined the migration, the logic evolved. As new edge cases appeared, scripts were adjusted. As the dataset grew, infrastructure was scaled.
The migration matured with each cycle.
Navigating the Complexity Beneath the Surface
Large ServiceNow environments carry history. Years of custom fields. Variations between business units. Inconsistent usage patterns. Mandatory fields missing in some records. Text fields exceeding Jira limits. Asset relationships tied to operational workflows.
Each of these realities surfaced during the migration.
Some ServiceNow records lacked mandatory Jira values and required fallback logic. Certain descriptions exceeded field size limits and had to be intelligently split. Custom fields accumulated over time needed consolidation to avoid recreating unnecessary complexity in Jira Cloud.
Even attachments, comments, and relational asset data required separate validation during each migration wave.
Because ServiceNow remained active, delta runs became critical. The team had to account not only for historical data but also for changes happening in real time.
Toward the final phase, a controlled downtime window was introduced to stabilize the dataset and ensure clean cutover. Even then, late-stage operational updates required recalibration of migration ranges and processing strategies.
Enterprise migrations rarely move in straight lines. This one demanded flexibility without sacrificing control.
The Outcome: A Clean Transition to Jira Cloud
By the end of the project, more than 300,000 work items had been migrated and validated. Attachments and comments were preserved. Custom forms and legacy structures were transformed into Jira-compatible formats. Asset data relevant to workflows was successfully mapped.
Most importantly, the organization transitioned to Jira Cloud without operational disruption.
The new environment provided a unified platform for engineering, IT, and operational teams — replacing fragmented legacy structures with a cleaner, scalable foundation. Reporting became more transparent. Governance became more consistent. The strategic consolidation into Atlassian Cloud was complete.
While a final last-minute dataset could not be migrated due to ServiceNow license expiration, the validated scope required for production readiness was fully delivered.
What This Success Story Really Shows
This migration was not defined by volume alone — though 300,000+ records is significant. It was defined by precision under pressure.
Security constraints. Evolving scope. Active source systems. Tight deadlines. Cross-continental coordination.
The project demonstrates that large-scale ServiceNow → Jira Cloud migrations require more than tooling. They require structured iteration, collaborative ownership, adaptable migration logic, and disciplined cutover management.
When those elements align, even the most complex enterprise transitions become achievable.
And for this global organization, the result was clear: a successful modernization of its ITSM foundation — delivered at scale, securely, and with continuity preserved.
