Get the details of dependent items migrated

Look for the ServiceMax Job record of the Type Configuration Migration Tool, and check the file named SVMX Migrated Items.txt.

Validation result for an item selected for migration indicates a missing custom object, custom field, or Apex class

Ensure that any referenced entity reported as missing is deployed to the target org before commencing migration

The validation result for an SFM Transaction is This item will not be migrated

Check if the associated page layout already exists in the target org and if there is a mismatch between source and target orgs with respect to child section name, count, or sequence.

If yes, clone the page layout in target org and associate the other SFM Transactions with the cloned page layout.

Alternatively, clone the page layout in source org and associate the cloned page layout with the SFM Transaction(s) to be migrated.

If the error message lists any missing fields, ensure that they are created in the target org before re-trying the migration.

Validation result for an Output Document is This item will not be migrated

Check if the associated output document template already exists in the target org and if there is a mismatch between source and target orgs with respect to child section name, count, or sequence. If yes, clone the template in target org and associate the other output documents with the cloned template. Alternatively, clone the template in source org and associate the cloned template with the Output Document(s) to be migrated.

If the error message lists any missing fields, ensure that they are created in the target org before re-trying the migration.

Validation result for a Mobile Configuration is This item will not be migrated

Check if any custom field is referenced in any expressions related to download criteria or advanced download criteria. Create a similar custom field in the target org, with the same API name as in the source org.

Validation result for Inventory Process is This item will not be migrated

Check if any custom field/custom record type is referenced in the process. Create a similar custom field/custom record type in the target org, with the same API name as in the source org.

Validation result for SFM Mobile Permissions is This item will not be migrated

Check the SFM processes that are associated with the selected profile for any metadata issues (like the ones mentioned in the validation result for SFM Transactions above). Try migrating the processes independently to isolate the issue.

The validation result shows The user does not have sufficient permissions on the target org to proceed with the migration. Contact your System Administrator for details.

Ensure that the logged-in user’s Salesforce profile has all field and object-level permissions to ServiceMax configuration objects such as ServiceMax Processes, ServiceMax Config Data, Page Layout, Page Layout Details, SFM Events, and so on.

The validation result for DC Views shows Assignments for the selected DC Views will not be migrated. You should manually set the assignments in the target org for restricting them to specific service teams/territories.

Post Migration, edit the custom DC Views identified during pre-migration and set the required assignments.

Validation result for PM Process shows The values for ‘Assign To’ and ‘Active’ fields for the selected PM Process (es) will not be migrated.

You should manually set the assignments before activating the process in the target org. Post Migration, edit the custom PM Process identified during pre-migration, set the Assign To value as required, and set the Active checkbox.

Validation result for SPM shows Failed to migrate SPMDetails; Record Type ID: this ID value isn't valid for the user: <<user id>>.

Ensure that the System Administrator has permission for the “SPM Details” record type. To enable the permission, add the “SPM Details” record type in the ServiceMax Config Data Record Type Settings.