We have developed a cpanel module for our migration tool recently. Currently we are searching for cpanel users that would like to migrate to ISPConfig and want to beta test our cpanel migration. As cpanel has a very different method of storing and processing data, there are some limitations that cannot be avoided when migrating to ISPConfig: We cannot migrate each and every email filter that might be set up in cpanel. This is due the very different approach (spamassassin/exim filters vs. sieve filters and mail account based vs. client account based filters). We try to convert as much filters as possible, though. You need at least ISPConfig version 3.1.15 as target. We cannot (under some circumstances) migrate all database user to database relations. That is because cpanel uses a quite low-level approach where you can assign unlimited users with custom privileges to each database. ISPConfig only allows up to two (one with full, one with r/o access) users for each database. The migtool does it's best to determine the right users to assign. The remaining users (if any) will still be created but not assigned to any database. Cron Jobs will be migrated but have to be checked manually. That is because cpanel might use /usr/local/something/php or different binaries which do not exist on the target machine. In ISPConfig there is no "master mail box". That means the migration tool will create a "[email protected]" mail box that takes the settings from the cpanel master box. Right now (we'll change that) we do not import the corresponding mail data from there. The web aliasdomains and subdomains in cpanel have quite a different structure so we might not be able to match the settings 100%. PostgreSQL is not supported by ISPConfig and is not migrated. WebDav users in ISPConfig have no setting for r/o or r/w access so all users from cpanel are imported as r/w. If you'd like to be considered as a beta tester, please send an email to the migration toolkit support.