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:

• Included toggle – Controls which fields are part of your Insycle dataset
• Sync process – The overnight synchronization that keeps your data up-to-date between your CRM and Insycle

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.

OR Logic with Pipe-Separated Values

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.

New "Any Of" and "Not Any Of" Conditions for Picklist Fields

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.

Duplicates aren't always easy to identify—sometimes the same person has multiple records with matching names and phone numbers but different email addresses (e.g., a personal versus work email). Or you might have companies with the same domain and other indicators showing they're the same organizations, but with differences in other fields.

In Insycle's Merge Duplicates module, you can now create sophisticated templates that identify duplicates even when certain fields exist but don't match, helping you catch variants and edge cases.

The new Values Don't Match condition lets you set up multi-phase deduplication workflows that target different duplicate scenarios without overlap.

For example, after running a template to merge contacts with identical email addresses, you can run a second template to catch duplicates with matching first name, last name, and phone number - but different email addresses. By setting the Email field condition to Values Don't Match, you'll only surface duplicate groups where the email addresses exist, but differ, automatically excluding the exact-match duplicates you've already merged.

Or, if you've already merged companies with identical names, you can create a follow-up template to find duplicates with similar names (like "A.B.C. Corp" versus "ABC Corporation") and other matching information. Use the Values Don't Match condition on the company name field to find only duplicates with different company names, skipping the exact matches you've already taken care of.

Check out these articles in our Help Center for more details:

• Deduplication Scenarios: Advanced Techniques for Duplicate Management
• Module Overview: Merge Duplicates

Insycle's Salesforce integration now includes enhanced security during the authorization process with PKCE (Proof Key for Code Exchange) implementation in our OAuth flow.

PKCE provides additional protection against token interception attacks and ensures Insycle meets Salesforce's updated security standards. This security enhancement works automatically in the background—no action is required from you, and all existing integrations will continue to function normally.

This upgrade reflects our ongoing commitment to maintaining the highest security standards for your data integrations.

Learn more about getting started with Insycle for Salesforce.

When running operations in Update mode, Insycle now displays an estimated duration in the confirmation dialog before you execute the operation. This helps you plan your work and understand how long data processing will take.

The estimate is calculated based on the number of records being processed, the complexity of the operation, and typical throughput rates.

For example, if you're about to merge 900 duplicate contacts, the confirmation dialog might show you an estimated time of approximately 2 minutes, allowing you to decide whether to proceed immediately or schedule the operation for a more convenient time.

This feature is available in Merge Duplicates, Transform Data, Magical Import, Bulk Operations, Cleanse Data, Group & Update, Assign, and Associate modules.

Learn more about data update speeds and throughput in Insycle.

When comparing website URLs in Insycle's Merge Duplicates module and Associate app, you can now choose to ignore the URL path—the part that comes after the domain.

This new option lets you focus on matching just the domain while ignoring everything that follows. For example, when comparing nytimes.com/puzzles/spelling-bee and nytimes.com/crosswords/daily-puzzle, you can now match these as the same website by ignoring the paths /puzzles/spelling-bee and /crosswords/daily-puzzle.

In the Merge Duplicates module: Use the Ignored setting to exclude URL Paths when identifying duplicates. For example, if you have multiple records for the same company with different regional URLs, such as servicepublic.fr/france-33/bouches-du-rhone-13 and servicepublic.fr/france-75/paris. Ignoring the URL path will treat these as duplicates of the same organization.

In the Associate app: When defining rules to match related records, select "URL Path" in the Ignored dropdown to exclude paths from comparison. For example, when associating contacts to companies, you can match contacts from perthur.com/us/western-region and perthur.com/uk/northern-region to the same parent company by ignoring their regional URL paths.

Learn more about finding duplicates and creating associations in Insycle.