Create a sync
Choosing the object type, mapping HubSpot properties onto entity columns, and putting the sync on a schedule.
A sync is created from HubSpot in the console with New sync. Creating, editing and running a sync is limited to owners and admins; other members can see syncs and review what they bring in.
Object type and entity
Choose the connection, then whether this sync reads contacts, companies or deals, then the entity its records live on.
One sync covers one object type. A portal where you want contacts and companies needs two syncs, usually onto two different entities.
Field mapping
Say which HubSpot property fills which entity column. The property list comes from your portal, so custom properties appear alongside the standard ones.
Values are converted to the column's type on the way in, and a value that cannot be converted — text in a number column, or an option that is not one of a select column's allowed values — fails that one object with an explanation rather than writing something wrong. Only mapped columns are ever touched, so anything your team maintains by hand in Auron is left alone.
Identifying column
Choose the column that identifies a record, and make sure it is mapped from a property that is genuinely unique — a company's domain, a deal's name if your team keeps those distinct.
This is how a sync decides between updating and creating. It is only consulted for objects Auron has not seen before; after that, a sync remembers which record belongs to which HubSpot object and goes straight to it.
Schedule
Name the sync and choose how often it runs: manual only, hourly, daily, or weekly.
Hourly suits a portal your team edits through the day. Daily is enough for most. Manual only is worth keeping while you are still settling the mapping.
Nothing runs until you activate it
A new sync is created as a draft, and drafts never run on a schedule whatever frequency they carry. Open the sync and choose Activate to put it on its schedule, Pause to take it off again.
You can also run it by hand at any time:
- Run sample reads the first handful of objects, ignoring where the sync had got to, so you can check the mapping produces what you expected. A sample deliberately does not move the sync's position, so the objects it looked at are still picked up by the next real run.
- Run now performs a full run: everything new or changed since last time.
Only one run happens at a time per sync.
The first run reads everything
A sync's first full run walks the entire object type, a few hundred objects at a time across as many runs as it takes. Once it reaches the end, every run after that asks HubSpot only for objects modified since the last run finished, which is why a large portal is cheap to keep current but takes a little while to load initially.
An hourly sync on a portal of fifty thousand companies therefore spends its first day or so backfilling, then settles into reading only the handful of companies that actually changed each hour.
Optional review before values land
By default a sync writes straight to entity records, because the mapping is a direct copy of what is in HubSpot with no interpretation involved — there is nothing for a reviewer to second-guess.
If you would rather see changes before they land, turn on Require approval in the sync's settings. Every pulled object then waits in the sync's Review tab, and nothing reaches a record until someone approves it. This is worth turning on for the first few runs of a sync onto an entity that already holds records your team maintains.
Changing a sync later
The name, mapping, schedule, approval requirement and status can all be edited. The connection, object type and entity cannot: those define what the sync is, and changing them would silently re-point existing records at different objects.
Editing the mapping affects future runs and does not revisit objects already synced. Deleting a sync stops it and removes it from the list; records it already wrote are kept, as is everything in HubSpot.
Where this is managed
Syncs are created and edited under HubSpot in the console. Entity types and their columns are configured under Entities and records. Writing the other way is covered in Push back to HubSpot.