Overview of Migrating Applications

Use Classic Migration Service to migrate applications, such as Oracle Java Cloud Service, SOA Cloud Service, and Integration Classic applications, from Oracle Cloud Infrastructure Classic and Oracle Cloud@Customer to Oracle Cloud Infrastructure.

Classic Migration Service (formerly known as Application Migration Service) simplifies the migration of applications from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure. An application is a combination of deployable artifacts and the applied configuration, which can be exported from a service instance running in a source environment and imported into a compatible service instance running on Oracle Cloud Infrastructure.

Classic Migration Service performs the following actions:

Connects to a specified Oracle Cloud Infrastructure Classic source environment and authenticates with that source environment using the specified credentials.
Displays a list of applications that can be migrated from the source environment. You can select the application that you want to migrate.
Discovers the artifacts and configuration of the application selected for migration. You can configure this application and provide details required for the application to be set up in the target environment. When the configuration is complete, you can start the migration.
Launches a service instance on Oracle Cloud Infrastructure to host the migrated application.
Deploys the exported artifacts and specified configuration on the target instance in Oracle Cloud Infrastructure.

When you are satisfied that an application has been successfully migrated and works as expected, you can delete the corresponding application and associated resources in the source environment. If the migration results in any application-specific changes, such as changes in IP addresses or DNS names, then you might have to update objects that reference those resources.

Supported Applications

Use Classic Migration Service to migrate the following applications to Oracle Cloud Infrastructure:

Oracle Java Cloud Service
Oracle SOA Cloud Service
Oracle Integration
Oracle Process Cloud Service
Oracle Integration Cloud Service

Supported Regions

You can migrate your applications from all Oracle Cloud Infrastructure Classic regions to the supported regions in Oracle Cloud Infrastructure.

Classic Migration Service is available in the following regions:

Australia East (Sydney)
Australia South (Melbourne)
Brazil East (Sao Paulo)
Germany Central (Frankfurt)
India West (Mumbai)
Japan East (Tokyo)
Netherlands Northwest (Amsterdam)
Saudi Arabia West (Jeddah)
Switzerland North (Zurich)
UAE East (Dubai)
UK South (London)
US East (Ashburn)
US West (Phoenix)

Note

If you want to use Classic Migration Service to migrate your applications to an Oracle Cloud Infrastructure region that is not mentioned in the list of supported regions, then contact My Oracle Support.

Service Limits

Classic Migration Service has various default limits. When you create a source or migration in Classic Migration Service, the system ensures that your request is within the bounds of your limit. The limit that applies to you depends on your subscription.

The following limits apply to Classic Migration Service resources, such as source and migration. These limits apply to resources in each region.


Resource	Monthly Universal Credits	Pay-as-You-Go or Promo
Total sources	100	50
Total migrations	100	50
Total active migrations	10	5
Total Oracle Java Cloud Service migrations	30	10
Total Oracle SOA Cloud Service migrations	30	10
Total Oracle Integration Classic migrations	30	10
Total Oracle Integration Cloud Service migrations	30	10
Total Oracle Process Cloud Service migrations	30	10

You can submit a request to increase the service limits for Classic Migration Service resources. See Requesting a Service Limit Increase.

In addition, applications that you migrate use resources that the Classic Migration Service creates, such as database instances, Oracle Java Cloud Service instances, SOA Cloud Service instances, compute instances, and networking resources. These resources are also subject to their respective service limits. For more information about the service limits that apply to other resources, see Service Limits.

Service Events

Actions that you perform on sources and migrations in Classic Migration Service emit events. You can define rules that trigger a specific action when an event occurs. For example, you can define a rule that sends a notification to administrators when someone migrates an application. See Overview of Events and Get Started with Events.

Source Event Types

The following table lists the source events that you can reference.


Event Name	Event Type
Source - Create Begin	`com.oraclecloud.applicationmigration.createsource.begin`
Source - Create End	`com.oraclecloud.applicationmigration.createsource.end`
Source - Update Begin	`com.oraclecloud.applicationmigration.updatesource.begin`
Source - Update End	`com.oraclecloud.applicationmigration.updatesource.end`
Source - Delete End	`com.oraclecloud.applicationmigration.deletesource.end`
Source - Change Compartment	`com.oraclecloud.applicationmigration.changesourcecompartment`

