Perfect sync between Zeliq and HubSpot
Identify and fix sync issues between Zeliq and HubSpot to keep your CRM data clean and up to date.
Your CRM is your source of truth. But when sync breaks down, problems pile up fast. Duplicates multiply. Critical leads slip through. You waste time cleaning up.
That's where Data Health comes in — your sync guardian that keeps HubSpot and Zeliq perfectly aligned. 🧼
Why Data Health is essential
For most sales teams, HubSpot is the foundation.
When Zeliq and HubSpot don't sync properly, chaos ensues:
Duplicate contacts and companies clutter your CRM
Critical leads fall through the cracks
Data integrity breaks after merges or deletions
We fixed that.
How to activate Data Health
Step 1: Connect HubSpot
Go to Integrations
Click Connect for HubSpot
Select your account and authorize the connection with Zeliq
⇒ Zeliq and HubSpot are now connected, but synchronization isn't active yet.
Step 2: Launch synchronization
Go to Integrations > HubSpot
Click Set-up synchronization
Configuration happens in 4 steps:
1. Sync type
Sync everything or only specific lists
List-based sync only updates enriched data in Zeliq, doesn't create new contacts in HubSpot
2. Push settings
Determine which entity types can be created in HubSpot
If disabled, sync will only update existing entities in HubSpot
3. Mapping ⚡
The most important step
Connect fields between Zeliq and HubSpot
Choose the directionality for each field
4. Exclusion rules
Filter out elements you don't want synced from HubSpot to Zeliq
Currently, no exclusion rules from Zeliq to HubSpot
⇒ Once complete, synchronization starts. It'll be operational in a few minutes.
Automatic after activation
Once your HubSpot integration is connected and sync is active, Data Health runs automatically in the background. It monitors all new contacts and companies, flagging issues in real time.
How Data Health works
Data Health acts as your sync control center. Every time you create a contact or company in Zeliq or HubSpot, our matching engine checks for similar existing records.
Our engine analyzes:
Companies: Name, LinkedIn URL, Domain
Contacts: Name/firstname/company combination, LinkedIn URL, email, phone number
No match? → We sync the entity seamlessly
Match detected? → We flag it in Data Health so you can decide
Smart, simple, efficient.
The 4 types of errors detected
This version focuses on duplicate prevention.
Error type | What it means | Example |
Single match | One possible duplicate found | You create "ACME Corp" in Zeliq, but a similar company already exists in HubSpot |
Multiple matches | Several possible duplicates found | Same scenario, but multiple similar companies exist |
Company not synced | Contact blocked because parent company has sync issues | A contact can't sync until its company's issue is resolved |
Conflicting issue | Matching entities have errors in both directions | We prioritize HubSpot → Zeliq errors and flag the conflict |
💡 Automatic redirects
Click on "Company not synced" → redirects to the parent company's error
Click on "Conflicting issue" → redirects to the HubSpot → Zeliq error (we prioritize CRM data)
The 3 ways to resolve errors
Each flagged issue offers three resolution options:
Action | When to use it | What happens |
🔗 Connect | The match is the same entity, just not linked yet | Links both records so they sync together. Automatically handles existing connections |
✳️ Create anyway | The match isn't relevant (different person, subsidiary, etc.) | Creates a new record in HubSpot. Use with caution to avoid real duplicates |
🗑️ Archive/Cancel | The entity is a duplicate or no longer needed | Archives Zeliq records or permanently cancels HubSpot creation |
💡 Recommendations
Connect: use this option when none of the matches are already synced between Zeliq and HubSpot
Archive/Cancel: recommended when at least one match is already synced to avoid duplicates
Tip: Some actions trigger follow-up flows to keep your systems aligned and prevent data loss.
Resolution order: who goes first?
Our priority system ensures clean resolutions:
1. Resolve company issues before contact issues
Contacts depend on their parent company
Resolving the company often automatically unblocks contacts
2. Handle HubSpot → Zeliq errors before Zeliq → HubSpot errors
We prioritize CRM data
Avoids discrepancies between resolutions
Follow the indicated order → one resolution often fixes multiple issues at once.
Post-resolution: what happens next?
In some cases, a second step appears after the resolution to prevent your resolution from creating new problems.
Case 1: After a connection (Zeliq → HubSpot errors only)
If your connection removes an existing connection, we offer to archive the entity in Zeliq that lost its connection.
Example:
Company ACME1 is connected between HubSpot and Zeliq
Company ACME2 was created in Zeliq and identified as a duplicate
You connect ACME2 (Zeliq) with ACME1 (HubSpot)
→ ACME1 in Zeliq is no longer connected to anything. You can then:
Archive this company
Archive associated contacts (otherwise they'll be automatically transferred to the newly connected company)
Benefit: Avoid keeping unsynced entities in Zeliq.
Case 2: After archiving/creation was cancelled
For a company with associated contacts, you can choose:
Apply the same resolution to contacts as to the company
Transfer contacts to an already synced company (if available)
Note: If no match is synced, the transfer option won't be offered to avoid conflicts. Contacts will automatically get the same resolution as the company.
Benefit: Delete a duplicate company while keeping relevant contacts.
Handle multiple errors at once
Some errors are eligible for bulk treatment to quickly clean your CRM.
Bulk-eligible errors:
"Single match": all resolutions available
"Multiple matches": only forced creation and archiving available (connection requires manual choice among matches)
Non-bulk-eligible errors:
"Company not synced" (redirect)
"Conflicting issue" (redirect)
💡 Tip: Handle bulk-eligible errors first. Redirects will transform into bulk-treatable errors. Use the filter to easily identify bulk errors.
The 3 bulk actions available
1. Auto-fix (only for "single match")
Automatically connects all leads with their single match. You can choose:
Connect only matches that aren't already synced (recommended to avoid breaking existing connections)
Connect all entities, even if the match is already synced
Option to automatically archive Zeliq leads that would lose their connection
2. Creation
Creates all selected entities in the target platform:
HubSpot → Zeliq errors: creation in Zeliq
Zeliq → HubSpot errors: creation in HubSpot
You can select errors from different directions, all will be processed.
⚠️ Caution: risk of creating duplicates
3. Archive / Cancel creation
HubSpot → Zeliq errors: creation cancelled
Zeliq → HubSpot errors: archiving in Zeliq
The number of leads per direction is shown in the confirmation modal.
Note: If companies are part of this resolution, associated contacts will automatically get the same resolution.
What's not covered yet?
This version only handles creation-related sync issues.
Coming in future updates:
Modified/merged entities (HubSpot merges that break connections)
Invalid data errors (wrong formats, missing required fields)
Rate limits and system delays
We're building a complete sync solution, step by step!
👩🏼💻 For further information, please do not hesitate to contact us: