CRM Integrations Guide: HubSpot, Salesforce, ERP & Phone

CRM integrations connect your website, ads, phone, ERP, and support tools so sales works from one pipeline—not five spreadsheets. This Tekvers guide covers ownership rules, HubSpot/Salesforce checklists, AI receptionist write-back, and when to go custom.

Service: /services/crm-integrations. Deep dive: HubSpot/Salesforce blog · AI receptionist → CRM.

---

Integration Map (Start Here)

1. Inbound — forms, chat, ads, AI receptionist
2. System of record — HubSpot / Salesforce / custom CRM
3. Downstream — ERP, billing, fulfillment
4. Collaboration — Slack/email tasks and digests
5. Analytics — attribution that sales actually trusts

If you cannot draw this map, you are not ready for bi-directional sync.

---

Source-of-Truth Rules

Without ownership rules, bi-directional sync creates duplicates and “who changed this?” wars.

---

HubSpot & Salesforce Checklist

• Lifecycle stages agreed with sales leadership
• Required properties enforced at create/update
• Deduplicate by email/phone with clear merge policy
• Round-robin or territory assignment documented
• Activity logging from calls, forms, and chats
• Permission sets that prevent accidental mass edits
• Sandbox testing before prod field mapping changes

Field sprawl kills CRMs. Prefer fewer reliable properties over fifty neglected ones.

---

Website and Lead Capture

• Forms write structured payloads—not free-text only
• UTM persistence through redirect chains
• Spam protection without blocking real buyers
• Instant routing + SLA timers for hot leads
• Confirmation UX that sets expectations

Pair with business process automation so enrichment and notifications are reliable.

---

Phone + AI Receptionist

Wire voice outcomes into CRM activities and meetings:

• Contact create/update
• Deal/ticket notes from transcripts (summarized, reviewed)
• Appointment objects synced to calendar
• Missed-call callbacks as tasks

Guides: AI receptionist · voice AI for small business · service /services/ai-receptionist.

---

ERP and Billing Sync

Typical patterns:

• CRM wins until “closed won,” then ERP owns fulfillment
• Product catalogs sync one direction to avoid price fights
• Invoice status mirrors back for sales visibility
• Idempotent upserts with external IDs

Money-moving sync belongs on durable workers—not fragile one-off zaps. Tooling context: n8n vs Make vs Zapier · /services/business-process-automation.

---

Custom CRM / SFA

When industry workflows (field sales, distribution, manufacturing) do not fit SaaS CRMs, Tekvers builds custom CRM and Sales Force Automation experiences. Sometimes the right answer is HubSpot/Salesforce plus a custom portal—not a total rewrite.

---

Data Cleanup Before Integration

Integrations amplify dirt:

• Normalize phone/email formats
• Merge obvious duplicates
• Archive junk lifecycle stages
• Define required fields with sales—not IT alone
• Backfill carefully with dry runs

Skipping cleanup imports chaos at machine speed.

---

Security and Compliance

• Least-privilege API keys and OAuth apps
• Rotate credentials; store in a secret manager
• Audit logs for exports and bulk updates
• PII minimization in Slack notifications
• Vendor DPAs where required

AI layers that read CRM data need the same scrutiny as /services/ai-machine-learning projects.

---

Field Dictionary Example (Keep Short)

| Field | Owner | Source | Required | | --- | --- | --- | | email | Sales ops | Form / voice | Yes | | phone | Sales ops | Form / voice | Yes if phone-led | | utm_source | Marketing | Web | No | | lifecycle_stage | Sales | CRM rules | Yes | | next_step_date | Sales | Human / AI task | Yes for open deals | | last_call_summary | Phone/AI | Receptionist | No |

If your dictionary exceeds ~40 active fields, you likely have zombies. Archive them.

---

Deduping Policy Starter

1. Match on email first
2. Else match on normalized phone
3. If conflict (same email, different company), queue human merge
4. Never auto-merge accounts with open revenue above threshold
5. Log every merge for audit

Automation without merge policy creates two pipelines and zero trust.

---

Integration Test Pack

Before production mapping changes:

• Create contact from form fixture
• Update existing contact (no duplicate)
• Voice booking → activity + meeting
• Closed-won → ERP stub called once
• Failure path alerts fire

Run in sandbox. Screenshots in the PR/change ticket.

---

FAQ

HubSpot or Salesforce? HubSpot often faster for SMBs; Salesforce for complex enterprise hierarchies. Choose based on process complexity and admin skill—not ads.

Real-time or batch sync? Real-time for leads and bookings; batch for heavy catalog/ERP where eventual consistency is fine.

Custom CRM worth it? When SaaS forces painful workarounds daily. Otherwise extend HubSpot/Salesforce with a portal.

---

Attribution Sanity Checks

Marketing will ask “which campaign worked?” Integrations must preserve:

• First-touch and last-touch fields deliberately
• UTM survival across redirects
• Offline conversion uploads when ads platforms require them
• Clear definitions so sales and marketing argue less

Broken attribution creates budget fights. Fix the field dictionary before buying another analytics tool.

---

Additional Practical Notes

Teams researching this topic in 2026 usually underestimate two things: ongoing ownership after launch, and the cost of unclear requirements. Write success metrics before tools. Prefer thin vertical slices over sprawling rewrites. Use Tekvers as a sounding board when you need production judgment—architecture, security, integrations, and AI features with evals—not just another tutorial outline.

Document decisions in the repo. Review AI-assisted changes like junior PRs. Connect products to CRM, automation, and voice only after the core workflow is trustworthy. Measure outcomes monthly and kill work that does not move them. That operating rhythm beats chasing every new framework or model release.

---

---

Soft-Launch Integration Plan

1. Sandbox mapping review with sales + marketing
2. Replay 50 historical leads; verify fields
3. Enable form → CRM only for one week
4. Add voice/AI write-back second
5. Only then consider ERP bi-direction

Sequence prevents “everything syncs everywhere” outages. Document each stage’s go/no-go owner. Tekvers uses this ladder on /services/crm-integrations projects.

---

---

Field Notes From Tekvers Delivery

Clarity beats novelty. Write the outcome, constraints, and non-goals before choosing tools or models. Prefer thin slices with monitoring over big-bang launches. Review AI-assisted work like you would a junior engineer’s PR. Connect CRM, automation, and voice channels only after the core workflow is trustworthy. Keep a named owner for every production workflow and schedule a monthly metrics review. When deadlines matter more than learning curves, partner with an experienced team rather than stretching a tutorial into a customer promise. These habits travel across stacks and survive the next wave of frameworks.

---

Next Steps

1. Draw your systems map and name owners per field domain
2. Fix duplicates and required properties before new syncs
3. Prioritize inbound → CRM reliability over exotic bi-directional dreams
4. Add phone/AI write-back once core lead flow is trustworthy

Book a CRM/integration consult: Contact Tekvers.