The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:

Transformations	Object Type	Advanced Fields
Source	Single object	Folder path and file name
Target	Single object

After you migrate the mapping from Org1 to Org2, you must not edit the mapping.

For an existing target object in Org2, you must specify the folder path and file name in the advanced properties. If the object does not exist in Org2 or the connection does not have access to the object that you used in Org1, the mapping fails with a 403 error.

When you use a parameter file in a cloud-hosted directory and you use different Google Cloud Storage V2 connections in Org1 and Org2, you must specify a bucket name in the

Bucket Name

connection property. Otherwise, the mapping fails.

Ensure that you specify a valid folder and file name in the advanced properties. Otherwise, the mapping fails.

You cannot configure encryption in a mapping that you migrate to the new environment.

Before you specify a Google Cloud Storage folder path and enable the Is Directory option to read files from a Google Cloud Storage folder and subfolder, specify the following value for the INFA_DEBUG property in the System Configuration Details section for the Secure Agent :

When you create a mapping in advanced mode, ensure that you do not select the

Allow Wildcard Characters

option or specify wildcard characters for the source file name. Else, the mapping fails.

When you create a mapping in advanced mode, ensure that you do not read from and write to partition columns. Else, the mapping fails.