Clone Environment Overview

The Clone Environment feature lets you clone an environment by using a simple screen-based process. In this context, the source environment is the one you want to clone (or copied). The target environment is the where you're copying the source environment.

By using the Clone Environment feature, you can also optionally clone the following:

• Identity domain artifacts (users and predefined role assignments)

• Contents of the inbox and outbox

• Stored snapshots

  Important:

  The Clone Environment feature uses the current snapshot (named Artifact Snapshot) that is created by the last daily maintenance.

  After the snapshot you'll use to clone the environment is created, don't make changes to your source application. Any changes you make after the snapshot is created won't be included when you clone the environment.

• Data Management records

• Job Console records

• Application Audit data

Important:

Before you start using the Clone Environment feature, be aware of its limitations and important considerations. For more information, see Important Considerations for Cloning Environments.

Note:

You can use the cloneEnvironment EPM Automate command instead of the Clone Environment feature. For more information about this command, see cloneEnvironment

Cloning Environments Guidelines

To use the Clone Environment feature, complete the following consecutive steps:

1. Prerequisites for Cloning Environments

2. Cloning NetSuite Cloud EPM Environments

3. Post-Cloning Environment Tasks

To troubleshoot issues, see the help topic Resolving Clone Environment Issues in the Oracle Help Center.

Related Topics

• Migrate from Legacy LCM-based SKUs to NetSuite EPM SKUs
• Clone to NetSuite Cloud EPM Environments
• Important Considerations for Cloning Environments

General Notices