What the ConnectWise + HubSpot integration creates, updates and removes

Last updated: November 11, 2026

This article lists, object by object and in each direction, what the ConnectWise + HubSpot integration does to your records: whether it creates them, updates them, changes their associations, or removes anything. Use it with your Sync Logs when you're checking what the integration did, and with What the ConnectWise + HubSpot integration doesn't sync for the things it leaves alone.

The short version

  • The integration creates and updates records. It never deletes a company, contact, deal, opportunity, product or activity in either system.

  • Nothing is deleted in ConnectWise. Your ConnectWise API member doesn't need delete permission. The one removal the integration makes in ConnectWise is a company's Type tags, which it keeps in line with the mapped HubSpot value.

  • In HubSpot, the only removals are associations. A line item is taken off its deal when its ConnectWise forecast item is deleted, and a deal's or engagement's association moves when its company or contact changes in ConnectWise. The records themselves stay in HubSpot.

Each direction runs only when it's turned on for that object in SmartHub, and only for records that pass your filters and inclusion lists.

Object by object

Object

Direction

Creates

Updates

Removes

Companies

HubSpot → ConnectWise

Yes

Yes

Company Type tags that are no longer in the mapped value

Companies

ConnectWise → HubSpot

Yes

Yes

Nothing

Contacts

HubSpot → ConnectWise

Yes

Yes

Nothing

Contacts

ConnectWise → HubSpot

Yes, except contacts permanently deleted in HubSpot for privacy (GDPR) reasons, which are never re-created

Yes

Nothing

Deals and opportunities

HubSpot → ConnectWise

Yes

Yes

Nothing

Deals and opportunities

ConnectWise → HubSpot

Yes

Yes

Moves the deal's company or contact association when it changes on the opportunity

Line items and forecast items

HubSpot → ConnectWise

Yes

Yes

Nothing. Removing a line item from a HubSpot deal leaves the forecast item in ConnectWise.

Line items and forecast items

ConnectWise → HubSpot

Yes

Yes

Takes the line item off its deal when its forecast item is deleted in ConnectWise, or when a forecast item's one-time price and cost are cleared. The line item itself stays in HubSpot.

Products

ConnectWise → HubSpot only

Yes

Yes

Nothing

Engagements and activities

HubSpot → ConnectWise

Yes

Yes

Nothing

Engagements and activities

ConnectWise → HubSpot

Yes

Yes

Moves the engagement's company, contact or deal association when it changes in ConnectWise

Notes

HubSpot → ConnectWise only

Yes

Yes

Nothing. Notes written in ConnectWise don't sync to HubSpot.

Reading "Deleted" and "Skipped" in your Sync Logs

Deleted appears on line items only. It means a forecast item was deleted in ConnectWise, usually because someone removed a product from an opportunity, and the integration took the matching line item off the HubSpot deal. These rows are labeled HS Line Item => CW Forecast, but nothing was deleted in ConnectWise; the deletion happened there first, and the integration mirrored it in HubSpot. To confirm one, open the opportunity's forecast in ConnectWise: the item won't be there.

Skipped with a reason such as HubSpot record was deleted or ConnectWise record deleted means the record's linked partner in the other system no longer exists, so there was nothing to update. Clean these up with the archive approach in How Do I Manage Record Deletion Between Systems.

Deleted records and orphans

Because the integration doesn't delete companies, contacts, deals or opportunities, deleting one of them in either system leaves its partner in the other system. Over time these orphaned records build up. Flag records with an archive property instead of deleting them directly; How Do I Manage Record Deletion Between Systems walks through the setup.

Need something that isn't listed here?

If your team needs the integration to handle something it doesn't, or you think you've found a gap, contact our support team. Feature requests help us decide what to build next.