Rules and guidelines for migrating a mapping

• •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, multiple objects	Dataset and table name
Lookup	Single object Note: Applicable for unconnected, and connected cached and uncached.	Dataset and table name
Target	Single object	Dataset and table name

• •Before you migrate a mapping to the new environment, map the connection from the earlier environment to the migrated environment that has access to the dataset and table name configured in the advanced properties in the earlier environment.
• •Ensure that the table that you specify as an override contains the same schema as the corresponding table selected during design time.
• •When you specify a custom query as a source object and override the source dataset and source table name, the Secure Agent does not consider the dataset name or table name to import the metadata.
• •After you migrate the mapping to Org2, you must not edit the mapping.
• • When you override the dataset and table name in a mapping, the mapping fails with an error if the dataset used in the connection in Org2 is not valid. The mapping fails with the following error:
Operation failed: error [The following exception occurred: [404 Not Found]
• • Before you migrate a mapping that contains an override to the parameterized object using the parameter file, you need to disable the "Allow parameter to be overridden at run time" option. If you enable the option and you run the mapping after the migration, the following error occurs:
Mapping is failing with error -Unable to start Mapping Task because schema fetch failed.