Example

The following example shows information associated with the Source - Create Begin event:

{
  "eventType": "com.oraclecloud.applicationmigration.createsource.begin",
  "cloudEventsVersion": "0.1",
  "eventTypeVersion": "2.0",
  "source": "applicationmigration",
  "eventId": "<unique_ID>",
  "eventTime": "2019-12-13T05:51:25.412Z",
  "contentType": "application/json",
  "data": {
    "compartmentId": "ocid1.compartment.oc1..<unique_ID>",
    "compartmentName": "example-compartment",
    "resourceName": "example-source",
    "resourceId": "ocid1.amssource.oc1..<unique_ID>",
    "availabilityDomain": "<availability_domain>",
    "freeFormTags": {
      "Department": "Finance"
    },
    "definedTags": {
      "Operations": {
        "CostCenter": "42"
      }
    },
    "additionalDetails": {}
  }
}

Migration Event Types

This table lists the migration events that you can reference.


Event Name	Event Type
Migration - Create Begin	`com.oraclecloud.applicationmigration.createmigration.begin`
Migration - Create End	`com.oraclecloud.applicationmigration.createmigration.end`
Migration - Update Begin	`com.oraclecloud.applicationmigration.updatemigration.begin`
Migration - Update End	`com.oraclecloud.applicationmigration.updatemigration.end`
Migration - Migrate Application End	`com.oraclecloud.applicationmigration.migrateapplication.end`
Migration - Delete End	`com.oraclecloud.applicationmigration.deletemigration.end`
Migration - Change Compartment	`com.oraclecloud.applicationmigration.changemigrationcompartment`

Example

The following example shows information associated with the Migration - Create Begin event:

{
  "eventType": "com.oraclecloud.applicationmigration.createmigration.begin",
  "cloudEventsVersion": "0.1",
  "eventTypeVersion": "2.0",
  "source": "applicationmigration",
  "eventId": "<unique_ID>",
  "eventTime": "2019-12-13T05:51:25.412Z",
  "contentType": "application/json",
  "data": {
    "compartmentId": "ocid1.compartment.oc1..<unique_ID>",
    "compartmentName": "example-compartment",
    "resourceName": "example-migration",
    "resourceId": "ocid1.amsmigration.oc1..<unique_ID>",
    "availabilityDomain": "availability_domain",
    "freeFormTags": {
      "Department": "Finance"
    },
    "definedTags": {
      "Operations": {
        "CostCenter": "42"
      }
    },
    "additionalDetails": {}
  }
}

Accessing Oracle Cloud Infrastructure

You can access Oracle Cloud Infrastructure using the Console (a browser-based interface) or the REST API. Instructions for the Console and API are included in topics throughout this guide. For a list of available SDKs, see Software Development Kits and Command Line Interface.

To access the Oracle Cloud Infrastructure Console, see Signing In to the Console.

Classic Migration Service also supports private access from Oracle Cloud Infrastructure resources in a VCN through a service gateway. A service gateway allows connectivity to the Classic Migration Service public endpoints from private IP addresses in private subnets. Set up a service gateway if you are using the REST API or CLI to access Oracle Cloud Infrastructure. If you are using the console to access Oracle Cloud Infrastructure, then you need not set up a service gateway. You can optionally use IAM policies to control which VCNs or ranges of IP addresses can access Classic Migration Service. See Access to Oracle Services: Service Gateway for details.

For general information about using the API, see REST APIs.

Authentication and Authorization

Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).

An administrator in your organization must set up groups, compartments, and policies that control which users can access which services, which resources, and the type of access. For example, the policies control who can create users, create and manage the cloud network, and launch instances. For more information, see Getting Started with Policies. For specific details about writing policies for each of the different services, see Policy Reference.

If you are a user without administrator access and you need to use Oracle Cloud Infrastructure resources that your company owns, then contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you should be using.

Oracle Cloud Infrastructure Documentation