Licence exit

A path off proprietary licences.Database engines first.

Assessment from the live estate, then migration under governance, one workload at a time.

Scope a pilot →

Oracle and SQL Server

MySQL and MariaDB

PostgreSQL

Every row verified

Proven in your lab first

Cutover scheduled by you

The problem

Licence costs grow quietly, and the migration off them is deferred because it looks like a project nobody has time for.

Databases, hosts and self-hosted search all carry licence models that get more expensive as the estate grows, and the work to leave them never reaches the top of anyone's list.

The IT Operations Engine does the assessment from the live estate and executes the migration under governance, one workload at a time, each proven in your lab before production.

What a licence exit has to prove

An engine and version inventory taken from the live estate rather than from the licence paperwork
End-of-life dates setting the order of work, so the deadlines that cannot move come first
Migration executed under governance, with approval points rather than a single long-running job
Every row verified on the other side before a source is considered replaceable
Each move proven in your lab before it touches production

How we approach it

Database engines first, one workload at a time.

Each move is proven in your lab before it touches production, and the cutover is yours to schedule. The engine has moved a database between engines inside a network with no internet access, writing the client it needed from scratch, pausing for approval mid-task, and verifying every row on the other side. The same mechanism carries a licensed engine to an open one.

Oracle

SQL Server

MySQL

MariaDB

PostgreSQL

Find, fix

- Find - Engine and version inventory across Oracle, SQL Server, MySQL, MariaDB and PostgreSQL estates, and the operating-system and runtime versions running alongside them. End-of-life dates set the order of work.
- Fix - Heterogeneous database migration under governance. The engine has moved a database between engines inside a network with no internet access, writing the client it needed from scratch, pausing for approval mid-task, and verifying every row on the other side. The same mechanism carries a licensed engine to an open one. Self-hosted search onto managed services follows the same pattern.
- Proven before production - Each move is proven in your lab before it touches production. The cutover is yours to schedule, and application-side changes that a new engine requires are scoped with your team.

Want to know what the licensed estate actually holds?

A read-only inventory first, then one database chosen with you for the first move.

Scope a pilot →

How it starts

A read-only inventory, then one database.

The inventory sets the order. The first move proves the mechanism in your lab.

1
Read-only inventory
An inventory of the licensed estate, read from what is actually running. Engines, versions, and the operating systems and runtimes alongside them.
- Oracle, SQL Server, MySQL, MariaDB and PostgreSQL
- Operating-system and runtime versions included
- End-of-life dates set the order of work
2
One database, in your lab
One database chosen with you for the first move, executed under governance and proven in your lab before anything production-facing happens.
- Approval points mid-task, not a single long job
- Every row verified on the other side
- Nothing touches production until the lab move is clean
3
Production, on your schedule
The same mechanism carries the production workload. You schedule the cutover, and application-side changes the new engine requires are scoped with your team.
- One workload at a time
- Cutover scheduled by you
- Application-side changes scoped together

What stays with you

Which workloads move, and when.

Application-side changes that a new engine requires are scoped with your team.

You gain:

The engine can migrate between any pair it can reach. Oracle, SQL Server, MySQL, MariaDB and PostgreSQL today.
Self-hosted search onto managed services follows the same pattern as the database moves.
Each move is proven in your lab before production, and the cutover is yours to schedule.

FAQ

Questions.

Which engines can you migrate between?

Any pair the engine can reach. Oracle, SQL Server, MySQL, MariaDB and PostgreSQL today.

Start with a read-only inventory of the licensed estate.

We read the engines and versions from what is actually running, then choose one database with you for the first move, proven in your lab.

Your benefits:

Read from the estate - not from the licence paperwork.
Under governance - approval points, not one long-running job.
Every row verified - on the other side, before anything is replaced.
Lab first - production only once the mechanism is proven.

What happens next?

Talk.

A focused discussion about the licensed estate and what it is costing.

Inventory.

A read-only inventory, with end-of-life dates setting the order.

Move.

One database, proven in your lab, then production on your schedule.

No obligation. Just a focused discussion about your licensed estate.