Building value mappings one row at a time in the Transform Data module works fine when you have a handful of substitutions. But when you're standardizing company name abbreviations, industry codes, or territory labels across thousands of records — and you need those mappings enforced continuously, not just once — Insycle offers a better long-term home for that work in the Data Logic module.

You can now export your Transform Data mappings directly to a Blueprint CSV, ready to use in Data Logic. Instead of manually rebuilding your mapping logic from scratch, the export captures everything you've already configured and outputs it in the format Data Logic expects — so you can move your mappings to the tool built to run them at scale, automatically, across all records.

For example, if you've mapped abbreviations like CU → Credit Union, FCU → Federal Credit Union, and CB → Community Bank in Transform Data, the export generates a Blueprint CSV with those mappings ready to load.

If any existing text entry used pipe delimiters to define multiple variations (for example, NY|NYC|New York City → New York), the export automatically splits those into individual rows so the Blueprint is structured correctly.

To use it, configure any supported map function in step 2 of Transform Data — the blue Export button will appear in that row.

Learn more about Transform Data and Data Logic.

If your team manages territory assignments, lead scoring, routing rules, field classifications, or similar logic in your CRM, you know the maintenance burden: every time a rule changes, someone has to track down the right process branch, update conditions, test it, and hope nothing breaks. For logic that lives in your head — or in a spreadsheet — keeping the CRM in sync is a constant, manual effort.

Data Logic and Blueprints replace that process with a table. You define your business logic as rows and columns in a CSV — match conditions and output values — and Insycle applies it across your records. When your logic changes, you upload a new version of the table. There's nothing to rebuild.

A Blueprint is the table itself. Data Logic is the module that connects it to your CRM fields, controls when each field is updated, and runs the operation across your records. The same Blueprint can be reused across multiple configurations, applied to any supported CRM, and scheduled to run automatically.

For example, if you assign sales territories based on country, state, and industry, you can define every combination as rows in a Blueprint — each row specifying the Region, Territory Owner, and Sales tier to apply — and configure Data Logic to match records against it and update those fields automatically. When territories change, you update the Blueprint via a CSV file.

Blueprints can be built from a CSV you already have, created from one of Insycle's example templates, drawn from a library of reference data, or generated from scratch using AI, which analyzes your CRM fields and can suggest use cases, match common business logic patterns, or build a Blueprint from your own description.

Learn more about Data Logic and Blueprints.

HubSpot enforces a strict rule for Lifecycle Stage: it can only move forward in the funnel. When duplicates are merged — whether directly in HubSpot or through Insycle's native merge — HubSpot automatically keeps the stage furthest down the funnel, no exceptions. If your master record is a Lead but another duplicate is a Customer, the merged record becomes a Customer, regardless of your intent.

For teams that need to retain an earlier Lifecycle Stage after a merge — for example, to flag a record for re-nurturing or to match an internal classification — there was previously no way to override this.

Insycle now lets you control exactly which Lifecycle Stage is retained using Native merge, even if it's earlier in the funnel than the default HubSpot behavior would select. You can designate a specific stage from either the master record or any duplicate in the group, and Insycle will apply it to the merged record — bypassing HubSpot's usual funnel-progression rule. This applies to HubSpot contacts and companies.

For example, if your master record is tagged as Lead and a duplicate is tagged as Customer, Insycle can retain Lead on the merged record — something that isn't possible when merging directly in HubSpot.

To use this, go to the Merge Duplicates module, under 3. Merge Logic on the Method tab, make sure your Merge API is set to Native, and then set your Lifecycle Stage selection rule on the Fields tab.

Learn more about merging duplicates in HubSpot.

Salesforce databases often contain hundreds of fields—far more than most teams actively use. Without a way to control which fields are pulled into Insycle, your dataset can become bloated with unnecessary data, slowing syncs and making filtering and duplicate matching more difficult.

You can now choose exactly which Salesforce fields are included in your Insycle dataset — the same self-service field inclusion controls already available for HubSpot now work for Salesforce as well.

In Insycle, go to Settings > Fields, select your Salesforce database and object type, and use the Included toggle to add or remove individual fields from your dataset. The Fields table shows each field's label, internal name, field type, and writability, giving you full visibility into what's available. Fields used in automated Recipes and templates are protected and included automatically — you're only managing the additional fields you choose to bring in. You can include up to 100 fields per object type (150 for Enterprise plans).

For example, if your team tracks sales territory and contract tier in custom Salesforce fields, you can enable those fields so they're available for filtering and standardization in Insycle — without pulling in hundreds of fields you'll never use.

Field inclusion changes take effect during the overnight sync process. If you need fields available sooner, contact support to trigger an immediate sync. Note that an Admin or Owner user role is required to manage field inclusion.

Learn more about managing which Salesforce fields are included in Insycle.

When importing into Salesforce, one of the most common pain points is not knowing whether a person already exists in your CRM—and whether they're a Lead or a Contact. Without a way to check both object types at the same time, avoiding duplicates meant running separate comparisons and manually consolidating the results.

Insycle’s Magical Import now supports cross-object matching for Leads and Contacts for Salesforce. When importing into Leads, you can enable an Including Contacts toggle to match against Contacts as well. Likewise, when importing into Contacts, you can enable the Including Leads toggle to match against Leads as well.

Insycle searches across both object types simultaneously and returns a unified preview showing each record's type, so you can see exactly where every row stands before committing to an import. A Type column in the Preview and in CSV reports indicates whether each matched record is a Lead or Contact, giving you complete visibility into the results without leaving Insycle.

For example, you're importing a prospecting list from Sales Navigator. Some people on the list already exist as Contacts; others are Leads; and a few aren't in Salesforce at all. With cross-object matching enabled, Insycle identifies each one in a single pass, updates the existing record if a match is found, and creates a new Lead only for rows with no match in either object type—no manual cross-checking needed. It will also flag if duplicates are present in your database.

Learn more: Cross-Object Matching for Leads and Contacts in Magical Import

When merging duplicates, the right merge method depends on your CRM setup, the object types involved, and the level of control you need over the outcome. Until now, that choice has happened behind the scenes. The new Merge API setting — found on the Method tab in Step 3: Merge Logic — puts it in your hands.

Available for HubSpot and Salesforce users, the Merge API lets you choose between two merge approaches: Native, which uses your CRM's built-in merge logic, and Synthetic, which uses Insycle's custom merge logic for greater control over field retention, master record selection, and complex associations.

Insycle selects a sensible default based on your platform and object type — for example, Native is the default for HubSpot Contacts and Salesforce Contacts, Leads, and Accounts, while Synthetic is the default for object types that don't have native CRM merge support. But now you can override that default when your use case calls for it.

For example, a user merging HubSpot Contacts might switch from Native to Synthetic merge because they need the master record's ID to remain unchanged — such as when that record ID is referenced in an external system and changing it would break the connection.

Learn more:

• Native Merge vs. Synthetic Merge behavior in HubSpot
• Native Merge vs. Synthetic Merge behavior in Salesforce

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.