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
| Stage | Meaning | Entry criteria |
|---|---|---|
| Subscriber | Opted in to content or newsletter | Valid email, consent recorded |
| Lead | Gave contact details or was sourced | Email + company domain present |
| MQL | Fits ICP and shows intent | Fit score ≥ 60 and at least one intent signal in 30 days |
| SQL | Sales accepted after first conversation | Pain confirmed, buying role known, next step booked |
| Opportunity | Active deal with a defined scope | Deal created with amount, close date and stage |
| Customer | Signed and billed | Closed-won deal linked to the company |
Opportunity stages and exit criteria
| Stage | Probability | Exit criteria (to move on) |
|---|---|---|
| 1. Discovery | 10% | Pain and impact written down; economic buyer named |
| 2. Solution fit | 25% | Demo done; decision criteria captured |
| 3. Proposal | 50% | Quote sent; decision process and timeline confirmed |
| 4. Negotiation | 75% | Champion confirmed; legal/procurement engaged |
| 5. Closed won / lost | 100% / 0% | Signed order form, or a loss reason picked from the list |
Key fields and validation rules
| Field | Type | Rule |
|---|---|---|
| Lifecycle stage | Picklist | Can only move forward, except an admin reset back to Lead |
| Lead source | Picklist | Required on create; no free text |
| Amount | Currency | Required from Proposal; must be > 0 |
| Close date | Date | Required; cannot be in the past on an open deal |
| Loss reason | Picklist | Required when stage = Closed lost |
| Economic buyer | Contact lookup | Required to enter Proposal |
HubSpot → Salesforce object and field mapping
| HubSpot | Salesforce | Note |
|---|---|---|
| Contact (lifecycle = Lead/MQL) | Lead | Before conversion, a HubSpot contact maps to a Salesforce Lead |
| Contact (SQL and later) | Contact | Converted Lead becomes Contact under an Account |
| Company | Account | Match on primary domain |
| Deal | Opportunity | Deal stage → Opportunity StageName via a lookup table |
| Deal amount | Opportunity.Amount | Same currency; no rounding |
| Lifecycle stage | Lead.Status / custom field | Salesforce has no single lifecycle field; a custom field keeps the history |
Sync design: source of truth per field
| Field | Source of truth | Rule |
|---|---|---|
| Email, name, title | CRM where the record was created | Enrichment fills blanks only; it never overwrites a value a person typed |
| Company size, industry | Enrichment tool | Refreshed monthly |
| Deal stage, amount | Salesforce | The rep's working system wins on conflict |
| Marketing consent | HubSpot | Always 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.Request. Written request with the problem, the owner, and which reports or automations it touches
- 2.Sandbox. Build the change in a sandbox or test portal first, never in production
- 3.Test. Test with sample records: create, edit, a validation rule failing, and the sync running both ways
- 4.Release note. A short note for users: what changed, why, and what they need to do differently
- 5.Rollback. Written undo steps and a field export taken before release, so the change can be reversed