ispCP - Board - Support
Automat the migration process for non-VHCS/Omega clients - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Migration (/forum-35.html)
+--- Thread: Automat the migration process for non-VHCS/Omega clients (/thread-8221.html)



Automat the migration process for non-VHCS/Omega clients - polysign - 10-25-2009 10:37 PM

Hi there,

I am using VHCS for over 5 years. Now we want to migrate a few clients (100) to a new Omega installation.

The problem is that those new clients come from a proprietary hosting system and I cannot migrate them that easy...

So I managed to create new domains trough the database by setting the domain_status to "toadd". But that only adds me the domain (even tough I don't know if it really works well, as I had a PHP issue with such a domain).

Then I wanted to add some mail users. But how to do that? Is there a way to automate this process? Trough the database or any other way?

What about the clients old databases (coming from mysql). Is there a way to import the exports in new databases (those have to be named like the old ones. ispcp creates it's own db-namespace).

Migrating 100 clients will be hard if there is no easy way doing it Smile

Any ideas?

thx


RE: Automat the migration process for non-VHCS/Omega clients - MasterTH - 10-26-2009 12:14 AM

take a look in the documentation area, there you a way to migrate from vhcs zu ispcp


RE: Automat the migration process for non-VHCS/Omega clients - polysign - 10-26-2009 04:20 AM

(10-26-2009 12:14 AM)MasterTH Wrote:  take a look in the documentation area, there you a way to migrate from vhcs zu ispcp

Sorry if I misguided you, but my problem is how to migrate those 100 clients coming from a completely different hosting system (proprietary).

I have 50 VHCS clients I will migrate to ispcp, but that won't be much of an issue.

thx


RE: Automat the migration process for non-VHCS/Omega clients - MasterTH - 10-26-2009 04:34 AM

oh i'm sry. i haven't seen the "non" in the title Wink

this will be very difficult. Because every cp-software uses different databasenames or entrys, the next problem are the passwords. Each CP uses his own crypt and decrypt function. I think you can copy alle the entrys by yourself into the database of ispcp (email, domain stuff a.s.o) and then run the rqst manager by hand to create all of the mail-adresses and domains...

But the users has to set their passwords.
This is very difficult and my optinion is, that theres no way to get this work automatically .


RE: Automat the migration process for non-VHCS/Omega clients - roadfox - 11-24-2009 03:16 AM

this might help: http://www.isp-control.net/documentation/doku.php?id=dev:daemon_commands_cli