Resources > ServiceMax Tools > ServiceMax Migration Tool > Best Practices for Migration Tool
Best Practices for Migration Tool
This section explains the best practices you should consider while migrating ServiceMax configurations from one org to another using the ServiceMax Migration tool.
When you plan to migrate configurations with a large number of dependent items, such as SFM Mobile Permission and SFM Wizards, then it is recommended to migrate these configurations separately in multiple iterations. Consider the following recommendations for a smooth migration of these configurations.
Migrating SFM Transactions, SFM Wizards, and SFM Mobile Permissions
SFM Transactions are consumed as the dependent items in SFM Wizards and SFM Mobile Permissions. If you select SFM Transactions along with SFM Wizard or SFM Mobile Permissions, it is a repetition of the SFM Transactions for migration.
Recommendations
To avoid multiple migrations of the same transactions, migrate SFM Transactions separately after migrating SFM Wizards and SFM Mobile Permissions.
Migrating Configuration Profiles
Configuration Profiles can be migrated either as dependent items or as separate items. The following configurations are dependent on Configuration Profiles:
Field Inventory
IB App Setup
Mobile Configuration
SFM Mobile Permissions
If you select Configuration Profiles with any of the above four configurations, it is a repetition of the Configuration Profiles for migration.
Recommendations
To avoid multiple iterations of migration of Configuration Profiles, consider the following points:
If you are migrating any of the four components, the Configuration Profiles are migrated as dependent items automatically. Do not migrate it separately.
If you want to migrate Salesforce Profile Assignments of Configuration Profiles, select Configuration Profiles for migration. Since the assignments do not get migrated when Configuration Profiles is migrated as a dependent item.
Recommendations for Importing from File
The following are the best practices when migrating configuration items from a file to an org:
ServiceMax recommends that you limit the file size to 2 MB and perform migration in multiple iterations if the import file size is huge. An alert message is displayed if the file size exceeds 2 MB, as migration might fail because of the huge file size.
You can import up to 30 SFM Transactions at a time. However, if the SFM Transactions contain lots of configurations, the file size might exceed 2 MB and you might not be able to import 30 SFMs at a time.
Was this helpful?