Run outbound here, keep HubSpot as the record
Most teams should not migrate their CRM to change how they run outbound. Sync instead.
Sync
Contacts and activity
Direction
Two-way
Seats
Unlimited in Autocloz
Migration
Not required
What it does
Contacts sync between the two systems and outbound activity — sends, calls, replies, opt-outs — writes back to the HubSpot timeline, so reporting and attribution stay where your team already reads them.
The common reason to do this is cost shape: HubSpot bills on paid Sales Hub seats, and outbound headcount is usually what grows fastest. Execution moves to a system with up to 5 users while the record stays put.
Setting it up
- Connect your HubSpot account in Autocloz.
- Choose which contact properties map in each direction, and which system wins on conflict.
- Decide what activity writes back — most teams sync sends, replies and opt-outs, but not every automated touch.
- Run a small segment first and confirm the timeline looks right in HubSpot.
- Expand once the mapping is proven.
Limits worth knowing
- HubSpot API rate limits apply and vary by subscription tier.
- Custom objects and some property types need manual mapping.
- Suppression is authoritative in Autocloz for outbound; make sure a HubSpot unsubscribe also flows back.
- Two-way sync always needs a conflict rule. Decide it deliberately rather than accepting a default.
Common questions
Do we have to leave HubSpot?
No, and most teams should not. Keep it for reporting and marketing, and run outbound execution in Autocloz.
Will opt-outs sync both ways?
Yes, and this is the setting to verify first. An unsubscribe recorded in HubSpot should suppress in Autocloz and vice versa.
Does this need a paid HubSpot tier?
The free CRM supports contact sync. API limits are more generous on paid tiers.
Connect HubSpot in a few minutes
Free forever, up to 5 users, no card.