Resources > ServiceMax Tools > ServiceMax Migration Tool > Configuration Items Supported for Migration > Engage Supported Dependent Items
Engage Supported Dependent Items
The following is the list of dependent items for Engage migration.
Categories
Supported Configuration Items
Description
Global Settings
Notification Setup
JWT Authentication: The existing configuration for the following items is supported for migration.
• Push Notification Connected App Consumer Key
• Self-Signed Certificate Name
Notification Workflow Configuration: The notification workflow configurations are supported for migration if the flow with the same name exists in the target org.
Translations
All the translations with the filter criteria are supported for migration.
* 
Translation of message type Push Notification Messages is supported for migration. The other message types such as Custom Action, Questionnaire, and Tailored Custom Request Type are migrated as part of the Community.
Environments
All the fields are supported for migration.
Mobile App Settings
Branding
All the settings are supported for migration.
Home
Upcoming Appointments: The Status and the Order Type are supported for migration if the target org has the same values in the Status and Order Type.
Asset Spotlight: The same reports with the same name must exist in the target org.
Asset
Action Area: All the features including the Custom Actions are supported for migration.
Details: All the templates are supported for migration. The Product Family and the Product Line values must exist in the target org.
The asset fields selected in the template must exist in the target org.
Records: The Header Field and the Body fields are supported for migration.
* 
If any custom field is configured for the header or the body fields, the same custom fields must exist in the target field.
Properties: All the settings are supported for migration.
Location
Action Area: All the features including the Custom Actions are supported for migration.
Details: All the templates are supported for migration.
* 
If any custom field is configured for the primary or the additional location field, the same custom fields must exist in the target field.
Records: The Header Field and the Body fields are supported for migration.
* 
If any custom field is configured for the header or the body field, the same custom fields must exist in the target field.
Request
Technician Visit: All the settings are supported for migration.
* 
The Request a Technician Visit flows are supported for migration if the flow with the same name exists in the target org.
All additional questions are supported for migration.
Data Update: All the settings are supported for migration.
* 
The Data Update flows are supported for migration if the flow with the same name exists in the target org.
Custom Requests: All the settings are supported for migration.
Remote Support
The Zinc Hotline ID, if configured, is supported for migration.
Settings
The configured Help URL is supported for migration.
Feature preferences
Configurations
All the configurations are supported for migration.
For more information about the validations performed as part of Engage migration, see Engage Configurations.
Was this helpful?