What these systems normally control
Requirements for assessment; confirm supported actions before relying on this workflow.
Contacts, companies, deals, pipelines, activities, tasks, and — depending on the product — email campaigns and reporting.
Customer Relationship Management
Keep sales context with the customer’s next handoff.
Provider options and connection limits
Providers to assess for customer relationship management
HubSpotNeeds assessment
SalesforceNeeds assessment
Zoho CRMNeeds assessment
PipedriveNeeds assessment
Check the actual connection before changing your process.
On Pro, the QuickBooks Online connection imports customers and invoices from your own company and does not write back. It still needs checking with your company. Other provider names and the information flows below describe requirements to assess, not ready-to-use connections. Confirm the provider, plan, permissions, direction and any setup cost before work begins.
Why the specialized system usually stays
Requirements for assessment; confirm supported actions before relying on this workflow.
For teams already living in a CRM with configured pipelines and reports, replacement is disruptive. The Forge can consume the CRM's customer and pipeline state so operations, communication, and billing work off the same record — or, for teams whose CRM has become an over-priced contact list, The Forge can absorb the CRM's function entirely.
Information to review for import
Requirements for assessment; confirm supported actions before relying on this workflow.
- Contacts and companies with source attribution
- Deals and pipeline stage
- Activities and notes
- Owner assignments
- Custom fields where mapped
Information to review for export
Requirements for assessment; confirm supported actions before relying on this workflow.
- Won-deal handoffs to operations
- Communication events (calls, SMS, email) attached to the contact
- Job / project status back to the deal
- Revenue back to the deal for attribution
Events to consider during setup
Requirements for assessment; confirm supported actions before relying on this workflow.
- Deal won
- Deal stage changed
- New contact received from an intake source
- Owner reassigned
- Activity logged
Manual work the proposed connection may reduce
Requirements for assessment; confirm supported actions before relying on this workflow.
- Copying won deals into a scheduling or job system
- Sending updates to the CRM after operations finishes
- Duplicating contact records across sales, operations, and billing
- Maintaining separate follow-up lists
Whose work improves
Requirements for assessment; confirm supported actions before relying on this workflow.
- Sales and marketing leader
- Owner / executive
- Operations manager
- Office administrator
Reports that become possible
Requirements for assessment; confirm supported actions before relying on this workflow.
- Deals won by source, campaign, or referral
- Revenue delivered vs. deal amount won
- Time from deal-won to work-started
- Rep-level operational conversion
Access and permission notes
Requirements for assessment; confirm supported actions before relying on this workflow.
- Standard OAuth against the CRM.
- Read scope requested by default; write scope only where the customer opts in.
- Deleted contacts in the CRM are respected in The Forge.
Common category-wide limitations
Requirements for assessment; confirm supported actions before relying on this workflow.
- Complex CRM automations may not have direct equivalents in The Forge and remain in the CRM.
- Custom-field parity depends on mapping done during setup.
- Some CRM products throttle writes on lower plan tiers.
What might be replaced after review
Requirements for assessment; confirm supported actions before relying on this workflow.
The Forge can consolidate lightweight CRMs (contact list + basic pipeline) once the operation is stable. Sales-heavy CRMs with configured reporting usually remain.