ISPConfig Migration Toolkit 2.1 Released

Today, the ISPConfig Migration Toolkit 2.1 has been released. This release adds support for cPanel systems and fixes several minor issues. Now you can use the Migration tool to import your cPanel server into an ISPConfig system. The cpanel module is currently in beta, but we reached the point where we want to make these functions available to all Migration Toolkit users.

The new Migration Toolkit version can de downloaded here:

What is the ISPConfig Migration Toolkit

The Migration Toolkit consists of 2 applications , the ISPConfig Migration Tool 2.1 and ISPCopy 1.0. The ISPConfig Migration tool 2.1 is the direct successor of the old Migration Tool 1.0. It has been renovated from ground up. e.g. the data get’s copied from source server directly without the need to manually copy a data copy script to the target system and new filters for partial migrations have been added.

Migration Tool

The Migration Tool is used to import an ISPConfig 3 installation fully or partially (e.g. just some websites or clients) into another ISPConfig single- or multiserver system. The Tool supports also imports from cPanel, Plesk, Confixx and ISPConfig 2. More…

Tutorial for the Migration Tool:

Limitations of the new cPanel import feature

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 have any issues in using the new cPanel Module or the Migration Tool in general, please contact our support here so we can help you to solve the problem.


ISPCopy is a new tool which copies and ISPConfig installation “as it is” from one server to another server. The new server must use the same operating system than the old one, all required services (e.g. apache, postfix, dovecot etc.) must be installed already, but ISPConfig itself can be left out as it’s installtion is moved from old server. If ISPConfig is already installed, then it will get overwritten. This approach is less flexible than the one that the Migration tool is using, but the benefit is that the config files of the services that get configuerd by ISPConfig and all paths remain the same. ISPCopy can also be used to move a slave node within a multiserver system to a new server, this can’t be done with the Migration Tool. More…

Get a Migration Toolkit License

The Migration Toolkit license can be purchased here. The price for the full version is 59 EUR excl. VAT.

If you have any questions, feel free to contact us.