cPanel Import Function - Clarify please

[zwankie]

Hi everyone,

I searched the forums and also the DA Docs but could not find clarity on the DA cPanel Import function (unless I looked in the wrong Forum sections) which I hope someone can explain to me correctly.

1. What exactly do the three tick boxes for the "Run Import" mean and what exactly do they do?
- Replace existing user
- Ignore convert errors
- Preserve owner

2. Is there no option to add an imported account or list of accounts to an existing user?

3. How is the list of sailed and successful import logs cleared?

4. Can multiple Imports be run at the same time or not?

5. Are there any post-import options like changing source server DNS entries or Suspending the Source Account etc. part of future planning for DA or not?

 

[chrisduk112]

Hi

I've answered your questions with what my understanding is after using the tool multiple times.

1. What exactly do the three tick boxes for the "Run Import" mean and what exactly do they do?
- Replace existing user
- Ignore convert errors
- Preserve owner

if in DA you have a user called bob, if you then migrate bob from cpanel it'll overwrite bob in DA.
if you get an error such as corrupt file cant be copied, it'll continue restoring everything else
keep the owner the same (ie reseller) however what it doesn't do is migrate the reseller first so you need to do this first.

2. Is there no option to add an imported account or list of accounts to an existing user?

Do you mean move them to an existing reseller? if so yes do this the normal way.

3. How is the list of sailed and successful import logs cleared?

you do this in the messages area.

4. Can multiple Imports be run at the same time or not?

This is the biggest problem I have with the tool, it does one at a time and took me 10 hours to move 30 accounts (around 60GB ) from 2 servers racked next to each other, both pretty fast servers! if it did multiple at once this would make migrations so much easier. my ticket with DA asking about this is 45877
Please vote for this feature here https://feedback.directadmin.com/b/feature-requests/cpanel-import-multipe-migrations/

5. Are there any post-import options like changing source server DNS entries or Suspending the Source Account etc. part of future planning for DA or not?

Unfortunately not and this is also a problem of ours, we've wrote a script to do it manually as we plan to move all accounts beginning with A in cPanel to DA and we want DNS to change from Cpanel IP to DA IP on each account move. I have provided some tips to DA on how to do this via WHM API, i also suggest you vote for this feature here https://feedback.directadmin.com/b/feature-requests/cpanel-import-improvements-update-remote-dns/

 

[zwankie]

Thank you for the detailed reply.
There is some work to do in my view for DA to get this working efficiently for larger migrations.

I did find the 3rd Party DA Migration Plugin to have more options but it too does one-by-one.

I started a migration of 200 domains (300+GB) from Plesk > cPanel > DA - I gave up after two days because it's just to much manual checking and interventions and also takes forever with the single migrate mode.

Please neatly groups all domains under a "Client" so that the user only needs to log into one Plesk instance to see all their domains and emails etc but when migrating to cPanel & DA every domain is created separately so the client needs to remember each and every domain's login details separately. I then used the DA scripts to move domains to specific users so they are grouped together - massive manual tasks.

Then to top it all off, if you use Hostbill and possibly WHMCS it also needs to be updated and then new domains are again added separately, not under the existing "main" user account....

Maybe I'm missing something or doing something wrong.

PS: Battling to vote for features these days, seems like DA removed the Direct Email login option, it's now only Twitter, Gmail, Facebook login options for me and that's just not acceptable because I don't use that crap.

 

[thuanduongpa]

I'm not sure if this issue has been reported before, but today I encountered a problem while using the cPanel Import feature in DirectAdmin.

Specifically, the issue relates to the preservation of database table prefix capitalization during the import process. While the import completes successfully without any errors, I noticed that the capitalization in the `$table_prefix` used by WordPress is not retained.

For example, in cPanel the value was:
$table_prefix = 'vaN9aGKY_';

However, after importing to DirectAdmin, the prefix in phpMyAdmin appears as:
$table_prefix = 'van9agky_';

This change in case could cause issues with WordPress installations that rely on the original prefix structure.

Is this behavior expected, or is there a way to preserve the original capitalization during import?