System Migration 4.2.0d to 4.5.1d

[asc]

System Config:

OS: FreeBSD 6.0
SugarCRM: Open Source Versions 4.2.0d moving to 4.5.1d
Apache: 2.0.58
PHP: 5.2.1 or 4.46 are available in ports collection
MySQL: 5.0.19

Summary:

I have inherited an old CRM (4.2.0d) system that is currently limping along, but in use. I would like to move it to a more current system. I've tried many approaches and I'm not sure how to make this work. I would like to use PHP5.

I was able at one point to get 4.2.0d upgraded to 4.2.1d, but then I need to do some magic to get to 4.5.1d because the mbstring stuff seems only to work with php5 on this machine. That may be an error on my part.

What I'd like to do is get a new install of 4.5.1d up and working with php5, which I was able to do at one point. Then, somehow migrate the data from the appropriate tables in the old database instance to the new database instance.

Questions:

Migrate data to new db approach:
We have a backup made by the default backup utility, but there seems to not be a restore for this. If such a tool exists, will it cross the version gap from 4.2.0d to 4.5.1d?

Upgrade path approach:
If I follow the 4.2.0d -> 4.2.1d -> 4.5.1d upgrade path, at what point can I change over to php5? This is assuming that php5 is required for mbstring, is this a valid assumption?

Thanks for any insights,

-ASC

[sanver]

You have to manually upgrade to latest version from 4.2.

Setup the latest version Sugar, map the old db structure with new one and then do import/export data.

Do let me know in case you need help.

Sanjay Verma
Sanver E-Solutions
www.sanver.com
+1 646 736 7546
+44 20 8133 6894

System Config:

OS: FreeBSD 6.0
SugarCRM: Open Source Versions 4.2.0d moving to 4.5.1d
Apache: 2.0.58
PHP: 5.2.1 or 4.46 are available in ports collection
MySQL: 5.0.19

Summary:

I have inherited an old CRM (4.2.0d) system that is currently limping along, but in use. I would like to move it to a more current system. I've tried many approaches and I'm not sure how to make this work. I would like to use PHP5.

I was able at one point to get 4.2.0d upgraded to 4.2.1d, but then I need to do some magic to get to 4.5.1d because the mbstring stuff seems only to work with php5 on this machine. That may be an error on my part.

What I'd like to do is get a new install of 4.5.1d up and working with php5, which I was able to do at one point. Then, somehow migrate the data from the appropriate tables in the old database instance to the new database instance.

Questions:

Migrate data to new db approach:
We have a backup made by the default backup utility, but there seems to not be a restore for this. If such a tool exists, will it cross the version gap from 4.2.0d to 4.5.1d?

Upgrade path approach:
If I follow the 4.2.0d -> 4.2.1d -> 4.5.1d upgrade path, at what point can I change over to php5? This is assuming that php5 is required for mbstring, is this a valid assumption?

Thanks for any insights,

-ASC

[asc]

Yes please. I do need help. Do all the data in every table get copied in? Or are there only some that need transferred?

I can make a fresh installation of 4.5.1d with php5 and get it running, but I'm not sure how which data to transfer into the new database instance from the old one.

Feel free to email me if you like. aclapp@verilan.com

-ASC