Oracle Cloud Classic to Oracle Cloud Infrastructure (OCI) Migration Assistance Program for Early Adopters

Oracle has a longstanding reputation for providing innovative technologies that empower organizations to meet their most demanding business needs. One of Oracle's latest advancements is Oracle Cloud Infrastructure (OCI). As the foundation of Oracle's second generation cloud, OCI is purpose-built, best-in-class platform for running enterprise applications. OCI is engineered from the ground up to run mission-critical databases, workloads, and applications while providing end-to-end security. Oracle's data centers around the globe are standardizing on the new OCI architecture which will deliver even greater performance and reliability.

Oracle Cloud Classic is the predecessor to OCI. Many Oracle Enterprise Performance Management Cloud customers are supported on Oracle Cloud Classic.

New EPM Cloud subscriptions purchased by first-time customers are supported on OCI.

About the Migration Assistance Program

To ensure continued success as your business grows and evolves, your EPM Cloud environments will migrate to the OCI platform over time, enabling you to run your SaaS and PaaS solutions from the same data center.

Oracle has instituted a program to assist a limited number of early adopters on Oracle Cloud Classic to migrate to OCI. This program is available on a first come, first served basis at no additional cost.

Enrolling in the Program

When you enroll in this program, Oracle provides you OCI environments equaling the number of Classic environments you have. Only after you successfully test applications in OCI environments will Oracle terminate your Classic environments.

Information about the new OCI (Gen 2) environments is sent to the emails of the Account Administrators and Service Administrators. The production and the test environments of a subscription are migrated simultaneously. For example, epm and epm-test environments are always migrated together. The test or the production environment cannot be migrated separately.

You incur no additional cost to migrate from Classic environments to OCI environments.

To enroll in this program:

  1. Create a CSV file with the following header
    Service URL,New Domain,New Data Center,Account Administrator Email,Service Administrator Email
  2. Add one row containing information for each production environment. Do not specify test environments in the CSV file. The values you specify in the CSV file fields apply to both test and production environments of a subscription.
    1. Service URL: Specify the URL of the Classic environment without any context such as /epmcloud. Example:
    2. New Domain: If you want to change the existing domain name, specify the new domain name. Otherwise, do not specify this value. The new domain names must satisfy the following criteria:
      • Contain only lower-case English letters and numbers
      • Start with a letter
      • Contain a maximum of 32 characters
    3. New Data Center: The OCI region where you want the OCI environment to be hosted. If you want the environment to be hosted in the default region of the Classic data center, do not specify this value. For a mapping of current Classic data centers to OCI regions, see Mapping of Current Classic Data Centers to OCI Regions.
    4. Account Administrator Email: The email address of the Account Administrator (Identity Domain Administrator) of the OCI domain who should receive email about the environments. This email is unique for each domain. If you use the same domain for multiple environments, this email address must be identical in all the rows with the same domain name. Specify only one email address in this field.
    5. Service Administrator Email: The email address of a user who should be created as the Service Administrator. Oracle assigns this user as the Service Administrator of this and the corresponding test environments and sends email about the environments to this address. This email address may be identical to that specified for the Account Administrator. Specify only one email address in this field.
    6. Save the CSV file.
  3. Submit a technical service request asking that your environments be enrolled in the program. Be sure to attach the CSV file created in the preceding step to the service request. See Submitting a Technical Service Request for instructions.

    Oracle will, usually, provide OCI environments within two weeks of submitting the request.


    If your current production and test environments are on different domains, the OCI (Gen 2) production and test environments will both be created in the domain you specify in the CSV file. However, the production environment will be on the primordial stripe and the test environment will be on the secondary stripe so that you can manage them individually; for example, you can add users and set up SSO separately for each stripe. See Creating Oracle Identity Cloud Service Striping for information on primordial and secondary stripes.

Mapping of Current Classic Data Centers to OCI Regions

See the following list for the OCI regions that can host your OCI environments based on your current Classic data centers. The first region is the default if you do not specify one.

  • Ashburn (US6) – us-ashburn-1, us-phoenix-1, ca-toronto-1, ca-montreal-1
  • Austin (US1) – us-phoenix-1, us-ashburn-1, ca-toronto-1, ca-montreal-1
  • Chicago (US2) - us-phoenix-1, us-ashburn-1, ca-toronto-1, ca-montreal-1
  • Chicago (US8/US-Gov) – Not available
  • Sterling (US9/US-Gov DR) - Not available
  • Markham (CA2) – ca-toronto-1, ca-montreal-1, us-ashburn-1, us-phoenix-1
  • Amsterdam (EM2) – eu-amsterdam-1, eu-frankfurt -1
  • Slough (EM3) – uk-london-1
  • Slough (EM6/UK-Gov) – Not available
  • Chessington (EM7/UK-Gov DR) – Not available
  • Abu Dhabi (EM8) – me-dubai-1, me-jeddah-1
  • Sydney (AP1) – ap-sydney-1, ap-melbourne-1, ap-tokyo-1
  • Melbourne (AP4) – ap-melbourne-1, ap-sydney-1, ap-tokyo-1

Steps to Migrate Your Environments to OCI

You use the Clone Environment feature or the cloneEnvironment EPM Automate command to clone your environments.

  1. Clone the test environment using the information available in one of these sources:
  2. Test the cloned environment to ensure that everything works well.
  3. Use the Clone Environment feature or the cloneEnvironment EPM Automate command to clone your production environment.