SugarCRM - is it a CRM? | HowToUseACRM.com

Every verdict, with its evidence

Core objects

In full

Accounts, Contacts, Opportunities and the three activity modules - Calls, Meetings and Tasks - are separate modules with their own records. The opportunity carries an Account Name field described as "The account to which the opportunity belongs", and the vendor states that "Each opportunity can relate to one or more contacts that are displayed in a subpanel on the Opportunities record view", with contacts assigned opportunity-specific roles. Activities attach to the opportunity as well: meetings and tasks both carry a Related To field holding "The related module record associated with the meeting", and the opportunity offers a historical summary of activities such as calls and meetings related to it. Contacts are related to accounts through their own Account Name field, so the person and the organization are distinct record types rather than two flavors of one.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/opportunities/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/contacts/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/meetings/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/tasks/

Verification: Verified

Pipeline stages

In full

The opportunity carries a Sales Stage field described as "The opportunity's current sales stage (e.g., Prospecting, Qualification, etc.)", and the vendor publishes the ordered stock sequence with the probability attached to each rung - Prospecting 10, Qualification 20, Needs Analysis 25, Value Proposition 30, Id. Decision Makers 40, Perception Analysis 50, Proposal/Price Quote 65, Negotiation/Review 80, Closed Won 100 and Closed Lost 0. The sequence is held in the sales_stage_dom dropdown list with a matching probability list, so the order and the weighting sit on the field rather than on a view, and administrators can add their own stages to it.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/ent/application_guide/opportunity_management/opportunities/, https://support.sugarai.com/knowledge_base/opportunities_forecasts/understanding_sugar_sales_stages/

Verification: Verified

Status

No verdict

The vendor's Opportunity Fields reference, in both the Sugar Sell and the Sugar Enterprise 26.1 guides, lists a field named Status on the opportunity, described only as "The status of an opportunity record". Neither guide states what values that field holds, whether Sugar maintains it, or how it relates to Sales Stage, and the Opportunities configuration page in the administration guide does not mention it at all. Pulling the other way, the vendor's knowledge base says the open-or-closed fact is a property of the stage: administrators "can classify the stock/custom sales stages as 'Open', 'Closed Won', or 'Closed Lost' by editing sales_stage_dom". So an attribute whose name is exactly this feature does exist on the record, and the vendor's own pages do not establish what it carries. Absence cannot be recorded against an enumeration that lists the field, and a pass cannot be recorded against a description that says nothing.

Searched: Read the Opportunity Fields tables in the Sugar Sell 26.1 and Sugar Enterprise 26.1 application guides, the Opportunities Configuration page in the Sell 26.1 administration guide, the Revenue Line Items page and the knowledge base articles on sales stages; searched the vendor documentation and the SugarClub community for the values of the opportunity Status field. No page enumerates them.

Verification: Pending vendor verification

Resolution

In part

Won and lost are stage values - Closed Won and Closed Lost sit at the end of the sales stage list with probabilities of 100 and 0 - but there is metadata behind them rather than only a name. The vendor documents that stock and custom sales stages are classified as "Open", "Closed Won" or "Closed Lost" in the sales_stage_dom list, and the administration guide relies on that classification when converting between tracking modes: if every related revenue line item was Closed Lost the opportunity is marked Closed Lost, and if all were closed with at least one Closed Won it is marked Closed Won. The outcome is therefore readable from the stage's own metadata rather than from an attribute whose job is the outcome.

Source: https://support.sugarai.com/knowledge_base/opportunities_forecasts/understanding_sugar_sales_stages/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/administration_guide/opportunities/, https://support.sugarai.com/documentation/sugar_versions/26.1/ent/application_guide/opportunity_management/opportunities/

Verification: Verified

Value

In full

The opportunity ships three monetary amounts - Likely, "The opportunity's most probable total amount", alongside Best and Worst - plus a Lost amount and a Forecasted Likely figure used by forecasting. A Currency Rate field holds "The base currency rate for an opportunity record", so Sugar treats the figures as money rather than as plain numbers, and where revenue line items are in use the amounts roll up from the line items' calculated amounts.

