Epic Clarity on Oracle. Getting ahead of the migration.

Epic Clarity has historically run on Oracle or Microsoft SQL Server. Epic's strategic direction has been toward SQL Server and the Caboodle dimensional warehouse that pairs with it. For the hundreds of health systems still running Clarity and an enterprise data warehouse on Oracle, the migration is not a someday problem. It is a strategic question on a tightening timeline.

Here is the thing most teams miss in the first planning meeting: this migration is also the best excuse you will get this decade to fix the reporting layer that has been quietly failing you. Handle it as a chore and you will pay twice. Handle it as a modernization and the timeline pays for itself.

Why this is a strategic question, not a nice-to-have

The pressure to move is real, even when no single hard deadline forces the date. The Oracle estate is increasingly expensive to run on-prem. Epic's strategic direction is clearly toward SQL Server and Caboodle. Your security team is less and less comfortable with infrastructure you have to maintain yourself. Your auditors keep asking better questions about the lineage of every number. And the cloud-modernization conversation is happening at the board level whether your data team is in it or not.

The runway is shorter than it looks. A genuine enterprise migration of Clarity, the EDW, and the reporting that sits on top of them is a 12-to-18-month program, not a weekend cutover. Start the planning conversation late and you compress every downstream phase.

The trap: lift and shift

The path of least resistance is to recreate your Oracle objects one-to-one on a new database, repoint the reports, and call it done. It feels safe. It is the most expensive thing you can do.

A lift-and-shift carries every brittle, overnight-batch report and every undocumented dependency straight onto a new platform, with a new bill attached. You spend a year and a large budget to arrive at exactly the reporting problems you had before, now in the cloud.

What getting ahead of it actually looks like

The systems that come out of this stronger treat the migration as four moves, in this order:

1. Rationalize before you migrate

Before you move anything, inventory it. Which reports are actually run, by whom, how often? Which direct database connections are real and which are ghosts? Shrinking the target first means you rebuild what is used, not what was simply left over. This is the cheapest phase and it determines the cost of every phase after it.

2. Land the data in a governed lakehouse

Instead of another relational copy, land Clarity and Caboodle in a lakehouse with a medallion structure (raw, refined, curated) and a real governance catalog. This is where you stop copying data through fragile multi-stage ETL between servers and start reading it where it lives.

3. Serve it sub-second

Curated data feeds a modern serving layer so dashboards read in-memory, with sub-second performance over tables in the tens of millions of rows. The overnight refresh runs on a schedule the team can trust, and leadership stops waiting on analysts to compile yesterday's numbers by hand from four different systems.

4. Cut over with proof, not hope

Run old and new in parallel, validate the numbers match, then decommission the legacy estate deliberately. Governance, dual-run validation, and a clean rollback path are what let you retire Oracle without holding your breath.

The part everyone underestimates: who actually uses your data

The single most dangerous assumption in a Clarity-off-Oracle migration is that you know who depends on the current environment. You usually do not. Shared service-account credentials mask the real humans and applications behind them. Until you have decomposed those accounts and identified the true population, you cannot safely cut a workload over and revoke access, which is the step that actually defines "done." Budget for that detective work early. It is the critical path.

The bottom line

The Clarity-on-Oracle question is going to land on your roadmap whether you plan for it or not. The only choice you control is whether you spend the money to relocate your problems or to retire them. The health systems that start now, rationalize first, and rebuild on a governed, sub-second-serving foundation will not just stay ahead of the migration. They will come out the other side with reporting their leadership finally trusts.