The Cloud is Calling: Beyond the Data Center, a Healthcare Leader's Guide to Application Rationalization and Cloud Migration

Mar 24, 2026 | min read
Please select some categories on More Settings section.
By

Luiz Cieslak

While every other industry moved to the cloud, healthcare hesitated – and for several good reasons:

- The safety and security of sensitive patient data.
- The sheer volume and complexity of their data, which is spread across a host of disparate digital systems.
- The lack of cloud integration with Epic, through which most U.S. hospital data flows.

But cloud maturity has come a long way in recent years. Cloud solutions are much better at handling complexity and maintaining security than they were a decade ago. Even more significantly, Epic now runs on the cloud, which opens up a new world of opportunity.

The question is whether healthcare providers are ready to take advantage of it. 

Why Healthcare Has Been Slow to Adopt the Cloud

What is the value of migrating to the cloud? Lower costs compared to operating and maintaining an on-prem data center aren’t the only draw.
A cloud migration also offers the opportunity for greater business agility, increased security, and, crucially, a stronger compliance posture. Major cloud providers can offer:

- Robust audit logging.
- Encryption at rest and in transit.
- Infrastructure that can support HIPAA requirements.

Compliance like this does not happen automatically, however. Business associate agreements must be negotiated. Data residency requirements must be mapped. Access governance must be redesigned. These are not footnotes – they are potential landmines if left to the end of the project.
For many organizations, a move to the cloud also mitigates the risks of not knowing about their legacy systems and technologies, especially when the people who specialized in those systems are long since gone.

These would seem to be adequate selling points for most hospital and healthcare leaders, who are not only feeling the pinch of rising costs and shrinking profit margins, but are often watching their legacy systems grow more obsolete with each passing day. 

But old habits die hard. Providers that have been running their own data centers for years often have plenty of reasons for not making the move:

- Uncertainty about the tangle of dependencies in legacy systems.
- Worries about their sensitive data and how it will be validated in a move.
- Short-term concerns about the cost and ROI of a move to the cloud.

General skepticism around a seemingly complicated migration, especially when everything seems to be running fine with their current on-premises data center.

None of these holdups are outside the bounds of reason. A cloud migration is a major move that comes with its fair share of unknowns. But these are also the kinds of fears that can paralyze an organization facing any kind of technological transformation – in which case they become barriers to progress.

Why Now Is the Time for Healthcare Cloud Migration



For a long time, the convenient excuse for cloud holdouts was the inability to integrate Epic.

With that roadblock significantly reduced, the conversation can shift from “can we move to the cloud?” to “how do we rationalize our entire application ecosystem as we do?” And it’s hard to argue against the compelling reasons to make a move now:

The chance to get out of the IT business. Hospitals are meant to be healthcare organizations, not IT companies. By leaving behind their cost- and labor-intensive data centers with a move to the cloud, they can get their focus back to where it belongs – patient care.

A more affordable migration. While moving to the cloud still involves an investment, those upfront costs are much lower now than they once were. And over the long term, they pale in comparison to the price of operating an on-premises data center, especially as the cost of equipment – and the talent to run it – continues to climb.

A faster and less risky migration. Thanks to advancements in AI-assisted reverse and forward engineering, a migration or modernization project today can unfold more quickly and with less risk than ever before.

The price of waiting. As hospitals and healthcare providers continue to digitize more and more of their operations, the lift of a cloud migration only gets heavier. In other words, the longer the wait, the harder a move will be.

There is also one more dimension that rarely makes it into the business case: The accumulated weight of the integrated application ecosystem.

The average large health system connects 50 to 100 or more applications to its EHR – each with its own vendor relationship, contract cycle, interface dependencies, and cloud-readiness status. A cloud migration is the forcing function that finally puts every one of those applications on the table for honest evaluation:

- Which are mission-critical?
- Which are redundant with Epic modules already being paid for?
- Which should be retired, replaced with a cloud-native alternative, or modernized from HL7 v2 to FHIR-based APIs?

The organizations that treat migration as a pure infrastructure exercise miss this strategic opportunity entirely.

Despite these solid arguments in favor of action, however, the thought of such a massive undertaking can be intimidating for many healthcare organizations. What if something goes wrong and everything stops working? It’s an understandable concern – and in healthcare, it carries real clinical stakes.

A cutover that disrupts access to the medication administration record, the ED tracking board, or the radiology worklist is not merely an IT inconvenience. It’s a patient safety event. Cutover planning, clinical downtime procedures, and phased migration sequencing must be designed into the program from day one, not bolted on at the end.

It’s also why it’s so important to have a trusted partner to guide you through the process. Migration is a planned dance, and it’s always better to undertake it with someone who has done these steps before.

The Real Challenge: Application Rationalization



For most health systems, Epic is the hub of a wheel with 50 to 100 or more spokes. And each spoke is an application that cannot simply be lifted and shifted. That’s why before setting a migration timeline, leadership needs a clear-eyed view of what is actually in scope:

