SugarCRM CE Version 6.5.24 (Build 509)

Hi,

We are currently running the version 6.5.24 of the SugarCRM CE, and we would very much like to upgrade to SuiteCRM.

Our environment is as follow:
Windows Server 8 (Sp2)
MS-SQL 2008
PHP 5.2.11 - Zend Engine v2.2.0
There was some customisation done, using the Studio or adjusting php files in the custom directory.

We are running into difficulties when trying to run the migration packages (using a migration test environment) available to us:

  • SugarCE Migration 6.5.x to Suite 7.6.6
    => The uploaded file is not compatible with this version of Sugar: SugarCRM System Version: 6.5.24
    => We overcame that issue by playing with the manifest in the package. But we then ran into other errors during the upgrade process:
    => SQL Error : Invalid object name ‘aos_pdf_templates’ - and indeed that table does not exist in our MSSQL database.
    => It seems to have completed part of the migration, but after another login attempt : SQL Error : Invalid object name ‘securitygroups_users’.Database failure. Please refer to sugarcrm.log for details.

  • SugarCE Migration 6.x to Suite 7.6.6
    => error 404 - File or directory not found when uploading the package
    => It feels like the package is corrupted. But I assume the result would be the same since sugarCRM seems to be missing tables not included in the migration package.

Any ideas? Suggestions?

I would focus on the “SugarCE Migration 6.5.x to Suite 7.6.6” package, which seems to be the correct one, and really try to get it to run correctly.

Can you try it again and post the upgradeWizard.log? Also check php_errors.log for anything relevant at the time of the upgrade process.

Make sure you reset all permissions correctly before starting, and disable cron jobs during the upgrade.

I tried the “SugarCE Migration 6.5.x to Suite 7.6.6” package again, ensuring the cron jobs were disabled.

I am still getting the error “404 - File or directory not found” when uploading the package.
the php-errors.log does not contain anything - I cleared it before running the upgrade.

The upgradeWizard.log, however contains the following lines:
Thu, 29 Jun 2017 14:44:26 +0200 [UpgradeWizard] - setting session variables…
Thu, 29 Jun 2017 14:44:26 +0200 [UpgradeWizard] - At upload.php
Thu, 29 Jun 2017 14:44:27 +0200 [UpgradeWizard] - finding new files for upgrade
Thu, 29 Jun 2017 14:44:33 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/ContactActivities2011_09_16_075755.zip ]
Thu, 29 Jun 2017 14:44:33 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Companies2011_09_15_175501.zip ]
Thu, 29 Jun 2017 14:44:33 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Companies2012_10_05_104307.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Companies2012_10_05_103313.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Companies2012_10_04_170818.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Companies2012_10_04_163757.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Clearer2013_05_01_152507.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Clearer2013_05_01_152415.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_Campaign_Comment2015_12_14_151258.zip ]
Thu, 29 Jun 2017 14:44:34 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Bridport_BO2012_07_23_111032.zip ]
Thu, 29 Jun 2017 14:44:35 +0200 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/langpack/SugarCRM-5.2.0j-LangPack-fr_FR-2009-09-16.zip ]
Thu, 29 Jun 2017 14:44:35 +0200 [UpgradeWizard] - *** UW using [ ] as source for patch files.

Is the last line the source of the issue?

Thanks in advance

You can start by clearing those zip files from there, or move them to some place as a backup.

Clear the whole upload/upgrades directory and try again. Let’s hope that solves the problem.

Sorry, just noticed your PHP version is VERY old. This should be causing all the issues.

Check the Compatibility matrix here: https://suitecrm.com/wiki/index.php/Compatibility_Matrix

And try to keep your PHP updated to what is needed for each SuiteCRM upgrade…

Thanks,
I will try these recommendations today and come back to you.

Feedback:
I was only able to update to upgrade to PHP 5.2.17 before I start to encounter issue - possibly sugar php compatibility, but I am no expert in PHP.

So we decided to waste no more time.
We are going to start from a clean install of SuiteCRM and perfom a “manual” data migration.

Thanks for your help.

Just realised that I forgot to mention that from PHP 5.2.17, the migration package gave me the same error:
[UpgradeWizard] - *** UW using [ ] as source for patch files.

*** UPDATE: ***
After failing to run the migration script from Sugar to Suite, we decided to start from a clean install, i.e. installing a clean version of SuiteCRM on a new server and perform a “manual” migration of data and customisations!

1. Application Server
Windows Server 2012 R2
IIS 8.5
PHP 7.1.8
SuiteCRM 7.8.5 LTS

2. Database server - located on a different server
MS-SQL Server 2008

After a painstaking manual process, we manage to migrate from SugarCRM to SuiteCRM.

However, we still have a number of issues that could become a show-stopper:

  • Unified Search does not work with our custom module.

  • The “Manage Subscriptions” is not working => a blank page is displayed.

  • Finally the Search itself is not working properly. The attached file shows a search returning no result while there is obviously at least one match.

However clicking on the ‘Use Basic Search’ gives the expected result ???!!!

Can you please help?