Oracle Cloud Infrastructure Documentation

Managing Migration Plans

A migration plan in Oracle Cloud Migrations is a detailed mapping of external assets to target assets in Oracle Cloud Infrastructure (OCI) and the configuration from which to launch them. The plan includes compartment assignments, shape and size selection, and target network dependencies.

You can manage the migration plans by using either the automated recommendations, based on extracted metadata from the source environment, or using a manual configuration.

After creating a migration project, you can generate one or more migrations plans for various reasons such as testing different configurations or comparing cost models. You create these plans manually by cloning an existing plan or by importing plans from a CSV file.

Before you begin creating migration plans, ensure that you complete the following tasks:

To get started with managing the migration plans:

  1. Open the navigation menu  and select Migration & Disaster Recovery. Under Cloud Migrations, select Migrations.

    On this page, you can view all the active and deleted migration projects.

  2. Select the active migration project name link that you want to manage for all actions.

    You are redirected to the Migration project details page.

    On the migration project details page, you can find all the migration plans associated with the project.

When managing migration plans, you can do the following tasks:

Creating a Migration Plan

After creating a migration plan, you can further perform the following tasks on the relevant migration plan:

Required IAM Policies

You can create policies to allow user groups to access Oracle Cloud Migrations resources.

View the verb to permission mapping for Oracle Cloud Migrations to decide which verb meets the access requirements. For example, inspect enables you to view the list of all Oracle Cloud Migrations resources such as migration projects, migration assets, migration plans, target assets, replication tasks, asset sources in a compartment and read enables you to view the details of all the resources.

For details about writing policies for Oracle Cloud Migrations, see Oracle Cloud Migrations IAM Policies. For users to access the Oracle Cloud Migrations resources, see User policies. For using the Oracle Cloud Migrations service, see service policies.

Recommendations for Using Multiple Migration Plans for a Migration Project

Learn when you can use separate migration plans for a migration project.

The migration plans map with the migration assets of a migration project to specific target deployment configurations. These configurations include shape and size selection, instance launch configurations, and selection of the target network deployment.

A migration project has at least one migration plan and you can create multiple plans for a migration project for different scenarios. For example:

  • Separate plans for functional validation (test migration) and production migration: When performing a migration, we recommend that you launch the migrated VMs for functional testing before performing the final production. Therefore,
    • Create separate production and migration test plans for the migrated assets by using smaller shape sizes during test migration.
    • Aim for a separate isolated test deployment network to avoid potential conflicts with other production systems.
  • Separate plans to compare costs and performance of different shape and size selections: To evaluate the target deployment costs based on the shape series and sizing selections from different recommendation strategies and manual configurations, create separate migration plans. Therefore, you can launch separate plans to assess compatibility and performance for different plan configurations.
  • Separate plans to re-create test environments from production VMs: To reduce time and data transfer when moving test and production workloads from a source environment to the cloud, re-create the new test environment from the production data rather than migrating the test environment from the source. Create separate test and production plans to launch multiple instances in separate networks and compartments from the same source VMs.