Verification: Verified

Scope of work

In full

Revenue line items attach to the opportunity and hold what is being sold. Each line item carries a Product taken from the product catalog or entered as new, a Quantity described as "The number of products being purchased", a Unit Price populated from the catalog, a discount and a calculated amount, and an opportunity in that mode requires one or more related line items whose amounts roll up to the opportunity. The administration guide offers an Opportunities-only alternative in which the opportunity tracks the whole deal on its own; in that mode the record still carries a Description field, "A description or other information about the opportunity".

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/revenue_line_items/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/administration_guide/opportunities/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/opportunities/

Verification: Verified

Expected close date

In full

Expected Close Date ships on the opportunity, documented as "The date the sale is likely to be completed". Revenue line items carry their own expected close date and the opportunity's date follows from them where line items are in use. The field feeds forecasting and is used as a grouping in the vendor's own report examples.

Verification: Verified

Actual close date

No verdict

The Opportunity Fields reference in the Sugar Sell and Sugar Enterprise 26.1 guides lists one date for the close - Expected Close Date, "The date the sale is likely to be completed" - and no field for the date an opportunity was actually settled. That would point at a gap, except that the same-named field on the revenue line item is documented differently: "The date when the revenue line item is expected to close or already has closed", and the opportunity's expected close date follows from its line items. So the vendor's own pages disagree about whether the shipped date holds the settled date after close, and no page states that Sugar stamps it. The vendor knowledge base article that addressed this, Capturing the Age of Closed Won Opportunities, is no longer served and redirects to the section index.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/opportunities/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/revenue_line_items/, https://support.sugarai.com/documentation/sugar_versions/26.1/ent/application_guide/opportunity_management/opportunities/

Searched: Read the Opportunity Fields tables in the Sugar Sell and Sugar Enterprise 26.1 application guides in full and found no second close date; read the Revenue Line Items field table, the Opportunities Configuration page and the Reports guide; tried the knowledge base article Capturing the Age of Closed Won Opportunities, which now redirects to https://support.sugarai.com/knowledge_base/opportunities_forecasts/ and could not be read.

Verification: Pending vendor verification

Opportunity owner

In full

The opportunity carries an Assigned to field, "The Sugar user assigned to the opportunity", distinct from the Date Created and Date Modified audit stamps that sit alongside it. Role permissions are written against it: Edit, Delete, List, Export and Record View can each be limited to Owner, meaning records where the user is the Assigned To user.

Verification: Verified

Linked buyer

In full

The vendor states that "Each opportunity can relate to one or more contacts that are displayed in a subpanel on the Opportunities record view", and that those contacts can be assigned opportunity-specific roles. The link to the person is separate from the Account Name field, which holds the organization.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/opportunities/

Verification: Verified

Record preservation

In full

Closed opportunities stay in the system and stay reportable. The vendor's report examples build summation and matrix reports filtered on the Closed Won sales stage and grouped by expected close date, and the stock Opportunity Metrics dashlet "provides information regarding opportunities related to the account that are won, lost, and active along with the relevant dollar amounts", all of which require the closed records to persist and remain queryable.

Verification: Verified

Structured lost reasons

In part

No lost-reason field appears anywhere in the Opportunity Fields reference for either Sugar Sell or Sugar Enterprise 26.1; the only Lost field is a monetary one, "Representing revenue that has been lost". The buyer builds it: Studio creates new fields on stock modules including Opportunities, and offers Dropdown, MultiSelect and Radio among its field types, and the Reports module groups and counts by any field on the module, so a dropdown of loss reasons can be added and counted in a summation report.

Verification: Verified

Email sync

In part

