What Objects Does the Integration Support?
Last updated: January 8, 2026
This article is your field guide to what SyncSmart syncs between HubSpot and ConnectWise—what moves, which way it travels, and the fine print that saves implementations from late-night debugging sessions.
At a high level: core CRM objects sync bi-directionally, product data flows with intent, and associations keep everything holding hands like a well-behaved data family.
Supported Objects Matrix
HubSpot Object | Direction | ConnectWise Object | Notes |
Companies | ⟷ | Companies | |
Contacts | ⟷ | Contacts | A company sync is required |
Deals | ⟷ | Opportunities | You do not need products/line items for opportunity syncing |
Products | → | Product Catalog | Products and Forecast Items go together — you can’t have one without the other |
Line Items | ⟷ | Forecast Items | |
Activities | ⟷ | Engagements | |
Default Associations | ⟷ | Default Associations | |
Parent–Child Associations | ⟷ | Parent–Child Associations |
Legend
⟷ = Bi-directional sync
→ = One-way sync (ConnectWise → HubSpot)
Key Notes and Dependencies
Contacts depend on Companies
Contacts don’t freelance. A Company record must exist (or sync) for Contacts to flow cleanly.
Deals ≠ Products (by default)
Opportunities can sync without Products or Line Items. This keeps pipelines moving even when pricing isn’t ready for prime time.
Products & Forecast Items are inseparable
Think of them as a double album. If you want Products, Forecast Items come with them. No solo careers here.
Associations are first-class citizens
Both default and parent–child associations sync bi-directionally, preserving record relationships across systems.