OCI Migration Architect key terms

A structured set of guidance, phases, and checkpoints an organization uses to plan, govern, and execute a move to cloud, covering strategy, assessment, landing zones, migration, and operations.

A structured evaluation of people, process, technology, security, and governance that determines whether an organization can begin migrating workloads and identifies gaps to close before execution.

The discovery process that records which servers, services, databases, and network flows a workload depends on, so migration waves and cutover order reflect real technical coupling.

A repository of configuration items and their relationships, often used as the starting inventory for migration scoping, though it usually needs validation against live discovery data.

Software installed on source servers that collects inventory, performance, network, and dependency data to size target resources and validate assumptions before migration.

Selecting target compute, memory, and storage shapes that match measured workload demand rather than copying source specifications, which reduces cost and avoids over-provisioning.

A classification scheme for migration strategies: rehost, replatform, refactor or re-architect, repurchase, relocate, and retire, used to decide how each application moves.

Moving a workload to cloud infrastructure with minimal change, typically by block-level replication or image export, which is fast but preserves existing technical debt.

Migrating a workload while making targeted changes to take advantage of managed services, such as moving a self-managed database to a managed database service.

A defined group of workloads scheduled to move together in one execution cycle, sequenced by dependency, risk, business calendar, and available cutover windows.

A comparison of current on-premises and target cloud costs, including compute, storage, network egress, licensing, support, labor, and facility costs over a multi-year horizon.

A licensing model where an organization reuses existing Oracle software licenses on cloud infrastructure, which can lower cost but requires careful verification of eligibility and support terms.

A pre-provisioned, governed cloud foundation with identity, networking, logging, security, and account or compartment structure that migrated workloads are deployed into.

A logical container in OCI used to organize and isolate resources for access control, quota, and cost tracking, forming the basis of tenancy governance.

A human-readable OCI statement that grants a group permission to perform a set of actions on a resource family within a compartment or tenancy scope.

An OCI group whose membership is defined by matching rules on resource attributes, allowing instances or other resources to receive permissions without static credentials.

A software-defined private network in OCI with a defined CIDR range, containing subnets, route tables, gateways, and security rules for attached resources.

A contiguous CIDR range within a VCN that can be public or private and regional or availability-domain specific, and that carries its own route table and security list.

A set of stateful ingress and egress rules applied at the subnet level, affecting every resource in that subnet and evaluated alongside network security groups.

A virtual firewall applied to selected VNICs, allowing rules to follow a workload rather than a subnet, which suits tiered or shared-subnet designs.

A virtual network interface card attached to a compute instance, holding private IP addresses, MAC address, and security group membership that determine its network behavior.

A dedicated private network connection between an on-premises location and an OCI region, offering predictable latency and bandwidth compared with internet-based connectivity.

An encrypted IPsec tunnel over the public internet connecting an on-premises network to a VCN, commonly used for lower-cost or backup connectivity.

A virtual router that connects a VCN to on-premises networks, other VCNs, and peered regions, acting as the hub for private connectivity paths.

A VCN peering relationship between regions that lets traffic flow over the Oracle backbone without traversing the public internet or an on-premises detour.

An OCI compute shape whose OCPU and memory can be configured independently within allowed ratios, enabling cost-efficient matching of measured workload demand.

An isolated data center grouping within an OCI region with independent power and network, used together with fault domains to design resilient multi-tier architectures.

A grouping of hardware within an availability domain that shares no single point of failure, used to spread instances so a hardware fault does not take down a whole tier.

Software installed on a source server that continuously replicates disk blocks to a target environment, enabling test launches and short cutover windows for rehost migrations.

An Oracle Database feature that maintains a synchronized standby database through redo transport and apply, used for disaster recovery and to minimize downtime during migration.

A replication product that captures and applies committed transactional changes between heterogeneous or homogeneous databases, enabling near-zero-downtime migrations.

A technique that reads a database change stream and applies those changes to a target system, keeping source and target synchronized until final cutover.

A self-contained database within a multitenant container database, which can be unplugged, moved, and plugged into another container to simplify consolidation and migration.

A utility for exporting and importing database objects and data using dump files, commonly used for logical migrations and schema-level moves between databases.

A detailed runbook listing the ordered steps, owners, validation checks, communication points, and rollback triggers for switching production traffic to the target environment.

The approved period during which production service may be degraded or unavailable, sized to fit the switchover steps plus validation and contingency time.

A pre-tested procedure that restores service on the source environment, or reverses the switch, if cutover validation fails or business criteria are not met.

A full end-to-end execution of the migration and cutover runbook against a test environment, used to measure timing, find gaps, and train the team.

A defined post-cutover period of heightened monitoring, rapid support escalation, and daily review that continues until the target environment is proven stable.

The combined use of metrics, logs, and traces to understand system behavior, used after cutover to confirm performance, availability, and error rates meet expectations.