1. NetSuite Enterprise Performance Management
  2. Additional Resources
  3. Migrate from Legacy LCM-based SKUs to NetSuite EPM SKUs
  4. Clone to NetSuite Cloud EPM Environments
  5. Post-Cloning Environment Tasks

Post-Cloning Environment Tasks

After you clone an environment, if you're not using the source environment anymore, then make sure you complete the tasks described in this section. These steps ensure that the URLs, scripts, bookmarks, anything else set up for the source environment will work for the cloned environment.

Complete the following tasks after you clone an environment:

Limit Access to Source Environment

After cloning, you should consider allowing only one or two users to access the source environment and disable everyone else.

Notify NetSuite Cloud EPM Users About the New URLs for the Cloned Environment

Let NetSuite Cloud EPM users know about the new URLs for the cloned environment:

  • The URL to access the NetSuite Cloud EPM environment. For more information about these unique URLs, see Sample URLs in the Oracle Help Center.

  • The URLs for setting up public and private Oracle Smart View for Office connections to the environment.

Update EPM Automate and REST API scripts

Update any EPM Automate and REST API scripts that you plan to run in the cloned environment. Make sure you change these values:

  • The environment URL.

  • The user’s password, if it’s different in the cloned environment.

Update Task Manager, Supplemental Data Manager, and Enterprise Journal Custom Report Queries

If needed, update Task Manager, Supplemental Data Manager, and Enterprise Journal custom report queries in the cloned environment. You might need to do this because internal IDs for objects (like tasks, journals, and attributes) can change during migration.

Applies to: NetSuite Planning and Budgeting, NetSuite Tax Reporting, and NetSuite Close Management and Consolidation.

Update Smart View URLs

Update the following Smart View URLs:

Create New Vanity URLs

If your users connect with a vanity URL, create a new one or update the existing vanity URL to go to the cloned environment. See Using Vanity URLs in the Oracle Help Center.

Update Bookmarks

Remind users to update their bookmarks so that they go to the cloned environment.

Set Up Connection Between NetSuite and Target Environment

If you move many instances in an integrated business process to a new domain, please note that Single Sign On (SSO) won’t work until all instances are migrated.

If you previously set up NetSuite to run jobs through the NetSuite interface,you’ll need to update the connection to go to the new target environment. For more information, see the following help topics:

Update Integration With Other Services

If your source environment was integrated with other services, review the integration settings to make sure that the cloned environment works with them too.

Reconfigure SSO for Target Environment

If you previously set up Single Sign-On (SSO) to authenticate users in the source environment, make sure you set up SSO in the new target environment too. This action ensures that users can log in without any issues. For more information, see Configuring Single Sign-On in the Oracle Help Center.

Reconfigure IP Allowlist

If any of the following apply, you'll need to reconfigure the IP allowlists for your OCI environments by using the setIPAllowlist EPM Automate command:

  • You're migrating to OCI environments.

  • You haven't set up the IP allowlists as a prerequisite before cloning, or you want to change the configuration after cloning.

For more information about how to use the EPM Automand command, see the help topic setIPAllowlist in the Oracle Help Center.

Update IP address

You need to update your IP address if you used the IP address for the source IP anywhere. For example, you might have added it in your proxy configuration as an allowed outgoing IP address. You can find the target environment’s IP address by using nslookup. Alternatively, ping the IP address and update it.

Related Topics

General Notices