• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Contribution DirectAdmin 2 Plesk Migration

And perhaps it is also nice to point intested parties to our cp2plesk script:
https://github.com/rudybroersma/cp2plesk

I am aware that Plesk Migration Manager has a cPanel to Plesk migration function, but it doesn't work properly for migrating hundres of sites. For example, it does not search and replace paths, so any include() with a absolute URL will fail.
 
I have been working on a DirectAdmin 2 Plesk migration script. This is work in progress and "AS IS". It also requires some general Linux/programming skills to use. Is it not meant as a ready-to-use migration system. It needs work. No documentation as of now.

You can get it from Git:
https://github.com/rudybroersma/da2plesk/

Basicly, this script takes an unpacked DirectAdmin backup (login as admin on DA -> Create/restore backup -> select user and create backup. Copy the .tar.gz backup to your plesk server, unpack it somewhere) and retrieves data from the backup file.

The script outputs a series of CLI commands, run those to migrate the domain.

It does the following:
- Find and replace pathnames to Plesk path structure
- Create client account and subscription
- Upload files using lftp
- Create and insert databases and database users
- Create and migrate POP3 accounts (including e-mail using imapsync)
- Create mail forwards
- Create subdomains, aliases, pointers (using custom 301 redirects)
- Migrate protected directories and restore/reset .htaccess files (set proper password file location)
- (optionally) e-mail your customer with the new login details.
- Install cron scripts
- Change DNS records to the new IPs, while keeping user modifications

It does NOT:
- Migrate mailinglists

Current issues:
- The script sets the mysql password using MySQL CLI instead of PSA tools. This causes the 'DB WebAdmin' link to fail in Plesk. Fix is to enter the MySQL user password in Plesk.
- Limited to one account at a time (we use a bash loop script to migrate hundreds of domains in one go)
- Script needs to differentiate between errors and warnings, and exit on error(s).

The script relies on a file containing all e-mail passwords. I have gathered the e-mail passwords by patching Dovecot to log passwords. More details on this will be in the readme.md.
 
Back
Top