# Example: database backup
mysqldump -u <user> -p <database_name> > suitecrm_backup_$(date +%Y%m%d).sqlComplete every item on this page before running an upgrade, regardless of which method you use.
Confirm that your current PHP version, database, and web server are supported by the target SuiteCRM version.
If your stack needs updating, plan that work separately and complete it before upgrading SuiteCRM.
Never run an upgrade directly on production. Clone your production environment ā files and database ā to a development or staging server and complete the full upgrade there before touching production.
This is especially important if you have customisations. See Large or Complex Upgrades for a full guide to planning this process.
Back up both your SuiteCRM files and your database before proceeding. If the upgrade fails or causes issues, a clean backup is the only reliable recovery path.
# Example: database backup
mysqldump -u <user> -p <database_name> > suitecrm_backup_$(date +%Y%m%d).sqlEnsure the backup is stored outside the SuiteCRM root directory.
Download the appropriate upgrade pack from the SuiteCRM releases page.
Upgrade packs are named in the format SuiteCRM-Upgrade-7.x.x-to-7.x.x.zip. Ensure you are downloading the pack for your exact starting version.
The upgrade process requires generous PHP limits. Update your php.ini (or equivalent server configuration) with the following minimum values:
| Setting | Minimum value |
|---|---|
|
60M |
|
60M |
|
3000 |
|
6000 |
|
256M |
Restart your web server after making changes for them to take effect.
These settings apply to the Upgrade Wizard. If you are using the CLI upgrade, the PHP limits for web requests are less relevant, but memory_limit still applies to the CLI PHP process.
If using the Upgrade Wizard, the maximum upload size must also be increased within SuiteCRM itself:
Log in as an Administrator.
Navigate to AdminĀ āŗ System Settings.
In the Advanced section, set Maximum Upload Size to 30000000 (30 MB).
Click Save.
If your server uses an opcode cache (such as OPcache or APC), disable it before upgrading. A stale opcode cache can cause the upgraded application to behave unpredictably.
Re-enable it after the upgrade is complete and you have confirmed the instance is working correctly.
The web server user must have write permissions to the SuiteCRM root directory and all subdirectories during the upgrade. The upgrade process adds, replaces, and removes files across the installation.
# Example: set ownership on Linux (adjust user/group to match your web server)
chown -R www-data:www-data /path/to/suitecrmIf running the CLI upgrade, be aware that any files created during the upgrade will be owned by the user running the command ā not necessarily the web server user. See CLI Upgrade: File Permissions for details.
The Upgrade Wizard requires that config.php in the SuiteCRM root directory is writable by the web server user before it will proceed.
Before starting, confirm:
ā Target version is compatible with your PHP, database, and web server
ā Development instance tested (or this is the development run)
ā Files and database backed up
ā Correct upgrade pack downloaded
ā PHP settings updated and web server restarted
ā SuiteCRM upload size set to 30 MB (Wizard only)
ā Opcode caching disabled
ā Web server user has write access to the SuiteCRM root
ā config.php is writable (Wizard only)
Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.