← Back to team overview

openupgrade-drivers team mailing list archive

Re: [Question #239250]: [6.1 -> 7.0] Migration feedback

 

Question #239250 on OpenUpgrade Server changed:
https://answers.launchpad.net/openupgrade-server/+question/239250

Parthiv Patel posted a new comment:
Hi All,

My experience with migration has been almost 4 versions older, I
personally started working with OpenERP v4.2 where migration to v5.0 was
given by OpenERP using scripts, bunch of scripts to migrate each module
and same when moving from v5.0 to v6.0.

But after that OpenERP stopped distributing scripts to partners and
customers and started their inhouse server for the migration for
customers having OPW. It took me some time to understand the reason
behind it but then there is no other options available.

With no other alternatives available, I tried my hands to made a small
module which does on the fly migration from OpenERP v5.0 to v6.0, but it
couldn't went beyond certain limit.

When OpenERP v6.1 release, it was again time to move forward but wait how ? especially when you don't have an OPW. 
I again put my dev. cap on head and started making change scripts which will apply the changes to existing database and make it ready for next version, During these I found an interesting project taking shape with a great possibility to achieve migration by DIY process named OpenUpgrade.

After couple of demo database testing and some fine tuning, I was
convinced about the potential of it and took the testing to next level,
and first question that came to my mind was, Can I experiment it on a
live database without being blamed in case of something goes wrong ?
First thing I did was, backup our own live database (yes, we do use
OpenERP for our internal accounting as well) and started the migration
process, after of couple of changes in our inhouse module and changes in
script did the trick and voila.. my database was ready for v6.1.

I did some consistency check, cross checked random invoices and accounts
and everything was unaffected. Till the time, I was ready to put my head
on the line for using it for OpenERP migration. Next step was to offer
it to customers and it went as expected, as some of our customers were
still in v6.0 and was eager to move to a next version.

We did almost 30+ such migrations which included migrating openerp
instances including complex multi company architecture (11 organization
under, Large Scale MRP system (almost 100+ MO / day), CRM system with
almost 500k leads and 100k invoices. All live and working smoothly even
after migration and what downtime they had ? on average 2 hours.

Lastly we started migrating our customers from v6.1 v7.0 where "Partner"
and "Partner Address" change was way to crucial and to convince
customers for it took us some time. In our latest edition we migrated
one of our oldest openerp customer to OpenERP v7.0 having been using
OpenERP since v4.2.

All this, was only possible with OpenUpgrade and a pinch of know how
about how it's going to work. For custom made modules, we always
migrated them first, test it, test it again and again when convinced
time to migrate the database.

Cheers,
Parthiv

-- 
You received this question notification because you are a member of
OpenUpgrade Drivers, which is an answer contact for OpenUpgrade Server.