Interface engine dependencies. Most large health systems route significant HL7 and FHIR transaction volumes through an interface engine such as Mirth or Rhapsody.

That engine – and every one of the interfaces it manages – must be mapped, migrated, or replaced. This work alone can span multiple years, which is why this can be the ideal moment to modernize from HL7 v2 to FHIR-based integrations that will support the next decade of interoperability requirements.

Third-party vendor readiness. Not every vendor whose application touches your EHR is cloud-ready. And not every vendor operates on your timeline.

Contract renegotiations, vendor roadmap dependencies, and end-of-life decisions will shape your migration sequence in ways that no purely internal plan can fully anticipate. Build a vendor readiness matrix before finalizing your wave plan.

Application rationalization decisions. The migration is the forcing function for the kinds of questions every health system should be asking. Of the applications in your ecosystem, which ones do you actually need? Which are redundant with Epic functionality you are already paying for? Which should be replaced with a cloud-native alternative?

These decisions, made deliberately, can turn a costly migration into a meaningful efficiency gain.

Organizations that treat cloud migration as a pure “lift-and-shift” exercise will emerge with the same fragmented application portfolio they started with, just now running on someone else’s hardware.

Those that treat it as a strategic rationalization moment, on the other hand, can come out leaner, more integrated, and better positioned for whatever the next decade of healthcare technology brings.

How to Prepare for a Healthcare Cloud Migration

That’s not to say, of course, that cloud migration is easy. Truly transformative projects rarely are. Even with better technology and a progressive step-by-step plan, moving huge amounts of data and multiple apps from an entrenched on-premises data center to the cloud still represents a considerable effort.

That’s why those hospitals and healthcare providers that want to make the most of this opportunity need to prepare now and get themselves ready for the changes that are coming.

Build a migration mindset. Getting everyone on board with a future in the cloud can help eliminate any lingering skepticism or romanticism about sticking with how things have always been.

Map out interconnections. Untangling the overlapping web of systems and apps to identify blind spots and decide what moves when can seem like a herculean task. But that’s another reason why now is a great time to move – advances in gen AI analysis have the ability to speed up this process considerably.

Identify a decision-maker. Deciding which apps move and which don’t will invariably involve a lot of stakeholders. That’s why it’s so important to have someone in charge to take all of that input and organize it into a cohesive plan – which can dramatically lower the odds of your migration project getting bogged down.

Plan for clinical continuity. Define downtime procedures before you need them. Every migration phase should be mapped against the clinical workflows it touches – from the ED to the pharmacy to the OR. The answer to the question “what happens to patient care if this system is unavailable for four hours?” must be settled before any cutover window is opened.

Coordinate your vendor ecosystem. Build a vendor readiness matrix early. For each integrated application, assess cloud compatibility, contract flexibility, and the vendor’s own migration roadmap. Some of your most consequential sequencing decisions – such as what moves first, what moves last, and what gets replaced – will be determined by factors outside your organization.

CI&T can help get this plan into place. We generally start with an in-depth discovery and proof of concept phase as a fixed-price, short-term, low-risk engagement to determine whether a migration makes sense for the organization.

This discovery phase also surfaces one of the most valuable opportunities a migration presents: the chance to modernize your integration architecture. Most health systems still move clinical data primarily through HL7 v2 interfaces, a messaging standard conceived in the 1980s.

A cloud migration is the natural inflection point to shift toward FHIR-based APIs, enabling richer interoperability, support for patient-facing applications, and alignment with CMS interoperability mandates. Done right, this is not just a migration – it is a platform upgrade for the next decade of healthcare IT.

If the decision is made to move forward, we provide additional cost effectiveness throughout the process by relying primarily on nearshore resources, as well as by leveraging hyperscaler funding programs.

It’s Time to Head for the Cloud

Epic’s move to cloud hosting has removed one of the last structural barriers holding healthcare providers back, but let’s be precise about what that means. Epic’s cloud is a starting point, not a migration solution. The real work lies in rationalizing the application ecosystem that surrounds it. 

For health system leaders, the question is no longer whether to move to the cloud. It is whether to use this migration as a once-in-a-generation opportunity to evaluate every application, every interface, and every vendor relationship against a single standard:

Does this make us better at delivering care?
The organizations that ask that question, and answer it honestly, will emerge from this transition fundamentally stronger.

But moving to the cloud is not a simple, straightforward process. Large-scale cloud migration and modernization is about more than just technology – it’s about coordination and speed and security. In other words, it’s a great time to call on an experienced partner who can help mitigate the complexity and risk.

Get in touch to find out how CI&T can be that partner on your cloud journey.












Luiz Cieslak, VP, Digital Solutions, CI&T

Luiz Cieslak

SVP, Head of Healthcare & Life Sciences