[BETA RELEASE] ensim 4.0.x to directadmin migration script
I'm currently developing a migration script from ensim pro 4.0.x to directadmin. A lot is working but there are still some things I have to implement.
Should also work with 4.1.x as long as ensim hasn't changed the file system and export.xml structure.
I've made the third beta avalaible for download.
Current Version: v. beta 1.3
Ensim To DirectAdmin Script Beta 1.3
Important for freebsd da users, with da version prior to 1.24
Due to a problem with the restore sytem in da, you have to unoutcomment the line in the script.
This will be fixed in the next release of da.
If you don't do that the root password of your freebsd box will be overwritten when you restore a converted tarball on da.
The script is based on da.cpanel.import.pl authored by Phil 'l0rdphi1' Stier, I would realy like to thank him, for his work.
This new beta version completely works on the backup tarballs of the ensim server. So you don't need to run the script on the ensim server. Also this version imports all password hashess, so the passwords will be the same on directadmin as on the ensim server.
The ensim backup tarballs has to be in the import directory and it creates directadmin backup tarballs for the sites in the export directory.
Use this script at your own risk, I'm not responsable if anything goes wrong or something blows up.
Here's the current feature list of the migration script
- all passwords will be imported
- The ensim siteadmin user will be imported as a normal pop account and a normal ftp user. The ftp user will have access to the complete domain. This way customers don't have to change the login in their ftp or mail program. The migration script will then choose a new username for the directadmin main user.
- new directadmin main user will bei choosen the following way. I append "da" to the ensim siteadminusername then special chars ("-",".","_") in this username will be removed and the username will be cutoff at 10 characters, this is limited by da. The password for this user will be set to the password of the ensim siteadmin user.
- subdomains import
- webalizer stats import
- public_html files import
- ftp accounts import, also for subdomain owners
- pop3 accounts will be imported
- email aliases import
- email forwarders import
- email vacation messagesimport
- majordomo mailng list import
- catch all settings
- email accounts import including their pop3 messages, and imap folders
- domain aliases import
- mysql databases import
- mysql db will be renamed from domain_tld_-_dbname to dauser_dbname, and the da mysql db name will be cutoff at 16 characters, as of the limitation of mysql.
- renaming the dbnames in the script files
- mysql main user import
- fix .htaccess file of powertools
- fix all absoulte and relative paths in script files
What's on my ToDo list
- htpasswd files
Requirements
The migration script needs the XSLT. pm Perl Module to migrate the tarballs.
Before running the tool, you have to customize the defaults.conf file. You have to create the directory import and export, where you've extracted the script.
Please send bug reports or comments fabi[at]vweb.ch
Thanks you
Kind Regards
Fabrizio
I'm currently developing a migration script from ensim pro 4.0.x to directadmin. A lot is working but there are still some things I have to implement.
Should also work with 4.1.x as long as ensim hasn't changed the file system and export.xml structure.
I've made the third beta avalaible for download.
Current Version: v. beta 1.3
Ensim To DirectAdmin Script Beta 1.3
Important for freebsd da users, with da version prior to 1.24
Due to a problem with the restore sytem in da, you have to unoutcomment the line in the script.
# $passwd =~ s/\$/\\\$/g;
This will be fixed in the next release of da.
If you don't do that the root password of your freebsd box will be overwritten when you restore a converted tarball on da.
The script is based on da.cpanel.import.pl authored by Phil 'l0rdphi1' Stier, I would realy like to thank him, for his work.
This new beta version completely works on the backup tarballs of the ensim server. So you don't need to run the script on the ensim server. Also this version imports all password hashess, so the passwords will be the same on directadmin as on the ensim server.
The ensim backup tarballs has to be in the import directory and it creates directadmin backup tarballs for the sites in the export directory.
Use this script at your own risk, I'm not responsable if anything goes wrong or something blows up.
Here's the current feature list of the migration script
- all passwords will be imported
- The ensim siteadmin user will be imported as a normal pop account and a normal ftp user. The ftp user will have access to the complete domain. This way customers don't have to change the login in their ftp or mail program. The migration script will then choose a new username for the directadmin main user.
- new directadmin main user will bei choosen the following way. I append "da" to the ensim siteadminusername then special chars ("-",".","_") in this username will be removed and the username will be cutoff at 10 characters, this is limited by da. The password for this user will be set to the password of the ensim siteadmin user.
- subdomains import
- webalizer stats import
- public_html files import
- ftp accounts import, also for subdomain owners
- pop3 accounts will be imported
- email aliases import
- email forwarders import
- email vacation messagesimport
- majordomo mailng list import
- catch all settings
- email accounts import including their pop3 messages, and imap folders
- domain aliases import
- mysql databases import
- mysql db will be renamed from domain_tld_-_dbname to dauser_dbname, and the da mysql db name will be cutoff at 16 characters, as of the limitation of mysql.
- renaming the dbnames in the script files
- mysql main user import
- fix .htaccess file of powertools
- fix all absoulte and relative paths in script files
What's on my ToDo list
- htpasswd files
Requirements
The migration script needs the XSLT. pm Perl Module to migrate the tarballs.
Before running the tool, you have to customize the defaults.conf file. You have to create the directory import and export, where you've extracted the script.
Please send bug reports or comments fabi[at]vweb.ch
Thanks you
Kind Regards
Fabrizio
Last edited: