You've always been able to use Insycle to deduplicate records at scale, but when you already know which records are duplicates, creating matching rules to find them again is unnecessary work. Now you can skip that step entirely.
A new CSV tab in Step 1 of the Merge Duplicates module allows you to upload a list of known duplicate pairs and merge them directly, with full control over which field values are retained. It works for any supported CRM, including HubSpot and Salesforce.
For example, if your team has found a set of duplicate account records through an external audit or data export, you can format those records as ID pairs in a CSV file and upload them directly into Merge Duplicates—without needing matching rules or custom CRM fields.
Learn more: Customize How Duplicates Are Merged Using a CSV
When you're deduplicating at scale, it's not uncommon to find records that look like duplicates but aren't, or groups where most records match but one is clearly different. Until now, these groups kept reappearing in your results each time you ran a template, and the only solution was to create a custom field and manually log each record you wanted to skip.
You can now exclude any duplicate group directly in the Merge Duplicates module. This lets you prevent specific sets of records from appearing in duplicate analysis or being merged.
In Step 2, click the X on a group row to add it to the Exclusion List — it won't appear in duplicate analysis or be included in merges, regardless of which template or matching rules you use.
To review or undo exclusions, click the Exclusions button in the Step 2 header to open a list of all excluded groups, where you can inspect individual records or remove groups from the list at any time.
For example, if you're reviewing a batch of contact duplicates and notice one group contains records that belong to separate individuals who share a name, you can exclude that group on the spot. It will no longer surface in future runs, keeping your results clean without requiring manual field tracking.
Learn more about excluding duplicate groups from deduplication.
When using the Associate app to link parent and child companies in HubSpot — or parent and child accounts in Salesforce — the Copy Direction and Copy Rule labels in Step 3 now accurately reflect the actual parent-child relationship instead of showing a generic same-object label.
Previously, both options in the Copy Direction dropdown showed "Companies to Companies" (or "Accounts to Accounts" in Salesforce), making it hard to tell which way a value would actually flow. Now, the labels clearly display the direction explicitly — for example, "Child Company to Parent Company" — and the Copy Rule options update accordingly, so it's clear which record's field condition applies.
For example, to copy the Company owner from a child company to its parent only when the parent's field is empty, you can now select "Child Company to Parent Company" as the Copy Direction and "Only when Parent Company Field is empty" as the Copy Rule — no guesswork required.
There is no change to how the feature works; only the labels have been updated.
Learn more about creating parent-child relationships and copying values.
Knowing exactly where to look in Insycle takes time — especially when you're trying to track down a specific template, navigate to a setting, or pull up a help article mid-task.
Search is now the first item in Insycle's left navigation menu, putting universal search front and center wherever you are in the app. From a single search bar, you can find templates and Recipes, help center articles, and quick links to key areas like billing or AI settings — all at once, without navigating away from your current task.
For example, if you need to tackle erroneous phone number formatting, click Search and type "phone" into the field. Results will surface relevant templates (such as "Standardize USA/CAN phone numbers"), matching help center articles (such as "Format Phone Numbers for Country Codes"), and any saved templates your team has built around phone data — giving you a clear path forward in seconds.
When using the Merge Duplicates module to merge HubSpot companies, Insycle now gives you full control over which parent company value is retained on the master record, while automatically preserving parent company labels.
Previously, if a duplicate company had a parent company and the master did not, the parent company was carried over, but the parent label was sometimes missing after the merge. Insycle now automatically applies the parent label when merging companies where the duplicate has a parent and the master does not.
Additionally, you can now explicitly control which parent company value is kept during the merge. In Step 4 on the Fields tab, select Parent Company and choose the value you want to retain—including For master record (even empty) if you want to keep the master record's value as-is (even when it's blank). If you don't configure this field and the master record has no parent company, Insycle will automatically keep the parent company from the most recently modified duplicate record that has one.
For example, if you're merging subsidiary companies where some duplicates are correctly associated with a parent corporation, and others aren't, you can configure the Parent Company field to always retain the value from the record with the most recent activity, ensuring the correct corporate hierarchy is preserved after deduplication.
Learn more about defining what field data gets saved when merging HubSpot duplicates in Insycle.
In Insycle's Merge Duplicates module, you can now use additional Match Parts options under Step 1: Find Duplicates to identify duplicates with greater precision.
Extended Character Range: The First and Last Match Parts options now support matching 3–12 characters, giving you more flexible control when identifying duplicates based on partial field values.
New Word-Based Matching: You can now match on the First word or Last word in a field, making it easier to find duplicates when key identifying information appears at the beginning or end of field values.
These enhancements are particularly valuable when merging duplicates based on phone numbers. Phone numbers often contain exactly 10 digits, and duplicates may differ by just a single character—such as when one record includes a country code, and another does not.
For example, if you have contact records with phone numbers formatted as "+1 (555) 123-4567" and "(555) 123-4567," you can now use the Last 10 Characters Match Parts option to match on the core 10-digit phone number, ignoring the country code prefix. Use this in combination with the Ignored Symbols and Ignored Whitespace options to identify true duplicates even when formatting varies across records.
Learn more about using Match Parts options to find duplicates.
To make Insycle easier to understand, we've renamed the field setting control from "Sync" to "Included" in the Settings > Fields interface. This change primarily affects our HubSpot users.
This change clarifies the distinction between two important concepts:
The functionality remains exactly the same—only the terminology has changed to eliminate confusion.
For example, if you want to add the "Contact Priority" field to your Insycle dataset, navigate to Settings > Fields and toggle the "Included" control to the 'On' position (yellow). This field will then be available for filtering, duplicate matching, standardizing, and other operations in Insycle after the overnight data sync completes.
Learn more about managing which HubSpot fields are included in your Insycle dataset.
We've improved the Field data condition handling in Step 4 of the Merge Duplicates module to provide you with more flexible control over which field values are kept during merging.
The "Is" and "Is not" conditions now support OR logic using pipe-separated values (|). This lets you create a single condition that checks multiple values at once.
For example, if you want to retain the Country field when it contains either "United States" or "Canada," you can now use a single condition: Country is United States|Canada instead of creating two separate rules.
For picklist fields, we've added two new conditions—"any of" and "not any of"—that allow you to select multiple options from a dropdown menu without needing pipe separators.
For example, if you want to keep the Lead Status field when it's set to "New," "In Progress," or "Connected," you can select all three options at once using the "any of" condition instead of creating separate rules or using pipe separators.
Learn more about using conditions in Step 4 of the Merge Duplicates module.
In Insycle's Associate app under Step 2, you can already use the object filter to limit the number of target records Insycle searches for matches on the Simple and Advanced tabs.
Now, you can also apply filters to narrow down target HubSpot records on the Related and Existing tabs. This helps ensure that you create associations only between records that meet specific field-value criteria.
Related tab: The Related tab in Step 2 leverages existing associations to fill in missing ones. For example, when a new order comes in, you want it associated with the relevant company. Since you automatically link orders to contacts, you can use the Related tab to connect orders to companies through existing contact-to-company relationships.
Now, you can filter to associate only companies that meet specific conditions—such as those that have a Parent Company value (only select subsidiaries) or a Type value of "Customer." If multiple companies meet your filter criteria, all qualifying records will be associated with the source order.

Existing tab: The Existing tab of Step 2 lets you add or remove association labels between records that are already related in HubSpot. For example, you have course objects related to contacts and want to add an "Enrolled-Win26" label to currently unlabeled associations.
To ensure you label only relationships for the winter term, you can filter to show only courses with "Winter 2026" in the Term field.
Learn more about using the Filter when managing HubSpot associations and labels.
In Insycle's Associate App, you can now add a Condition to your matching rules in Step 2, giving you more precise control over which records to create relationships with.
Previously, preventing associations where certain field values didn't match between records required separate cleanup steps. Now, you can specify conditions directly within your association setup to ensure relationships are only created when all criteria are met.
For example, when removing existing associations between contacts and companies, you can add a condition to only remove relationships where the contact's Country/Region doesn't match the company's Country/Region. This helps you clean up incorrect relationships while preserving valid ones—all in a single operation.
This enhancement works alongside your existing matching fields, giving you more detailed control over association logic and helping prevent "Failed. Multiple target matches" errors by restricting potential matches to only those that satisfy all your specified conditions.
Learn more about configuring these Conditions in the Associate App.