Managed to run the dry-run. But what is it that dry run omits? It did produce the command script to be run on the target server, but log file shows lots of stuff missing that is normal for dry run. For example Code: [WARN] Could not resolve 300 to new web domain id. This is normal on dry runs Is that command script produced by dry-run OK to execute on the target server? Also, at one point migrate tells me Code: Be sure that the SOURCE has the domain module active and all domains in there! I am not sure I have domain module active. Is it the ISPConfig DNS tab? But that I think is always active and is there when ISPConfig get installed, which makes me assume this is about something else. jboud asked good questions in https://www.howtoforge.com/community/threads/ispconfig-migration-tool.75295/#post-354513 and got excellent answers. From that discussion I learned I can keep the source server running in production while trying out migration. The target server has different IP addresses now, but what are pros and cons in 1) keeping the ip addresses or 2) changing them to the addresses of the source after the successful migration? This is a multiserver setup, where I am migrating the old master to a new blank server. Does migration tool work this way, i.e. the slave servers appear after the migration in the target server?