Pradesh Chanderpaul

Thank you @d00p. You second answer is encouraging. I will attempt an installation on a test machine and see how far I can get. I found this page, which is an excellent starting point for me: https://github.com/Froxlor/Froxlor/wiki/Install-froxlor-from-tarball Key for me was this From that, I went to the demo again and this time revisited the Menu => System => Configuration => Web Server|Email|DNS etc etc Whereas the current control panel (i-mscp) wraps the installation steps and performs the installation tasks for you, froxlor on the other hand merely points to the commands that you should run yourself. Perfect for what I described in my initial post.

I have an existing server managed my i-mscp. I have searched for ways to migrate from i-mscp without success. The i-mscp control panel us written in PHP, perl and shell scripts to manage multiple domains and manages mail (postfix,dovecote), dns (bind), apache (supports subdomains, domain aliases), backups, and so on. I realise there is no migration scripts or guides, but I am looking for advise from people that may have embarked on similar migration journeys before. Key to my migration is to not break the existing server as I have multiple domains with multiple clients. I have a few requests for guiding me through to the next steps 1. Is there any reference for migrations (from other systems even) that I can use. 2. Is it possible, using froxlor, to only manage part of the system. This will allow me, for example to start with migrating the web sites first, then the emails etc, In this way, I can pace and prioriise the migration according to risk and client readiness,