Mail goes out of the CRM but not into it. Users connect an outgoing mail account - Google, Exchange Online, Outlook or generic SMTP - and compose and send from inside Sugar, and "Emails sent from Sugar are automatically archived in Sugar and related to records that match the email addresses in the message". The return leg is explicitly ruled out by the vendor: "Because Sugar is not an email application, users cannot receive email directly to Sugar via their user email accounts." What is offered instead is the Sugar Email Archiving service, where users forward mail to a monitored address that imports it and links related records, and the Sugar Connect add-in inside Gmail or Outlook, which archives messages on demand or by rule. A forwarding address and a mail-client add-in are not a mailbox sync, so the connection runs one way.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/emails/, https://support.sugarai.com/documentation/plug-ins/sugar_connect/sugar_connect_user_guide/

Verification: Verified

Calendar sync

In full

Sugar Connect, the vendor's own add-in for Gmail and Outlook, syncs the activity objects both ways: "Sugar Connect will sync meetings between Sugar and your Google/Outlook calendar", with meetings and calls created in the mail client landing in Sugar's Meetings and Calls modules and Sugar meetings appearing in the external calendar, on a repeating interval. Two constraints are worth stating. The route runs through software installed into the user's mail client rather than a server-side connection, and Sugar's own calendar offers only a one-way feed - a published iCal URL for use in another calendar application, where "The calendars are viewable as read-only in the external calendar applications and any edits to existing activities can only be done in Sugar". Ruled 31 Aug 2026: Sugar Connect is the vendor's own add-in - the two-way sync is already built, and the buyer installs it rather than builds it, so it counts as the platform's own capability. The verdict would be In part on Sugar's built-in calendar alone, which publishes read-only.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/calendar/, https://support.sugarai.com/documentation/plug-ins/sugar_connect/sugar_connect_user_guide/

Verification: Verified

Schedulable activity types

In part

The type set is fixed at three and covers meeting, call and task. Meetings are scheduled with start and end date and time, an assigned user, guests drawn from contacts, leads and users, and a Related To record such as an opportunity. Tasks carry a start date, a due date, a priority, a status such as Not Started or In Progress, an assigned user and their own Related To record. Calls are a third module of their own. Neither meetings nor tasks ship a user-definable activity type: the only Meeting Type field records "The application (e.g., Sugar, WebEx, GoToMeeting, etc.) hosting the meeting", not the kind of work.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/meetings/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/tasks/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/calendar/

Verification: Verified

Opportunity reporting

In full

All three are available, though not from the same place. The report builder alone cannot do two of them: it offers Rows and Columns, Summation, Summation with Details and Matrix reports with SUM, AVG, MAX, MIN and count, and no percentage or ratio, so no rate can be built in it. The rates come instead from the Enhanced Forecasting reports built into Sugar dashboards, which include a Win Rate Trend defined as the number of Closed Won opportunities divided by the total number of closed items in the period - a stated proportion, not a count beside a count - and Funnel Velocity and Conversion reports which show "what percent of the previous stage made it at least as far as the next stage", by opportunity count and by revenue. Forecasting is native in its own right through the Forecasts module, the opportunity's Forecast Stage and Forecasted Likely fields, and the Enhanced Forecasting pipeline and forecast-versus-prior-quarter reports. The constraint to state: the vendor says the Enhanced Forecasting set is "available to Sugar Sell Premier customers" on SugarIdentity-enabled SugarCloud instances, so a buyer on a lower subscription or on an on-site instance has the forecast but not the two rates. Ruled 31 Aug 2026: a capability restricted to the vendor's own cloud deployment still counts as native, on the same principle as plan tiers - the vendor built it and sells it, and whether a buyer chooses that deployment is the buyer's decision. An on-site Sugar Enterprise instance does not get these reports, and a buyer evaluating on-site should read this verdict with that in mind.

Source: https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/reports/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/user_interface/dashboards_dashlets/enhanced_forecasting_reports/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/user_interface/dashboards_dashlets/sugar_dashlets/, https://support.sugarai.com/documentation/sugar_versions/26.1/sell/application_guide/opportunity_management/opportunities/

Verification: Verified