SuiteCRM

Last reviewed Sep 13, 2026 · 895 words

SuiteCRM wins on one axis and loses on one axis, and you should decide which matters before installing anything. On features it is the most complete free CRM you can self-host: leads, opportunities, quotes, campaigns, cases, projects, workflow automation, a report builder, a module builder and a REST API, all AGPL-3.0 and all on your own MySQL. On feel it is a 2013 SugarCRM fork with a newer front end bolted on, and a sales team that has used HubSpot will say so on day one. The 2 GB RAM minimum in the catalogue is honest; give it 4 GB and a real CPU or the list views crawl.

Who actually runs it

The users I see stick with SuiteCRM are nonprofits and membership organisations that need campaigns, cases and donor-style records in one system with no per-seat cost; small B2B sales teams of 5 to 30 that want quotes and pipeline without a subscription; and consultancies that customise it for clients, because Studio and Module Builder let you add fields, relationships and whole modules from the admin panel without touching PHP. It is a poor fit for a two-person startup that wants a fast pipeline board, and for anyone who expects a mobile app in the box.

Two smaller projects cover those cases better. EspoCRM is lighter, faster and prettier with a similar data model, and is what I recommend to most people who arrive asking about SuiteCRM. Twenty is the modern-UI option for teams that live in a pipeline view. If you want CRM plus invoicing, inventory and accounting in one place, Odoo is the bigger sibling in the CRM and ERP category and the safer bet for a company that will grow into those modules.

SuiteCRM 8 or 7: pick 8 for a new install

SuiteCRM 7 is the long-lived line: the classic interface, the largest pool of third-party modules and themes, and a code base every SugarCRM veteran knows. SuiteCRM 8 rebuilt the front end in Angular on a Symfony back end while keeping the 7 core underneath as a "legacy" directory, which is why an 8 install still shows some 7-era screens. Version 7 is on long-term support and its end-of-life has been announced and extended more than once, so treat it as a migration target, not a destination.

For a fresh install, choose 8 unless you depend on a specific 7-only module. Check the module first. The extension ecosystem, including the paid SuiteCRM Store, still has plenty of things marked "7.x only," and a CRM you cannot extend is not the CRM you wanted.

Installation is a real LAMP job, not a container you forget

There is no official Docker image. Community images and Bitnami-derived ones exist, and they are fine for evaluation; for production I would install on a plain PHP 8 and MariaDB stack, because upgrades of SuiteCRM 8 are done through its own upgrade command and are far easier to reason about outside an opinionated container. The pieces you need:

# after unpacking the release into /var/www/suitecrm
chown -R www-data:www-data /var/www/suitecrm
sudo -u www-data ./bin/console suitecrm:app:install \
  -u admin -p 'change-me' -U suitecrm -P 'db-pass' -H 127.0.0.1 -N suitecrm -S http://crm.example.com -d no

Then add the cron entry that runs bin/console suitecrm:app:scheduler every minute as the web user; without it workflows, email polling and scheduled reports silently never fire, which is the most common "SuiteCRM is broken" report I see. Point the web root at public/, not the repo root, and enable mod_rewrite or the nginx equivalent.

Set PHP memory_limit to at least 256M and upload_max_filesize to something sensible for email attachments. Back up the database and the upload/ directory together; documents, email attachments and imports all live in upload/ and a database-only backup restores a CRM full of broken links.

The features that are genuinely good

The workflow module lets you trigger actions on record create or update with conditions, so "assign new web leads from country X to rep Y and email them within an hour" is a five-minute configuration. Reports are built in a drag-and-drop UI against any module and can be scheduled and emailed. The inbound email module turns a mailbox into cases, which is the feature that keeps support-desk users on it. Security groups give row-level access control by team, which most small CRMs do not offer at all. And the REST API under /Api/V8/ is a JSON:API implementation that integrators find more predictable than the 7-era one.

What I'd do

If you are a nonprofit or a sales team over ten people that needs campaigns, cases and row-level permissions, install SuiteCRM 8 on a dedicated 4 GB VM with MariaDB, set up the scheduler cron on day one, and budget a week for field and layout customisation before showing it to users. Everyone else should try EspoCRM first; it does 80 percent of this with a third of the weight and a UI that does not need apologising for. If accounting and inventory are on the roadmap, skip both and go to Odoo.