CRM Analytics. Standard reports vs CRMA. Know when Sales Cloud is enough.

What this means for your store

Standard reports hit live CRM records with report-type limits on objects and row counts. CRM Analytics pre-computes datasets built for heavy SAQL, external blends, and interactive exploration. A rep checking this week's open opps does not need CRMA. Ops correlating three years of pipeline with marketing touches and ERP order files will hit timeouts and export caps in standard reporting.

Scenario on a real storefront

A UK building-materials wholesaler hits row limits joining Opportunities to a custom line object. They pilot one CRMA lens before moving the whole “Pipeline by family” report:

# Decision checklist

Stay on standard reports when:
  - < 50k rows, single report type, live refresh is fine
  - Users live in list views + one tabular report
  - No external data blend

Move to CRMA when:
  - Joins exceed report type (Opp + Order + ERP object)
  - SAQL: cohort win rates, stage velocity, fiscal YoY
  - Partner portal on Experience Cloud needs embedded analytics

# Pilot: one lens vs legacy report total
# Adoption: weekly active users before decommissioning old dashboard

What to do next

• Same KPI in both places guarantees confusion - reps trust whichever number matches commission and ignore the other.
• CRMA adds licence and refresh cost; finance summaries often stay on scheduled standard-report exports.
• Run a parallel month reconciling by stage and owner before deleting the legacy Sales Cloud dashboard.

Bottom line

Standard reports for day-to-day CRM slices; CRMA for volume, blends, and advanced metrics. Pilot one high-value report, reconcile totals, then expand - do not lift every tabular report.