Dedicated CRM

SuiteCRM

Not a CRM - fails on status, actual close date, opportunity reporting

Every verdict, with its evidence

Core objects

In full

Opportunities, Accounts, Contacts, Calls, Meetings and Tasks are separate database modules. The Opportunity module's field definitions include an account_id/accounts link (organization) and a separate contacts link (person), plus tasks, calls and meetings link fields, so all four core object kinds exist as distinct, mutually linkable records rather than one contact object with a flag.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php, https://docs.suitecrm.com/user/core-modules/opportunities/

Verification: Verified

Pipeline stages

In full

The Opportunity's sales_stage field is an enum backed by a fixed, ordered list (Prospecting, Qualification, Needs Analysis, Value Proposition, Id. Decision Makers, Perception Analysis, Proposal/Price Quote, Negotiation/Review, Closed Won, Closed Lost) defined in the vendor's own language file, and every Opportunity record stores its current stage in that field.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/include/language/en_us.lang.php, https://docs.suitecrm.com/user/core-modules/opportunities/

Verification: Verified

Status

Not at all

The vendor's own field enumeration for the Opportunity module (vardefs.php) defines no status field. Open-versus-closed is only readable by checking whether sales_stage equals the reserved terminal values Closed Won or Closed Lost - there is no field separate from stage.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php

Verification: Verified

Resolution

In part

Win/loss lives inside the same sales_stage list as the pipeline stages themselves - Closed Won and Closed Lost are two of the ten dropdown values, not a distinct field. This is the stage-metadata case.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/include/language/en_us.lang.php

Verification: Verified

Value

In full

The Opportunity module ships a native currency field (amount), plus amount_usdollar and a linked currency_id/currency_name for multi-currency deals.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php

Verification: Verified

Scope of work

In full

The bundled Advanced Open Sales (AOS) Quotes module carries product and service line items with quantity, price, discount and tax, and a Quote's first panel includes a related-Opportunity field, so what's being sold is trackable as structured line items linked to the deal.

Source: https://docs.suitecrm.com/user/advanced-modules/sales/

Verification: Verified

Expected close date

In full

The Opportunity module has a native date field, date_closed, whose vendor-supplied label is literally 'Expected Close Date'.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/language/en_us.lang.php

Verification: Verified

Actual close date

Not at all

date_closed is the only close-date field the Opportunity module ships, and the vendor's own label for it is 'Expected Close Date'. No second field exists, and no vendor documentation describes date_closed also capturing the actual close date.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php, https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/language/en_us.lang.php

Verification: Verified

Opportunity owner

In full

Opportunities use SuiteCRM's core 'assignable' bean template, which ships assigned_user_id as a standard user-reference field distinct from the separate created_by field every module carries.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php

Verification: Verified

Linked buyer

In full

The Opportunity module defines a 'contacts' link field distinct from its 'account_id'/'accounts' organization link, so a person record can be related to the deal separately from the company.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php

Verification: Verified

Record preservation

In full

Closed Opportunities are not removed from the system; the Reports module documentation describes grouping and totaling Opportunities by Sales Stage, which includes the closed stages, showing closed records remain and feed reporting.

Source: https://docs.suitecrm.com/user/advanced-modules/reports/

Verification: Verified

Structured lost reasons

In part

No lost-reason field ships on the Opportunity module. Studio documentation confirms admins can add a custom dropdown field to any module, and the Reports module documentation confirms it can group and count records by any field, so a buyer-built structured reason field is countable.

Source: https://docs.suitecrm.com/admin/administration-panel/studio/, https://docs.suitecrm.com/user/advanced-modules/reports/

Verification: Verified

Email sync

In part

Users can send mail from the CRM through a configured outbound SMTP account, and non-personal inbound mailboxes are polled and imported automatically by the 'Check Inbound Mailboxes' scheduler. For personal user mailboxes specifically, vendor documentation states emails 'are not stored in SuiteCRM unless manually imported.'

Source: https://docs.suitecrm.com/admin/administration-panel/emails/automatic-email-importing/, https://docs.suitecrm.com/admin/administration-panel/emails/email/

Verification: Verified

Calendar sync

In full

The current Calendar Sync framework performs bidirectional sync of meetings between SuiteCRM and Google Calendar (via OAuth) or a CalDAV server: 'updates to the calendar in SuiteCRM will be synchronized to the external calendar and updates to the external calendar will be synchronized to SuiteCRM.'

Source: https://docs.suitecrm.com/user/calendar-sync/

Verification: Verified

Schedulable activity types

In part

Scheduling is limited to the three fixed activity modules the Opportunity links to - Calls, Meetings and Tasks. No vendor documentation describes buyer-defined activity types.

Source: https://github.com/salesagility/SuiteCRM/blob/hotfix/modules/Opportunities/vardefs.php

Verification: Verified

Opportunity reporting

Not at all

The core Reports module only offers count/minimum/maximum/sum/average with group-by - no rate calculation. The vendor's own Sales Forecast & Quota module documents revenue forecasting (amount weighted by probability) and quota tracking, but its user guide contains no mention of win rate or stage-to-stage conversion rate.

Source: https://docs.suitecrm.com/user/advanced-modules/reports/, https://store.suitecrm.com/docs/sales-forecast/user-guide

Verification: Verified