How to migrate from Pro 6.2 to CE 6.2

[glynne]

Hi

I need to migrate from Pro 6.2 to CE 6.2. Can you please detail the steps that I need to follow, or refer me to an existing thread that correctly details. I have found a number of threads, but the ones I have come across haven't worked in my case.

Hosting on Hostgator, mysql.

Cheers
Glynne

[sts]

First: I have experience with different versions and editions of Sugar but did not do such a migration PRO->ENT before ... so don't expect a detailed step by step plan from me.

I'll just give you some hints from my point of view:

1) As far as I see the Pro-Database is a superset of the Ent-Database. So you could try to install a CE in parallel to the Pro-installation and configure it to use the Pro-database. I'd expect and hope that this should work (but off course you'll only see the CE fields and any data in other fields will be not available).
2) Check: how did you use sugar pro? Did you do any customizations? Did you use Pro-specific stuff?
If you did some customizations it depends on how you did it if it will be possible or how complex it will be to migrate them. And you won't be able to use Pro-specific stuff anymore off course (but maybe you could find something fitting your needs in SugarForge) [but I'm sure you know that].
3) It would be nice (and it would help you to get help from the users of this forum) if you could share your experience with us ... What did you try and which were the results?

[glynne]

Thanks for the advice Stefan.

Yes I did have about 15 additional fields added to the Accounts and Contacts table. apart from a change in layouts in the Accounts and Contacts views to reflect the extra fields, these were the only customisations.

The process I followed was:
- installed CE v6.2.
- created a new mySql database
- imported the dataset from the Pro database into the new mySQL database
- edited the config.php to point to the new database
- rebuilt the relationships, etc from within Sugar CE

It appeared to go OK, as all the records came across. But then I noticed that the view/edit layouts didn't reflect the layouts from Pro. Whilst the fields were in the tables, it wasn't displaying them.

Also, I had various "undefined" errors showing up in the Studio when I went into view the various modules. also, there was no help showing over in the right hand panel - just completely blank.


Also, the Label names of the customised fields also hadn't come across, and had reset to the system name, i.e. starting with LBL_ etc.

So my new instance is running with all the data there, with no admin errors, but with definite problems.

I would appreciate feedback if there is a better way to migrate across to CE from Pro.

Cheers
Glynne

[sts]

Did I understand you right that you did not do any code changes and field definitions in the new CE installation? When creating custom fields Sugar allways creates php files (respectively adding the new stuff to existing files) describing the fields and the system uses this descriptions to access the data in the database.

[rafael.q.g@hotmail.com]

Now that you have your data available on your sugar ce, you could try to add your metadata customized files from PRO to CE. Then you will have the forms and lists looking the same.

Copy also all extended/custom vardefs and language files created by your customization, and later run a repair and rebuild, just to make sure that your sugar ce will understand your custom fields.

[glynne]

Did I understand you right that you did not do any code changes and field definitions in the new CE installation? When creating custom fields Sugar allways creates php files (respectively adding the new stuff to existing files) describing the fields and the system uses this descriptions to access the data in the database.

Hi Stefan
Correct, I didn't do any code changes and field definitions in CE before importing the dataset. I'm sensing from your question that I should have created them beforehand? I wasn't aware that Sugar created php files when adding new fields and had thought that all the neccessary table structure/definitions would be brought through when I migrated the database.


@rafael
Can you explain what you mean by "add your metadata customized files from Pro to CE" please. I'm assuming you're referring to some php files? And I'm not sure how I would go about doing this - can you either give me detailed instructions or point me to a link?

Thanks a lot guys.
Glynne

[sts]

Hi Glynne,

Rafael's and my last posts are more or less addressing the same thing ...
I mentioned the php files created/changed by Studio whenever creating a new custom field or changing labels or do any layout changes etc. Rafael tried to explain which files Studio manipulates - these are vardefs-, language- and viewdef-files (they are all text files with .php extension) - and how to get them to work in the new installation (running repair/rebuild in admin section).
Please have a look into the developer guides. You'll find some stuff there concerning those files. They are located in the module/<modulename> respectively custom/module/<modulename> subdirectories. So for customizations in Contacts module you'll have to look into module/Contacts/... and custom/module/Contacts/...

Regards
Stefan