ORACLE CLOUD TO STACKIT

Oracle Cloud to STACKIT migration

Oracle Cloud Infrastructure is the planned next source adapter of StackToIT. It brings the same method to OCI: read the estate, decide the treatment of each resource, and write the STACKIT migration package.

What an OCI migration has to answer

OCI workloads can rely on Oracle-specific infrastructure, database capabilities and licensing terms. These need an explicit design decision, not an assumption of equivalence.

  1. Know the estate

    Which compute, virtual networks, storage and databases do you run, and how much of it is already defined in Terraform?

  2. Separate the database question

    Oracle Database workloads are the decisive topic: which stay on Oracle, which can change engine, and what licensing allows.

  3. Compare the destination

    Which workloads have a clear STACKIT target, and which need a change to the application or a different pattern?

What you can do today

  1. Shape the adapter

    Talk to us about a representative OCI estate. Real estates show which services matter first.

  2. Assess the rest of your estate

    Workloads on AWS, Azure, Google Cloud or VMware can be assessed now, with the same method and package.

  3. Prepare your Terraform

    Infrastructure defined as code gives any migration a better starting point.

The OCI adapter is planned and not yet available. Current assessments read AWS, Azure, Google Cloud and VMware sources.

Planning a migration to STACKIT?

Let's explore how StackToIT can help assess your infrastructure and prepare a structured migration plan.