Question 1

How are companies matched between the two systems?

Accepted Answer

On domain, which is convenient because both sides already think that way. Plain accepts either its own company identifier or the domain name as the upsert key, and HubSpot companies are typically keyed on domain too, so a mapping can be built without first storing Plain identifiers anywhere. Customers are matched separately, by email address or by an external identifier that can carry the HubSpot record identifier if you prefer explicit keys.

Question 2

Which Plain objects can be written to?

Accepted Answer

Only customers, companies and tenants. Customers take an external identifier, name, email and email verification status. Companies take name, domain, contract value, account owner and tier. Tenants take name, external identifier, URL, tier and custom field values, and new tenant custom fields can be provisioned as part of the sync. Threads, messages, notes, users, tiers and label types are read only, so anything conversational flows out of Plain rather than into it.

Question 3

What can be pulled out of Plain into HubSpot?

Accepted Answer

Considerably more than can be written back. The readable catalogue covers customers, companies, tenants, threads, users, tiers and label types, plus messages, notes, attachments, message components, thread links, timeline events and discussions, plus seven prebuilt reports including daily thread counts and SLA compliance by label. Most teams pick a small slice of that, typically open thread counts or last contact date, and use reverse ETL to keep it on the CRM record.

Question 4

How current is the data?

Accepted Answer

As current as your schedule, since reads are incremental rather than full. Threads, customers, companies and tenants are read against Plain's updated timestamp, and each run picks up changes since the previous one, with a deliberate ten minute overlap so nothing is lost around a boundary. That makes a frequent schedule inexpensive. The overlap does mean a record can arrive twice, so the destination should merge on a key rather than append.

Connect Plain with HubSpot

Connect Plain and HubSpot with Polytomic

Domain is the natural key

Company profile into Plain

Support signals back out

Trusted by businesses worldwide

Step-by-step integration guide

Connect Plain in Polytomic

Connect HubSpot in Polytomic

Create a sync between Plain and HubSpot

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Plain with HubSpot?