We have a production database on Sugar CE 6.5.16. Weād like to give SuiteCRM a try by installing it in a new directory and using a new database (donāt want anything touching our production file.)
Can we just import a sqldump file of our Sugar database into an emtpy Suite database? (I wouldnāt think so becasue of getting duplicate admin records, etc.)
Where are the docs on how to move from Sugar to Suite?
What is the best/quickest way to make a clone of my SugarCRM directory in either FTP or SSH?
What download package do I use? This one? SuiteCRM-Upgrade-6.5.x-to-7.0.2
If so, do I then have to do the upgrade to 7.1.1.
(BTW, the Upgrades link for 7.0 on the download page does not work well in Chrome on OS X. Sometimes it drops down, other times it doesnāt. There is some bad javascript code in there. The others work OK but not that one. Works fine in Safari)
I can see that the Suite was (is) intended as an Upgrade for Sugar. That probably works for most people. But there are lots of people who just canāt ātake the chanceā by upgrading a production system with an untried product like Suite.
(We always felt it was ātaking a chanceā just upgrading Sugar from one CE release to the next!! And anyone who has been with Sugar for 7 years like we have has stories they can tell you!)
If Suite wants to differentiate itself from Sugar it would be great to have a method to easily allow the CRM system to be installed with an existing database. Iāve been after Sugar to do that for seven year nowā¦ but it has never been done. If any Sugar modules get corrupted itās a major PITA to reinstall it and use the existing (non-corrupted) database. Iāve done it several times so I know the drill and it is not fun, pretty, or easy deleting the duplicate records in some of the tables.
Create a zip of your sugar file structure
Create a mysqldump of your live database.
Unzip the files in another folder
Install the database
Set up the sugar config to point to the newly installed database.
Then upload the packages and run through the upgrade wizard
Quickest way depends on what you most like to use personally I would do it all via SSH
Yes you are correct since you are running SugarCRM CE 6.5.15 you will need to first use the SuiteCRM-Upgrade-6.5.x-to-7.0.2 package then upgrade again to 7.1,1
I understand the issues in upgrading this is why I suggested doing the upgrade on copy of your live instance first, then if you experience any problems with the upgrade you they will not effect your live instance.
You can link up your existing database to a fresh install of Suite by changing the config to point towards a COPY of your existing database and running a repair and rebuild. But this may cause issues with any customisations you may have.
Thanks for the excellent reply. Since this will entail:
Getting a mysquldump file
Creating a new database
Loading said database
Zipping and unzipping my Sugar directory (which is huge!)
Upload the both upgrade files and running wizard
I will wait until I have sufficient time to get this all done.
You are right about one thingā¦ trying to zip and unzip a directory as large as Sugar via an FTP client would take all day. SSH is the only way to go here.
I also have to decide if SuiteCRM is going to be around for the long-termā¦ or if I should be looking at vTigerā¦ although I donāt know if there is a migration path from Sugar to that fork either.
I canāt believe Sugar is just going to walk away from supporting their loyal CE usersā¦ people who have contributed to their codebase and community help forums over the past seven years or so.
I found some time this evening so I did the install. Had a few minor glitches (see thread about ātext screenā but finally got it working well.
BTW, if you want to clone our sugar directory, this is faster and easier than zipping it and unzipping it:
(assume your SugarCRM directory is named āsugarā in your document root, and you want a new directory called āsuiteā)
cp -R -p sugar suite
Now that the database is updated, I assume I can do a clean install of SuiteCRM and just point the config file to it? Iām wondering if some of my old Sugar core modules might be a bit wonkyā¦ and would be nice to have a clean Suite to test. Would this be a problem?
I am going to try this after hours this evening. Take our SugarCRM and cp files, customizations and settings off to a newly created instance and then upgrade to SuiteCRM. So far I keep encountering a white screen that I canāt seem to do much with doing a direct upgrade from SugarCE to SuiteCRM.
Thanks. Have tried 777 on all files and directories in our cloned instance. No luck. Owner is correct as previous Sugar CE upgrades have happened throughout the 6.5.x codebaseā¦
I donāt see anything of consequence in the logfile. I uploaded the log file to my [similar] thread on issues upgrading, but havenāt heard anything yet.
A white-screen-of-death is often a PHP error. Turn on error reporting in the .htaccess file :
php_flag display_startup_errors on
php_flag display_errors on
php_flag html_errors on
php_flag log_errors on
php_value error_log /home/path/public_html/domain/PHP_errors.log
(change the path for your own server)
Run Suite and then check the log file. I donāt think anything will display on the screen with above code.
If you canāt use .htaccess you should be able to use a .user.ini file instead which would would use this code (I think!)