Match email domain to company domain, company name to account name, custom ID to custom ID, or postal code to a service-area field.
Associate CRM records in bulk, contacts to companies, leads to accounts, hierarchies and all.
Find the relationships your CRM missed and create them at scale: match on any fields with fuzzy logic and smart ignores, match Salesforce leads to their accounts, build parent-child hierarchies, and copy key data across the link, previewed first, then automated so the graph stays complete.
Contacts without a company
1,246 records
Source
Email Domain
Target
Company Domain
maya@acme.co.uk
Contact · no company
Acme Software
acme.com · target
noah@northstar.io
Contact · no company
Northstar Labs
northstar.com · target
Find the missing link. Resolve ambiguity by policy. Preview every relationship before it exists.
Insycle turns bulk association into a controlled sequence: filter to unlinked records, match source and target fields with exact or fuzzy logic, apply selection rules when several targets qualify, preview every proposed link and copied value, then update and automate with alerts for anything left unmatched.
The record exists. The account context does not.
Deals with no company make account-level revenue reporting impossible. Contacts with no company blind ABM and leave reps without context. Unmatched Salesforce leads get cold-worked while the account they belong to is already a customer. A flat company list hides the enterprise hierarchy your team actually sells into.
From backlog to standing process
Native auto-association catches the easy case, an exact email-domain match at creation time. Associate works the backlog and keeps it worked: filter to the orphans, match them with logic that survives real-world identifiers, link them in bulk, then schedule the template and alert a teammate whenever a record cannot be placed.
Matching built for how identifiers actually look.
The same configurable matching DNA that powers Merge Duplicates is pointed at linking instead of merging. Compare any source field with any target field, then account for the noise that makes real CRM data difficult.
Use Exact for identifiers. Similar catches one-character drift, Acme finds Akme. Review Similar results before trusting them at scale; IDs are Exact-only.
Match through subdomains, TLDs, URL paths, symbols, digits, whitespace, and editable common terms such as Inc., LLC, and HQ.
Compare first words or last characters, or treat every value in a semicolon-separated field as a valid match.
In Advanced mode, evaluate one source field against several target fields, for example, Email Domain against Company Domain and Additional Domains.
Contact → Company
Email Domain
Source field
Company Domain
Target field
Exact
Comparison
Subdomain + TLD
Ignored
Company name
Second criterion
Similar
Ignore common terms
Multiple criteria combine as AND, not fallback. For domain first and company name second, save separate templates and chain them in a Recipe.
The links your CRM will not make for you.
Lead-to-account matching
Match leads to existing accounts using domains, names, ignored common terms, and Similar Match. Salesforce has no native lead-to-account matching; Insycle adds preview, audit, and automation inside the same data-quality platform.
It is also the prerequisite for bulk lead conversion: match here, then convert at scale in Bulk Operations.
Bulk convert leads to contactsBuild account hierarchies in bulk
Detect and create parent-child company relationships at scale, turning a flat list into the account structure your enterprise motion needs. Same-type links also support contact-to-contact colleague and referral relationships.
Replace record-by-record Parent field maintenance with a reusable matching policy.
Create parent-child relationshipsManage association labels at scale
Use the Existing tab to add, remove, or replace labels across records that are already associated, categorize decision-makers, billing contacts, and partners, or remove relationships that should not exist.
The Related tab can also infer a missing link from existing relationships, all within the same governed workflow.
Manage HubSpot association labelsAmbiguity handled, not failed.
Finding a possible relationship is only the beginning. Scope both sides of the link and decide what should happen when the answer is not obvious.
Target filters
Constrain which records can be matched to: only companies with a name, only accounts in the right region, or any other target-side condition.
Selection rules
When several targets qualify, choose deliberately, most recently created, has an owner, or another ordered rule. Ambiguity resolves by policy.
Create when no match exists
For contacts → companies, create the missing company and name it from selected fields. Pair this with careful matching, or it can create duplicates.
Supported direction, stated plainly
Contacts → companies is the fully supported standard direction. Configure the template around that direction instead of discovering the constraint during a trial.
The link carries data, not just structure.
As records are associated, copy values across the relationship in either direction. Fill a company’s industry from its contacts, or stamp the account tier down onto every linked contact.
Choose whether to copy only when the target is empty, only when the source has a value, or always. The preview CSV shows every proposed copy and its before value.
Copy values between associated recordsIndustry
Contact field
Industry
Company field
Only when source has a value
Copy rule
Only when target is empty
Write rule
New orphans, caught weekly, and flagged when they cannot be placed.
Check Count unmatched records as Failed, automate the template, and the run report’s subject line tells you when something could not be linked. The record that needs a human lands in your inbox instead of silently accumulating.
Run templates on a schedule, chain fallback passes in a Recipe, or trigger them from a HubSpot Workflow.
Most teams associate records in an annual cleanup. This turns it into a weekly sweep with an exception report.
New or orphaned record
Forms · imports · integrations
Saved Associate template
Schedule · Recipe · Workflow trigger
Matched, or flagged
Association created · exception emailed
Every link, on paper first.
Preview mode lists each result, the source and target records that would be linked, the fields that matched them, and every Step 3 copy with its before value. Start with a chunk, verify the relationships in the CRM, then scale.
Every preview and update lands in the Activity Tracker, with the Run ID cross-referenced on affected records. Failed rows can route to Grid Edit for investigation.
Evaluated
1,246
Ready to link
1,108
Unmatched
138
| Result | Source | Target | Matched on |
|---|---|---|---|
| Ready | Contact 98142 | Company 2046 | Domain |
| Ready | Lead 73608 | Account 1189 | Name |
| Failed | Contact 98211 | , | No match |
Retroactive matching, governed at scale.
| Capability | Native auto-association | Spreadsheet + import | Insycle Associate |
|---|---|---|---|
| When it works | Exact domain match at creation | Whenever someone does the project | Any time, any field pair, retroactively and on schedule |
| Matching | One built-in method | VLOOKUP exactness | Exact + Similar, ignores, match parts, multi-field, multi-value |
| Leads ↔ accounts | No native Salesforce matching | The SDR’s guess | Domains, names, ignores, and Similar Match |
| Deals ↔ companies | Manual or easy native inference | Painful | Matched directly or inferred, with policy, preview, and audit |
| Hierarchies | Parent field set by hand | By hand in a sheet | Detected and created in bulk |
| Ambiguous matches | , | Human review | Selection rules resolve by policy |
| No match found | Orphan persists | Orphan persists | Create the company or flag Failed to an inbox |
| Labels | One HubSpot record at a time | Not possible | Add, remove, or replace at scale in HubSpot |
| Dry run | No | The sheet was the dry run | Preview CSV with result, both records, match fields, and copies |
| Recurrence | Creation-time only | Next year’s project | Schedules, Recipes, Workflow triggers, and failure alerts |
One engine, every association backlog.
Reporting works when the relationships are complete.
Use an approved customer quote about restoring account-level reporting, giving reps complete context, or eliminating a recurring association project. Keep the proof in the task register.
Approved Associate customer proof
Complete-account outcome, company, role, and source
Server-rendered G2 proof
Rating, review count, and source link
What happens when the relationship is not obvious?
Does Salesforce have native lead-to-account matching?
No. Salesforce does not natively match leads to the accounts they belong to. Insycle compares lead fields such as email domain or company name with account fields, previews the proposed relationships, and can run the saved policy continuously.
Can I associate records that do not share an exact domain?
Yes. Associate supports Similar Match, ignored subdomains and TLDs, common-term removal, partial-field matching, and multi-field or semicolon-separated values. Review Similar results carefully before automating them at scale.
What happens when multiple companies match one contact?
Selection rules choose among eligible targets using ordered criteria such as most recently created or has an owner. You can also tighten the target filters. Multiple matching criteria combine as AND; fallback passes should be separate templates chained in a Recipe.
Can Insycle create a company when no match exists?
Yes, for the standard contacts-to-companies direction. Insycle can create the missing company and name it from selected contact fields. Use careful matching first because creating when no match is found can otherwise mint duplicates.
Can I be notified when a record cannot be associated?
Yes. Enable Count unmatched records as Failed and automate the template. The Activity Tracker report and its email subject will show when unmatched records need human review.
Connect your CRM and preview your first thousand associations in minutes.
See every proposed source, target, match field, and copied value before creating a relationship.
From complete fields to complete context
A complete record is more than correct fields, it is correct relationships.
An agent reasoning about an account can only see the records linked to it. See how teams keep the whole account picture governed, links included.
See the complete Data Integrity systemRelated capabilities and training
Watch how associations and hierarchies are built in bulk.
Explore Webinar: Lead-to-account matching in SalesforceWatch the lead-to-account matching walkthrough.
Explore Salesforce AssociationsLink leads, contacts, and accounts and build hierarchies in bulk.
Explore
HubSpot
Salesforce
Pipedrive
Intercom
Mailchimp