Appendix 6. cPanel and WHM Data Mapping Reference
This chapter provides complete reference for the migration of cPanel parameters and settings to Plesk for Windows. The information found in the chapter covers the answers to the following questions:
- What Plesk objects are created in Plesk after migration. (the "cPanel Object Mapping" section)
- What migrated Plesk object parameters are transferred from cPanel without change. (the "Migrated Plesk Object Mapping Reference" section)
- What migrated Plesk object parameters are recalculated or transformed and what are the recalculation and transformation rules. (the "Migrated Plesk Object Mapping Reference" section)
- What specific Plesk server settings are set by PMM by default that are different from the Plesk default settings. (the "Migrated Plesk Object Mapping Reference" section)
- Where in the Plesk control panel the migrated objects and Plesk server settings are found. (the "cPanel Object Mapping" and "Migrated Plesk Object Mapping Reference" sections)
- What important cPanel objects and server settings are not subject to migration. (the "Important cPanel settings that are not migrated to Plesk" section)
- What can be done to fix some common problems that may arise during migration. (the "Troubleshooting" section)
The appendix is organized into the following sections:
- "cPanel Object Mapping"
This section lists all cPanel objects that are subject to migration and matches them to the corresponding migrated Plesk objects. Use this section to find out what cPanel objects, server, hosting account, and user settings are migrated from cPanel to Plesk.
- "Migrated Plesk Object Mapping Reference"
Use this section to determine the exact cPanel origin and values of migrated parameters in Plesk.
- "Important cPanel settings that are not migrated to Plesk"
Not all cPanel settings have obvious counterparts in Plesk and, hence, cannot be migrated. Use this section to identify cPanel objects or settings that cannot be migrated to determine how you can configure Plesk to compensate for potential loss of content or functionality.