• Checks if any of the selected items and dependent items exist in the target org already:

◦ Does this based on the unique ID of the type of item, such as SFM Transaction ID, SFM Wizard ID, SFM Search ID, SFM Expression ID, Inventory Process ID and Configuration profile names.

◦ If the item or its dependent item(s) exist in the target org, prompts the user to overwrite the item in the target org.

• Checks in target org for the existence of any Apex classes and custom objects & fields referenced in the items selected for migration:

◦ If any referenced entity does not exist in target org, shows that as the reason for not migrating the item.

◦ If any referenced field does not have the same field type in source and target orgs, shows that as the reason for not migrating the item.

• For SFM page layout migration, the tool checks for mismatches in child sections (name, count, or sequence) between Source and Target orgs. The following are the validation scenarios:

◦ If there is no mismatch in child sections, then the user is prompted to overwrite all SFM transactions, SFM Wizards, and SFM Mobile Permissions in the target org.

◦ If there is a mismatch in child sections and if the page layout is linked to one SFM process which has the same SFM ID in Source and Target orgs, then the user is prompted to overwrite all SFM transactions, SFM Wizards, and SFM Mobile Permissions in the target org.

◦ If there is a mismatch in child sections and if the page layout is linked to one SFM process which has a different SFM ID in Source and Target orgs, an error message is displayed. SFM Transactions, SFM Wizards, and SFM Mobile Permissions are not allowed to be migrated.

◦ If there is a mismatch in child sections and if the page layout is referenced in multiple SFM processes in the Target org, an error message is displayed. SFM Transactions, SFM Wizards, and SFM Mobile Permissions are not allowed to be migrated.

• If an Output Document Template (dependent item) exists in the target org, checks if the name, count, and sequence of any existing child sections match between source and target org:

◦ If there is any mismatch, shows that as the reason for not migrating the Output Document.

◦ If there is no mismatch, prompts the user to overwrite the item in the target org.

• If Checklists Questions, associated Field Mapping, Data Validation Rules, Entry Criteria, Exit Criteria, and Page Layout (dependent items) exist in the target org, prompts the user to overwrite these items in the target org.

• If Timesheet configurations, associated Field Mapping, and Expressions (dependent items) exist in the target org, prompts the user to overwrite the item in the target org.

• If SPM Calculation Methods exist in the target org, the user will not be prompted to overwrite the items in the target org, instead, they will be migrated as new items.

• If the SPM Calculation Method’s associated Field Mapping and Expressions (dependent items) exist in the target org, they will be overwritten on migration.

• If custom fields used in SFM Formulas are not available in the target org, a warning message is displayed listing the missing fields with SFM ID that are required in the target org. Note if the user proceeds with the warning message, the SFM Formulas will not be migrated to the target org.

• When you migrate field inventory configurations, if the profiles do not exist in the target org, the migration will not be allowed. If the field inventory option is already configured to a profile in the target org, it will not override the existing field inventory configuration for that profile and will display a message that “Field Inventory configuration exists for selected profile(s) in Target org”.