I've just joined having been a reader of these forums for years!
My company is a small web design and hoster. Most of our clients have no interest in managing their own hosting and leave it all to us. We run our own dedicated server. Over 8 or so years we have used Ensim (later Parallels pro) and never had any problems. 3-4 months ago we had a hardware failure and were persuaded to switch to cPanel on a new box by our server provider who migrated everything with very few problems - all credit to them. But I hate cPanel for too many reasons to go into here - although if anyone wants to know why I'll happily tell. I am now looking at alternatives and Virtualmin pro (the paid version) looks most likely to be the one since we use Webmin to manage all our internal Linux servers and desktops and have used Virtualmin, albeit 4-5 years ago, on a small development server
So has anyone recent experience of migrating from cpanel to virtualmin that they could share?
Have you considered DirectAdmin? The best alternative to cPanel IMO.
★ Sam Barrow - CEO @ SQUIDIX(1-855-SQUIDIX)
★ Ask Us About Sponsoring Your Web Site (High Traffic Sites Only)
★ Squidix - Shared, Reseller, Semi-Dedicated, Managed VPS and Managed Dedicated Hosting
★ Midwestern Web - Web Design & Development Services
A migration from cPanel to Virtualmin (Pro or GPL) should Just Work(tm). It is the best tested migration path, by far, as we've had hundreds (possibly thousands) of cPanel migrations done over the past few years since introducing the migration capability.
In the mysql migration, most of our sites have database names that are not standard cPanel and all have usernames/passwords that are different to the account log-in values. Will that affect the migration script or will it just create dbs with the correct names and passwords? The mig. script notes are not too clear on this.
PS Thanks Sam for your observation, but we have already ruled out Plesk and DA.
Hard to say. Does cPanel know the databases are associated with the domains? If so, it should do the right thing with them, no matter what they're named. MySQL database names already must be separable from usernames, at least in Virtualmin, because usernames in Virtualmin can be longer than 16 characters, while MySQL imposes a 16 char limit.
Regardless, though, if the necessary data is in the cPanel backup and the migration fails, we'd want to know about it and we'd fix it. We take migrations very seriously, and we're always willing to fix it when problems are discovered.
The migration documentation is intentionally short, because there should be no major exceptions (though there are, necessarily, a few differences in the resulting account layouts when you import, because Virtualmin doesn't have the oddball "add-on domains" and "subdomain" account types, and some of our conventions are different than those of cPanel). Mostly, though, everything should just work, and you shouldn't have to think too hard about it. If it doesn't, it's a bug, and we'll fix it.