That is what we generally recommend for porting from 1.x to 2.x - use the programmatic API and edit by hand.
In Smitha's case, she has an upgrade option that she seems to have been unaware of, though, and in any case would want to do that first. Karl Sent from my Windows Phone ------------------------------ From: Will Martin Sent: 5/29/2015 1:48 AM To: [email protected]; Smitha S; [email protected] Subject: RE: ManifoldCF upgradation to 2.0.2- DB Issues Karl: Is the programmatic api available in 1.x? Dumping json specs for objects can get them back into 2.x quickly; we do. Although jobs themselves are somewhat trickier than repos/auths/output …. ?? regards will martin *From:* Karl Wright [mailto:[email protected]] *Sent:* Friday, May 29, 2015 1:44 AM *To:* Smitha S; [email protected]; [email protected] *Subject:* RE: ManifoldCF upgradation to 2.0.2- DB Issues Hi Smitha, There is no automatic upgrade from mcf 1.x to mcf 2.x. I suggest that you upgrade instead to 1.9. Karl Sent from my Windows Phone ------------------------------ *From: *Smitha S *Sent: *5/28/2015 11:21 PM *To: *[email protected]; [email protected] *Cc: *Karl Wright *Subject: *ManifoldCF upgradation to 2.0.2- DB Issues Hi, Currently we are using MCF 1.6 version. I wanted to upgrade to MCF2.0.2 version. Since so many jobs has been configured in MCF1.6 version, I was planning to use the same MCF DB for 2.0.2 version. But I am getting error related to some db column when I specify the same DB in new properties.xml. Is there any problem in using the old MCF DB. Or should I start fresh and re-create all the connectors and jobs. How do I migrate the jobs from old DB to new DB. Please help me in getting the process correct. Thanks in advance. Regards, Smitha
