• 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!
  • 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.

DirectAdmin to Plesk

As you can see here this migration impossible now. We have corresponding feature request and maybe it will be implemented to the one of next Plesk version.
 
Hi, we're also looking for a migration procedure from DirectAdmin to Plesk 10.x.

Is there some beta migration tool or procedure for it?


Kind regards,
B
 
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/Tozzje/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 ncftpput
- 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

It does NOT:
- Do anything DNS related
- Migrate mailinglists

Current issues:
- DirectAdmin supports 1 MySQL username for multiple databases. Plesk does not, so any account utilizing this will result in an incomplete MySQL migration
- 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
- Script needs to differentiate between errors and warnings, and exit on error(s).
- Uploading lots of files fails due to emphemeral port exhaustion. (http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html)

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.
 
Last edited:
Back
Top