*** Disclaimer of Warranties *** ISPConfig disclaims to the fullest extent authorized by law any and all other warranties, whether express or implied, including, without limitation, any implied warranties of title, non-infringement, integration, merchantability or fitness for a particular purpose. By continuing to use this software, you agree to this. First of all the most important question: Do you want to make a real migration or a dry run? (dry, migrate): dry The following modules are available: 1. Confixx to ISPConfig 3 migrator (confixx) 2. ISPConfig 3 to ISPConfig 3 migrator (ispconfig3) 3. Plesk (10.5 - 17.5) to ISPConfig 3 migrator (plesk) 4. ISPConfig 2 to 3 migrator (ispconfig2) 5. AutoDNS to ISPConfig 3 migrator (autodns) Which one is the one matching your SOURCE system? (confixx, ispconfig3, plesk, ispconfig2, autodns): ispconfig3 Enter this (SOURCE) server's ip that is used for outgoing connections [10.27.45.1]: Testing MySQL connection ... OK Name of the remote user of TARGET ISPConfig3 system: migrate Password for this remote user: xxxxxxx URL to the remote system (e. g. https://yourdomain.com:8080/remote/): https://192.168.145.96:8080/remote/ You gave me remote user 'migrate' with password 'xxxxxxx' And I shall connect to 'https://192.168.145.96:8080/remote/' Is this correct? (y, n): I will now have to make some changes in your ISPConfig3 TARGET system config. 1.) Enable domain module if needed 2.) Remove client prefixes (will be undone automatically at the end) 3.) Enable login for mail accounts if needed What is the main public(!) ip of the target server webserver.dailydata.net? [127.0.1.1]: 192.168.145.96 What is the main public(!) ip of the target server mailserver.dailydata.net? [127.0.1.1]: 192.168.145.97 What is the main public(!) ip of the target server dnsserver.dailydata.net? [127.0.1.1]: 192.168.145.98 Seems you have a multi-server setup. So you have to choose target servers for data now. [0] Don't import entries of this type [1] webserver.dailydata.net, main ip: 192.168.145.96 [2] mailserver.dailydata.net, main ip: 192.168.145.97 [3] dnsserver.dailydata.net, main ip: 192.168.145.98 Which server is the MASTER server of your multiserver setup? (0, 1, 2, 3): 1 [0] Don't import entries of this type [1] webserver.dailydata.net, main ip: 192.168.145.96 On which server you want the WEBSITES to be imported? (0, 1): 1 [0] Don't import entries of this type [1] webserver.dailydata.net, main ip: 192.168.145.96 [2] mailserver.dailydata.net, main ip: 192.168.145.97 [3] dnsserver.dailydata.net, main ip: 192.168.145.98 On which server you want the DATABASES to be imported? (0, 1, 2, 3): 1 [0] Don't import entries of this type [2] mailserver.dailydata.net, main ip: 192.168.145.97 On which server you want the MAIL ACCOUNTS to be imported? (0, 2): 0 [0] Don't import entries of this type [3] dnsserver.dailydata.net, main ip: 192.168.145.98 On which server you want the DNS ENTRIES to be imported? (0, 3): 0 Do you want me to overwrite/update existing entries with the same name? (y, n): You can now set entry names, that shall NOT be overwritten. You should use this if you plan to import several server's data to a multi-server installation. If this tool finds a name that is already present, it UPDATES the data with the SOURCE data! If this tool finds a name that you marked as not to overwrite, it either - appends a _2, _3 etc. to this name and creates a new entry, or - prepends a server prefix if specified by --server-prefix argument Do you want to change reserved names now? (y, n): n WARNING! client templates can not be imported! All imported clients will have their correct limits but no template assigned! Further things that will NOT be imported: - getmail accounts - APS information about installed APS packages --- press ENTER if you have understood this and want to continue --- Does your SOURCE ISPConfig 3 installation already use dovecot? [y]: What is the database name of your SOURCE ISPConfig 3 installation? [dbispconfig]: Do you want to migrate only some services or everything? Valid services are: client, web, mail, ftp, database, cronjob, dns, billing Please enter one or more services (comma-separated) or leave blank for all: client,web,ftp,database,cronjob,billing Should I try to keep the existing IDs for clients, webs etc. (IDs will still change if old ID is taken already)? (y, n): Calculating dependencies ... All entries read. To copy over web data, I need SSH access to the target webserver. Please make sure that root login via SSH is allowed. On the target open /etc/ssh/sshd_config and set PermitRootLogin to yes or without-password. You can revert this once the migration is complete. What is the ip for the target web server to connect via SSH? [192.168.145.96]: What is the SSH port? [22]: Testing MySQL connection ... OK Testing target server's MySQL setting ...Warning Warning Your max_allowed_packet setting is < 128M (16M). DB import might fail. Starting API calls. [47/47] processing clientname (C20) [67/67] processing example.com [67/67] processing example.co... www [34/34] processing c6_example [60/60] processing c6_example Processing of entries done. ============= Migration tool run completed.