Google Sheets + Notion → HubSpot
Your Series A team has been running the sales pipeline out of Google Sheets while Notion holds the customer context: account summaries, champion notes, decision criteria, objections, and meeting history. It worked at 200 leads — it doesn't at 800. Watch the agent treat this like a real CRM migration: profile the sheet as the deal-stage source of truth, profile Notion as the customer-intelligence source, map both into HubSpot CRM objects, create the right associations between companies, contacts, deals, and notes, stage a sandbox load, reconcile pipeline totals to the dollar, and ship a go-live checklist your VP Sales can sign off on.
What this does
The agent picks up a migration brief from the Head of Sales: Google Sheets owns where each opportunity is in the pipeline, while Notion owns what we know about each customer. Both need to become one usable HubSpot CRM before the board meeting.
It profiles both sources without modifying them — 612 pipeline rows in Sheets, 428 customer-context pages in Notion, 287 accounts that appear in both systems, and 41 deals where the sheet stage conflicts with a stale or ambiguous Notion note. The sheet wins for dealstage, pipeline, amount, and closedate; Notion wins for notes, pain points, champion details, and decision criteria.
Then it creates HubSpot companies, contacts, deals, note activities, custom properties, and associations between them. The sandbox load reconciles pipeline value to the dollar before the go-live plan is sent for approval.
How it works
Four connectors run in sequence.
- Google Sheets supplies the pipeline tracker — 612 rows with company, contact, amount, close date, owner, and stage.
- Notion supplies customer context — 428 account pages with notes, champions, pain points, decision criteria, objections, and meeting history.
- HubSpot receives standard CRM objects: contacts, companies, deals, notes, custom properties, and associations between records.
- Slack closes the loop with
#sales-opsand flags the 41 account-stage mismatches that need VP Sales review.
Same shape a RevOps lead would use on a first CRM migration: separate pipeline truth from customer context, map each source to the correct HubSpot object and property, create associations explicitly, load to sandbox, gate on reconciliation, then go live with a checklist — not a big-bang import.
Outcomes you can verify
12 evidence artifacts attached to the go-live plan: Sheets pipeline profile, Notion customer-context profile, overlap analysis, HubSpot object schema preview, field mapping, association plan, deal-load preview, dedup log, review queue, sandbox load report, reconciliation summary, and rollback plan.
753 unique contacts staged. 412 companies. 318 open deals. 312 Notion notes attached as HubSpot note activities. 1,483 associations created between contacts, companies, deals, and notes. Pipeline total before: $4.18M. Pipeline total after: $4.18M.
Nothing hits production HubSpot until the VP Sales signs off on the 41 account-stage mismatches and the reconciliation gate passes.