Sample data. Fictional companies. Nothing here is real.
GTMIQRead-only demo · Prototype
← Back to overview

CRM data model and change governance

A reference design for lifecycle stages, deal stages, fields and how changes get rolled out.

Sample data. Fictional companies. Nothing here is real.

HubSpotUsed in my sales careerSalesforceUsed in my sales career

I've used both hands-on in sales roles, and HubSpot early on at Scarlet Risk. I haven't owned either as an admin or architect. This page shows how I would structure it.

Lifecycle stages and qualification criteria

StageMeaningEntry criteria
SubscriberOpted in to content or newsletterValid email, consent recorded
LeadGave contact details or was sourcedEmail + company domain present
MQLFits ICP and shows intentFit score ≥ 60 and at least one intent signal in 30 days
SQLSales accepted after first conversationPain confirmed, buying role known, next step booked
OpportunityActive deal with a defined scopeDeal created with amount, close date and stage
CustomerSigned and billedClosed-won deal linked to the company

Opportunity stages and exit criteria

StageProbabilityExit criteria (to move on)
1. Discovery10%Pain and impact written down; economic buyer named
2. Solution fit25%Demo done; decision criteria captured
3. Proposal50%Quote sent; decision process and timeline confirmed
4. Negotiation75%Champion confirmed; legal/procurement engaged
5. Closed won / lost100% / 0%Signed order form, or a loss reason picked from the list

Key fields and validation rules

FieldTypeRule
Lifecycle stagePicklistCan only move forward, except an admin reset back to Lead
Lead sourcePicklistRequired on create; no free text
AmountCurrencyRequired from Proposal; must be > 0
Close dateDateRequired; cannot be in the past on an open deal
Loss reasonPicklistRequired when stage = Closed lost
Economic buyerContact lookupRequired to enter Proposal

HubSpot → Salesforce object and field mapping

HubSpotSalesforceNote
Contact (lifecycle = Lead/MQL)LeadBefore conversion, a HubSpot contact maps to a Salesforce Lead
Contact (SQL and later)ContactConverted Lead becomes Contact under an Account
CompanyAccountMatch on primary domain
DealOpportunityDeal stage → Opportunity StageName via a lookup table
Deal amountOpportunity.AmountSame currency; no rounding
Lifecycle stageLead.Status / custom fieldSalesforce has no single lifecycle field; a custom field keeps the history

Sync design: source of truth per field

FieldSource of truthRule
Email, name, titleCRM where the record was createdEnrichment fills blanks only; it never overwrites a value a person typed
Company size, industryEnrichment toolRefreshed monthly
Deal stage, amountSalesforceThe rep's working system wins on conflict
Marketing consentHubSpotAlways flows one way, from marketing to sales

Sync errors go to a review list rather than being retried forever. Each record carries a "last synced" timestamp so stale records are easy to find.

How I roll out a CRM change

  1. 1.Request. Written request with the problem, the owner, and which reports or automations it touches
  2. 2.Sandbox. Build the change in a sandbox or test portal first, never in production
  3. 3.Test. Test with sample records: create, edit, a validation rule failing, and the sync running both ways
  4. 4.Release note. A short note for users: what changed, why, and what they need to do differently
  5. 5.Rollback. Written undo steps and a field export taken before release, so the change can be reversed