Power user: managing multiple syncs across boards
TL;DR: You can run multiple syncs across different boards, HubSpot objects, and even multiple HubSpot accounts. Here's how to keep them organized without conflicts or wasted actions.
The scenario
You use HubSpot Integration Plus on more than one board — maybe Deals on a Sales board, Tickets on a Support board, and Tasks on a team board. Each board has its own sync configuration, and you may be working with different HubSpot objects or even different HubSpot portals.
When to use it
- Different object types on different boards — Deals on a Sales board, Contacts on a Marketing board, Tickets on a Support board, Tasks on a team board
- Different pipelines on different boards — your Sales Pipeline on one board, Partner Pipeline on another, using a Pipeline condition on each sync
- Different teams or departments — each team gets their own board with their own sync configuration
- Multiple HubSpot accounts — if your organization uses separate HubSpot portals (e.g., by region or business unit)
Before you start
- Have your boards created with the right columns before adding syncs — see Board Setup Best Practices
- Plan which HubSpot object goes to which board, and which board (if any) writes back to HubSpot
- Know your plan's monthly action quota — actions are shared across all syncs and reset on the 1st of every month. See Plans, Billing & Usage
How multiple syncs work
Each sync is independent. It has its own:
- HubSpot connection and object type
- Board and column mappings
- Sync direction and conditional triggers
- Action consumption
Each person can have one sync per board. To run several syncs, spread them across different boards, each with its own sync. To sync another object on the same board, a different user sets up their own sync. A subitem sync covers all subitems on the board.
Multiple HubSpot accounts: you can connect more than one HubSpot portal with Add another portal in the HubSpot 2-way Sync view on your board. Each sync connects to one portal, and syncs on different boards can use different portals. See Connect your HubSpot account .
Tips for managing multiple syncs
Keep syncs organized
One object per board
Clean separation. Best for large volumes — each board stays focused and filterable.
Multiple objects on one board
Each person can have one sync per board, so each extra object needs a different user to set up its sync. Use groups to separate object types.
One object, multiple boards
Different teams need different views of the same data. Each board can have different columns, groups, and conditional triggers.
- Name your boards clearly — "Sales Deals (HubSpot)", "Support Tickets (HubSpot)" — so it's obvious which boards are synced
- Document your setup — keep a note of which boards sync which objects, directions, and conditions. This saves troubleshooting time later
Avoid conflicts
- Don't sync the same HubSpot record to two boards with two-way sync — if both boards write back to HubSpot, conflicting updates can overwrite each other
- Use one-way sync for secondary boards — if your primary board is two-way, set additional boards to → (HubSpot → monday) only
- Use conditional triggers to partition — instead of syncing all Deals to two boards, use conditions to split (e.g., Board A = "Sales Pipeline", Board B = "Partner Pipeline")
Rule of thumb: Each HubSpot record should have at most one two-way sync connection. Additional boards should use one-way (incoming) sync.
Rule of thumb: Each HubSpot record should have at most one two-way sync connection. Additional boards should use one-way (incoming) sync.Watch your action usage
Every sync consumes actions from your shared plan quota. With multiple syncs running:
- Each changed field = 1 action per sync — if a Deal is synced to 2 boards, one changed field triggers 2 actions
- Monitor usage regularly — check your remaining quota in Plans, Billing & Usage
- Pause unused syncs — if a board isn't actively used, pause the sync to save actions. See Managing your sync
- Use conditional triggers — the more targeted your sync, the fewer actions consumed
Common gotchas
- Start small, expand gradually — get one sync working perfectly before adding more
- Review action usage monthly — multiple syncs can accumulate quickly
- Each sync's configuration is independent — changing the field mapping on one sync doesn't affect the others
- If your HubSpot connection expires, see Re-authenticate with HubSpot
Next up
Related
- Managing your sync
- Understanding Conditional Triggering
- Plans, Billing & Usage
- Understanding permissions
- Re-authenticate with HubSpot
Still stuck?