./vendor/bin/robo upgrade:suite <upgradeZipFile> <logFile> <pathToSuiteCRMInstance> <adminUser>The CLI upgrade runs the upgrade process from the command line on your server, bypassing web server timeout and upload size constraints. It is the recommended method for larger databases or if the Upgrade Wizard has previously timed out.
Before proceeding, ensure you have completed all steps on the Before You Upgrade page, including backing up your instance.
Two CLI methods are available depending on your SuiteCRM version:
| Method | Version requirement |
|---|---|
|
SuiteCRM 7.11.3 and newer |
|
All 7.x versions |
Use the robo command if your version supports it. The silentUpgrade.php script is available as a fallback for older installations.
Download the upgrade pack from the SuiteCRM releases page and copy it into the SuiteCRM root directory.
From the SuiteCRM root directory, run:
./vendor/bin/robo upgrade:suite <upgradeZipFile> <logFile> <pathToSuiteCRMInstance> <adminUser>| Argument | Description |
|---|---|
|
Path to the upgrade ZIP file (e.g. |
|
Path and name for the log output file (e.g. |
|
Absolute path to your SuiteCRM installation. Use |
|
Username of a SuiteCRM administrator account |
Example:
./vendor/bin/robo upgrade:suite SuiteCRM-Upgrade-7.12.x-to-7.13.0.zip upgrade.log . adminDownload the upgrade pack and copy it to a location accessible from your server. Note the full path.
php -f <path-to-suitecrm>/modules/UpgradeWizard/silentUpgrade.php \
<upgradeZipFile> <logFile> <pathToSuiteCRMInstance> <adminUser>| Argument | Description |
|---|---|
|
Full path to the upgrade ZIP file |
|
Full path to a log file (will be created if it does not exist) |
|
Full path to the SuiteCRM installation directory |
|
Username of a SuiteCRM administrator account |
Example:
php -f /var/www/suitecrm/modules/UpgradeWizard/silentUpgrade.php \
/tmp/SuiteCRM-Upgrade-7.12.x-to-7.13.0.zip \
/var/www/suitecrm/upgrade.log \
/var/www/suitecrm \
adminAny files written during the upgrade will be owned by the user running the command — which is often root in server environments. If Apache (or your web server) runs as a different user, it will be unable to read or write those files, causing the application to fail.
After the upgrade completes, reset permissions:
# Adjust user:group to match your web server (e.g. www-data:www-data, apache:apache)
chown -R www-data:www-data /path/to/suitecrm
find /path/to/suitecrm -type d -exec chmod 755 {} \;
find /path/to/suitecrm -type f -exec chmod 644 {} \;Reset file permissions as described above.
Log in as an Administrator and navigate to Admin › Repair.
Run Rebuild Relationships.
Run Rebuild Extensions.
Re-enable opcode caching if you disabled it before the upgrade.
Review the log file you specified in the command for details on any errors. The upgrade wizard log is also written to:
<suitecrm-root>/upgradeWizard.log
See also Logs and Known Issues.
Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.