How ITSM transformation reduced costs by 45% for a healthcare technology provider

e-Core • June 13, 2025

A provider of medical cost management solutions for the workers’ compensation industry was struggling with a complex and fragmented IT environment. Multiple platforms were used to manage projects, service tickets, and incidents. 


The IT services team used ServiceNow, while the development team was migrating from VersionOne to Jira Software. Service requests were submitted via SharePoint, which then generated tickets in ServiceNow. This disjointed system created visibility gaps and communication issues, delaying resolutions.


Change management and release processes relied on several SharePoint forms. SharePoint also served as a document repository and reporting tool—though some documents lived in ServiceNow. Asset tracking was split between a spreadsheet and an Access database. This patchwork of tools increased the risk of errors and made automation difficult.



When their ServiceNow license was nearing expiration, the company saw an opportunity to simplify and improve their IT operations. They chose to move their processes to a single platform using Jira and Jira Service Management (JSM), aiming to better connect business and DevOps at a lower cost.


   Our Work

  • Migrated ITSM tickets and project work from ServiceNow, VersionOne, and SharePoint to Jira Service Management (JSM) and Jira Software, creating a unified platform for managing IT services and project tasks
  • Simplified change management by replacing multiple forms with a single change request issue type in JSM
  • Set up automation rules for ticket prioritization, comment synchronization, and SLA tracking
  • Implemented Insight Asset Management integrated with JSM for real-time visibility and streamlined asset management
  • Provided comprehensive training for JSM agents and administrators


Results

  • Reduced task redundancy to zero and streamlined the approval workflow
  • Enhanced operational efficiency with more effective workflows and faster issue resolution
  • Improved team communication and collaboration with better visibility into development tasks
  • Achieved real-time visibility into network assets, enhancing the IT team’s management capabilities
  • Achieved significant cost savings, realizing an estimated 45% cost reduction and saving over $100K in licenses
  • Empowered teams with the ability to effectively manage and configure the new platform, driving ongoing improvements and adapting to future needs
  • 

The Solution


Our strategy targeted the client’s main issue: the lack of integration between ServiceNow, SharePoint, and VersionOne, which limited visibility into development tasks for bug fixes and incidents. 

Because the client was already moving from VersionOne to Jira, we replaced ServiceNow with JSM to unify IT services and project work, leveraging Atlassian’s built-in integration capabilities.

 

We migrated ITSM tickets and project tasks from ServiceNow and SharePoint to JSM and Jira Software, making collaboration between IT and development teams smoother and more efficient.


To simplify change management, we replaced two separate SharePoint forms with a single Change Request issue type in JSM. We also built in logic that prompted requestors to fill in specific fields based on criteria. This cut down on the back-and-forth, reduced errors, and saved time.


To further improve efficiency and responsiveness to critical issues, we set up automation rules for ticket prioritization, comment synchronization, and SLA tracking. For example, the “Set Incident Priority” automation was executed 30 times per day, ensuring incidents were prioritized efficiently and resolved more quickly. Previously, managing incidents, problems, service requests, and maintenance tasks across multiple systems created complex workflows. The new automation rules ensured efficient handling of critical issues and timely responses, reducing downtime and improving service quality.


The automations for low-environment change requests drastically reduced manual effort and improved processing times for non-critical changes. For example, the “Auto-approve low environments CRs” automation executed 20 times per day, and the “Auto-close low environments CRs” automation executed 18 times per day, minimizing errors and enhancing the overall efficiency of the change management process.


We also implemented Insight Asset Management, integrated with JSM, to replace spreadsheets and Access databases. This gave the team real-time visibility into assets and improved decision-making.


Finally, we trained both JSM agents and admins to make sure the team could manage and configure the platform on their own. The transition ran smoothly, with no disruption to ongoing operations.



The Results



The migration to JSM and Jira Software delivered significant benefits:

  • Enhanced operational efficiency

By consolidating the management of IT services and project tasks into a unified platform, the complexity of these operations was significantly reduced, leading to more efficient workflows and faster issue resolution.

  • Improved team communication and collaboration

The integration between JSM and Jira Software provided better visibility into development tasks and their impact on ITSM tickets, improving communication and collaboration between teams.

  • Streamlined change management process

The new Change Request process reduced task redundancy to zero and streamlined the approval workflow. We implemented logic to require certain fields in the Change Request intake process, based on the change request criteria. This optimization made the change management process more efficient and reduced the likelihood of errors.

  • Better asset management

The implementation of Insight Asset Management provided real-time visibility into network assets, enhancing the IT team’s ability to manage and maintain the infrastructure effectively.

  • Achieved cost savings

By migrating away from ServiceNow before the license expiration, the client avoided the costs associated with renewing the ServiceNow license and optimized their investment in JSM and Jira Software. The switch from VersionOne to Jira resulted in additional savings. Overall, the company realized estimated cost reductions of approximately 45% by moving to Jira Software and JSM, resulting in savings of over $100K per year.

  • Empowered teams for future success

Comprehensive training ensured that the client’s team could effectively manage and configure their new platform, driving ongoing improvements and adapting to future needs.


Looking Ahead



The transition to JSM and Jira Software enabled the client to overcome its ITSM and project management challenges, resulting in a more efficient, integrated, and cost-effective solution that supports its mission of delivering high-quality healthcare technology solutions.


We continue to support the company by providing services that enhance efficiency across strategy and operations alignment by conducting comprehensive business analyses and optimizing their processes. 


e-Core

We combine global expertise with emerging technologies to help companies like yours create innovative digital products, modernize technology platforms, and improve efficiency in digital operations.


