[Vtigercrm-developers] Moving Ondeman to Open source

[VTE]

As Conrado mentioned you might run into some issues. I'm not sure how well
you know the database structure, but that's how we proceed in cases like
these. It doesn't matter if field names are different as long as you map
them correctly - you should be fine.

Here's a sample:

#### Comments

INSERT INTO NEWDBNAME.vtiger_crmentity
(crmid,smcreatorid,smownerid,modifiedby,setype,description,createdtime,modifiedtime,viewedtime,STATUS,VERSION,presence,deleted)
SELECT
crmid,smcreatorid,smownerid,modifiedby,setype,description,createdtime,modifiedtime,viewedtime,STATUS,VERSION,presence,deleted
FROM OLDDBNAME.vtiger_crmentity WHERE setype='ModComments';

INSERT INTO NEWDBNAME.vtiger_modcomments
(modcommentsid,commentcontent,related_to,parent_comments)
SELECT modcommentsid,commentcontent,related_to,parent_comments FROM
OLDDBNAME.vtiger_modcomments;

INSERT INTO NEWDBNAME.vtiger_modcommentscf (modcommentsid)
SELECT modcommentsid FROM NOLDDBNAME.vtiger_modcommentscf;



#### Contacts


INSERT INTO NEWDBNAME.`vtiger_contactdetails`
(`contactid`,`contact_no`,`accountid`,`salutation`,`firstname`,`lastname`,`email`,`phone`,`mobile`,`title`,`department`,`fax`,`reportsto`,`training`,`usertype`,`contacttype`,`otheremail`,`secondaryemail`,`emailoptout`,`imagename`,`reference`,`notify_owner`)
SELECT
`contactid`,`contact_no`,`accountid`,`salutation`,`firstname`,`lastname`,`email`,`phone`,`mobile`,`title`,`department`,`fax`,`reportsto`,`training`,`usertype`,`contacttype`,`otheremail`,`secondaryemail`,`emailoptout`,`imagename`,`reference`,`notify_owner`
FROM OLDDBNAME.vtiger_contactdetails;

INSERT INTO NEWDBNAME.`vtiger_contactaddress`
(`contactaddressid`,`mailingcity`,`mailingstreet`,`mailingcountry`,`othercountry`,`mailingstate`,`mailingpobox`,`othercity`,`otherstate`,`mailingzip`,`otherzip`,`otherstreet`,`otherpobox`)
SELECT
`contactaddressid`,`mailingcity`,`mailingstreet`,`mailingcountry`,`othercountry`,`mailingstate`,`mailingpobox`,`othercity`,`otherstate`,`mailingzip`,`otherzip`,`otherstreet`,`otherpobox`
FROM OLDDBNAME.vtiger_contactaddress;

INSERT INTO NEWDBNAME.`vtiger_contactsubdetails`
(`contactsubscriptionid`,`homephone`,`otherphone`,`assistant`,`assistantphone`,`birthday`,`laststayintouchrequest`,`laststayintouchsavedate`,`leadsource`)
SELECT
`contactsubscriptionid`,`homephone`,`otherphone`,`assistant`,`assistantphone`,`birthday`,`laststayintouchrequest`,`laststayintouchsavedate`,`leadsource`
FROM OLDDBNAME.vtiger_contactsubdetails


INSERT INTO NEWDBNAME.`vtiger_contactscf` (`contactid`)
SELECT `contactid` FROM OLDDBNAME.vtiger_contactscf;

INSERT INTO NEWDBNAME.`vtiger_customerdetails`
(`customerid`,`portal`,`support_start_date`,`support_end_date`)
SELECT `customerid`,`portal`,`support_start_date`,`support_end_date` FROM
OLDDBNAME.vtiger_customerdetails;


lajeesh k-2 wrote
> Hi VTE,
> 
> Thank s for your tips
> 
> 1. So swaping database won't works ?. and we should copy data from
> individual table ..?
> 2. for recreating custom fields -- is there any quick method to recreate
> custom fields ?. The fields created from layout has names as cf_xxx, so if
> this names are not matching, we cannot copy records into table
> 
> 
> Regards,
> Lajeesh
> 
> On Mon, Nov 17, 2014 at 2:33 PM, VTE <

> support@

> > wrote:
> 
>> 1. Recreate users & groups - maintain the same 'id' value in vtiger_users
>> field. You can manipulate it using seq value.
>> 2. Recreate custom fields
>> 3. Select * from all 'leads' tables(ondemand) and insert into all 'leads'
>> tables(open source). vtiger_crmentity, leaddetails, leadscf, etc...
>> 4. Do the same for comments, just vtiger_modcomments and
>> vtiger_modcommentscf and vtiger_crmentity
>>
>> I used 'leads' as example - it can be done with any module.
>>
>> Once done - update crmentity_seq number and you should be all set.
>>
>>
>>
>> --
>> View this message in context:
>> http://vtiger-crm.2324883.n4.nabble.com/Vtigercrm-developers-Moving-Ondeman-to-Open-source-tp14431p14432.html
>> Sent from the vtigercrm-developers mailing list archive at Nabble.com.
>> _______________________________________________
>> http://www.vtiger.com/
>>
> 
> _______________________________________________
> http://www.vtiger.com/





--
View this message in context: http://vtiger-crm.2324883.n4.nabble.com/Vtigercrm-developers-Moving-Ondeman-to-Open-source-tp14431p14437.html
Sent from the vtigercrm-developers mailing list archive at Nabble.com.