• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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