live to production to testing to live

**ehsander** · 2009-12-09, 06:57 PM

Hello,

I just can't get this one figured out by myself. I want to move from production back to live, which should ultimately result in a new install(?) with the data from the live installation and the customizations from the production installation. How can I merge these? I cannot interrupt the live installation for too long, about 20 people are depending on it.

The customizations are all made using the Studio/Module Builder/etc..

I've taken a look at this older post here but it wasn't a real help since it doesn't deal with the customized part.

Also, HI! I'm a newbie to this forum, but since I've fallen in love SugarCRM, I'll probably stick around.

Kind regards,

Sander

**ehsander** · 2009-12-10, 01:01 PM

Any help would be appreciated!

**eggsurplus** · 2009-12-10, 03:24 PM

We keep a personal dev, test, and a production site. Most of our customizations are non-Studio based. For those, we checkout our Sugar instance from SVN, make the changes, commit, put on test, then deploy when ready. When deploying we make sure to clear the cache so that the changes come through. The easiest way to do that is by using Quick Repair & Rebuild. For minor Studio changes (add field, etc) we'll do that on dev, make layout changes, commit layout changes, put out to test then live but only add the field using Studio. Sometimes we may just push the field change as a db script (add to fields_meta_data table as appropriate and to the appropriate *_cstm table as a column). For major Studio changes (new module, etc) we'll deploy either as a package (usually easiest) or manual file/db deploy.

Sorry about the messy post but hopefully that helps a bit.

**mikesolomon** · 2009-12-10, 03:36 PM

I copy changed files from my development to by live and then do a repair

If you have added custom fields using studio you will also need to copy the table fields_meta_data from dev to live