You may also be interested in:

By e-Core July 22, 2025
A strategic approach to modernizing code At e-Core, we often partner with organizations whose software technically “works” in production, but just barely. Over time, shifting teams, competing priorities, and tight deadlines lead to codebases that are fragile, expensive to maintain, and risky to enhance. In this context, software refactoring becomes more than a technical task. It’s a business strategy that preserves continuity while unlocking future growth. Defining refactoring: Evolution without disruption Software refactoring is the disciplined restructuring of existing code, improving readability, modularity, and performance, without altering its external behavior. Unlike a full rewrite, refactoring delivers incremental value by: Accelerating feature delivery through cleaner, more modular code. Reducing operational risk by eliminating brittleness and regressions. Lowering total cost of ownership by making enhancements less labor-intensive. Why refactoring matters for business Healthy codebases have a direct business impact: Faster Time-to-Market: Modular components support parallel development and faster releases. Greater resilience: Decoupled services isolate failures and simplify maintenance. Easier onboarding: Clear architecture and design patterns help new developers ramp up quickly. Sustainable cost savings: Less firefighting, fewer regressions, and lower maintenance overhead. What may look like a simple “cleanup” is often the first step toward digital reinvention. Refactoring techniques In enterprise environments built on Java, C#, or Python, we apply proven object-oriented refactoring techniques to increase cohesion and extensibility: Class decoupling: Split monolithic classes into focused, single-responsibility components. SOLID principles: Apply interface segregation and dependency inversion to stabilize architecture. Composition over inheritance: Build flexible, interchangeable structures. Testability enhancements : Isolate side effects and inject dependencies for better test coverage. These techniques form the foundation of our incremental software refactoring roadmaps. Beyond OO: Choosing the right tools for each paradigm Modern languages blend programming paradigms. We help clients apply the right tools to the right problems: Functional patterns in Python to create concise, side-effect-free data pipelines. Kotlin/Scala hybrids that combine OO structure with expressive functional constructs. C# LINQ and Async for declarative data queries and scalable concurrency. This multi-paradigm approach ensures that systems remain robust, flexible, and expressive. A refactoring story: From debt to differentiation Case Study: Regional logistics provider
By e-Core July 16, 2025
Background Ricksoft is known for its popular work and project management apps on the Atlassian Marketplace, including WBS Gantt-Chart for Jira and Excel-like Bulk Issue Editor for Jira. Originating in Japan, the company has grown to serve over 8,000 customers worldwide through nine apps. Their tools are trusted by some of the world’s most innovative companies to boost productivity and manage complex work. By 2019, Ricksoft was seeing growing demand from customers in the Americas and Europe, and needed to scale its support operation beyond Japan. To serve new markets effectively, they had to provide fast, high-quality service in English and across time zones, while maintaining the responsiveness and care that defined their brand. That’s when they turned to e-Core. Our approach We designed a support solution based on three key principles: timezone alignment, consistent high-quality service, and cultural alignment . To get things right from the start, our analysts flew to Japan for in-depth training. They didn’t just learn the products; they learned how Ricksoft works , communicates, and supports customers. Once training wrapped, we built the support operation around Ricksoft’s priorities: timely responses, consistency, and a thoughtful, human tone. We created detailed documentation and a clear process for hiring and onboarding, ensuring every new analyst could step into the role with confidence and alignment. We also introduced monthly updates to the knowledge base and took responsibility for keeping existing articles relevant. That work paid off: most tickets are now resolved in just two to three exchanges , and self-service performance has improved across the board. Today, Ricksoft holds a satisfaction rate of 89 percent and a CSAT of 4.63 out of 5 , well above industry averages. As new analysts joined over the years and support expanded to more products, the service quality remained consistent. “We place great confidence in e-Core’s hiring decisions,” says Alessandro Cristiano, Support Manager at Ricksoft. “They understand how we work, and their mission, values, and culture attract good talent. We had five different generations of agents in seven years, and the work was consistent all the time.” Building long-term value through support. To make support even more impactful, we set up a feedback loop between support and product. Recurring issues and feature requests are flagged and shared with product managers, turning support into a valuable channel to inform product strategy. Tone and empathy matter, too. Ricksoft’s brand is rooted in respect, clarity, and thoughtful communication. We greet returning customers by name, tailor our closings, and have consistently met their SLA targets—with 99% first-response compliance within 12 hours or less. “What is special about e-Core is that they listen first,” Cristiano says. “They don’t try to mold things just for efficiency if it doesn’t work for you. First, they absorb your culture, and then transform it.” To strengthen Ricksoft’s presence in the Atlassian Marketplace , we introduced a post-ticket review request process. That simple step led to more customer reviews, better app ratings, and increased visibility. “We’re now at the top search results, which helps increase our app installs, and ultimately our revenue,” says Cristiano. We also monitor Ricksoft-related activity in the Atlassian Community. When their apps are mentioned, our team responds quickly and accurately, helping Ricksoft remain visible, helpful, and credible in the ecosystem .
By e-Core July 16, 2025
A successful cloud migration doesn’t start with tools, it starts with the right plan . Download this guide to discover a structured, strategic approach to migrating and modernizing workloads on AWS . Whether you’re just starting your cloud journey or looking to optimize an existing environment, this whitepaper gives you the clarity and framework to do it right. What you’ll learn: A 3-phase cloud assessment and planning framework AWS tools that support discovery, migration, and modernization How to reduce cloud spend, improve security, and scale with confidence Real-world planning strategies, including containerization, serverless, and data modernization