Blueprints

A Blueprint is a CSV file made up of input columns and output columns.

• Input columns define the matching conditions — the values the system checks against your CRM records to find a match. 
• Output columns define the outcomes — the values written to your CRM fields when a record matches a row.

When Data Logic evaluates a record, it checks the record against each row in the Blueprint from top to bottom. The first row where all input column conditions are satisfied is the matching row. The output values from that row are then applied to the record's CRM fields according to the update conditions configured in Data Logic.

A Blueprint that assigns territory and sales tier based on country and employee count might look like this:

In this Blueprint, Country and Employees are the input columns used to match records, and Territory and Sales Tier are the output columns whose values are written to CRM fields when a match is found. A company record with Country = United States and Employees = 750 matches the first row and receives the corresponding Territory and Sales Tier values.

A Blueprint is the single system of record for a piece of business logic — one table that defines the rules, versioned over time, and applied consistently across your CRM records.

HubSpot Workflows and Salesforce Flows use branching if/else logic. As the number of conditions grows, they become difficult to read, slow to update, and brittle to maintain. A territory model covering 50 countries with size-based tiers requires hundreds of branches. The same logic in a Blueprint is a table with rows that any RevOps or operations team member can read, edit, and version — without touching a single Workflow or Flow.

Blueprints also support multi-field matching and multi-field outputs in a single operation. One matching row can evaluate conditions across Country, Industry, and Employee Count, and write back Territory, Sales Tier, Owner, and Region in a single step. Workflows and Flows typically require separate branches and actions for each output field.

Blueprints are not a full replacement for all Workflows or Flows. They are purpose-built for table-driven, multi-field conditional logic — territory assignment, ICP scoring, renewal risk scoring, compliance enforcement, pricing governance, lead source harmonization, and similar use cases. For processes that go beyond field updates — such as sending emails, creating tasks, triggering notifications — Workflows and Flows remain the right tools. Blueprints handle the data logic, while Workflows or Flows handle the rest.

A Blueprint on its own does nothing. It is a definition, not an executor.

Data Logic is the configuration layer that puts a Blueprint to work. It binds Blueprint columns to CRM fields, defines matching criteria for each input, sets update conditions for each output field, applies fallback values for records that don't match, and controls when and how the logic runs.

This separation is what makes the maintenance advantage possible. When business logic changes, you update the Blueprint. The Data Logic configuration stays the same — the same input mapping, the same output mapping, the same filters. The same Blueprint can also be referenced by multiple Data Logic configurations simultaneously, and the same Data Logic configuration continues to work unchanged when a new Blueprint version is uploaded.

For complete details on Data Logic, see Module Overview: Data Logic.

Blueprints are versioned. When the logic changes — a new territory, a revised scoring model, updated suppression rules, new SKU classifications — you update the Blueprint CSV and upload a new version. Each time you upload a new version, Insycle retains all previous versions. You can preview any version and maintain a full history of how the table has changed over time. To restore a prior version, download the CSV file from the Table Preview panel and upload it as a new version.

When you upload a new Blueprint version, all Data Logic configurations that reference that Blueprint automatically use the updated version on their next run. No reconfiguration, Workflow rebuilds, or no code changes required.

Because every version is retained and previewable, a Blueprint functions as an auditable system of record — you can always trace how your business logic has changed over time.

You can create Blueprints from the Data Logic module or the Data Integrity > Blueprints page.

Within Data Logic under 1. Pick Blueprint, choose from five sources:

• Generate with AI
• Explore Examples
• Use Reference Data
• Create from CSV
• Select Existing

For a full breakdown of each source, see Picking a Blueprint for Your Data Logic Template.

The image above shows the 1. Pick Blueprint step in the Data Logic module, configured for a HubSpot demo account with the Contacts object type selected. The five Blueprint source options are listed — Generate with AI, Explore Examples, Use Reference Data, Create from CSV, and Select Existing — with Use Reference Data selected (indicated by the filled radio button). The Blueprint dropdown to the right of Use Reference Data shows GDPR Adequacy Reference selected, with description and version info, plus preview and refresh icons.

You can also create Blueprints by uploading a CSV directly from the Data Integrity > Blueprints page, without going through the Data Logic module.

For a comprehensive guide to structuring your Blueprint CSV — including column conventions, row order, blank-cell handling, numeric and date ranges, and picklist/owner values — see Designing a Blueprint CSV. Two additional techniques are covered there for generating a Blueprint CSV from your existing data: exporting Transform Data map functions and exporting field details from Cleanse Data.

The image above shows the Data Integrity > Blueprints page for a HubSpot demo account. The page displays a list of saved Blueprints with Name, Description, and File Name columns. Two Blueprints are partially visible: Derive Country from State/Province Code, which maps state and province values to their parent country, and Industry + Country → Success Tier & Territory, which matches accounts on Industry and Country/Region to assign Success Tier and Territory values. An Upload button and a Generate button appear at the top of the page, along with a filter field for searching the list.

Upload and manage Blueprints under Data Integrity > Blueprints.

To add a new Blueprint:

1. Navigate to Data Integrity > Blueprints.
2. Click Upload.
   The image above shows the Data Integrity > Blueprints page with the left navigation expanded, showing Blueprints selected under the Data Integrity section. The New button is visible at the top of the Blueprint list, with an arrow pointing to it. The list shows four saved Blueprints: Automobiles, Map Country, Territory ID, and Owner (described as "Map Country and Territory ID"), Simple discount and assignment (described as "Global Sales"), and Company Enrichment.
3. In the Create Blueprint popup, enter a name and, optionally, a description.
4. Click Upload and select your CSV file.
5. Click Create.

The image above shows the Create Blueprint popup with a name, optional description, and uploaded CSV file. The Name field contains "Territory Assignment by Country, State, & Industry," and the Description field contains "assign Region, Territory Owner, Sales Tier, Account Type." A CSV file named Territory-Assignment-Country-State-Industry-AccountType.csv has been uploaded, shown with its file size, row count, column count, and modification date. The Upload button (yellow) and Create button (dark) are visible at the bottom of the popup.

To upload a new version of an existing Blueprint:

1. Click the Blueprint in the list.
2. In the Table Preview below the list, click the Upload New Version icon in the header. The image above shows the Table Preview panel in Data Integrity > Blueprints, displaying version v1 of a Blueprint with columns for Country, State, Industry, Region, Territory Owner, and Sales Tier. The first visible row shows United States / California / Technology mapped to West / Sarah Chen / Enterprise. An arrow points to the Upload New Version icon in the Table Preview header, with a tooltip reading "Upload New Version." The header also shows a version dropdown, description, version info icon, edit icon, and download icon.
3. In the Upload New Version popup, click the yellow Upload button and select your CSV file.
4. Click the grey Upload button.

To preview a Blueprint:

When selecting a Blueprint in Data Logic, a Preview icon appears beside the Blueprint field. Clicking it opens a Blueprint Preview popup that displays the table data and a search field. Use the preview to confirm you have selected the correct Blueprint and version before configuring your input and output mapping.

The image above shows the 1. Pick Blueprint step in the Data Logic module with Explore Examples selected and the Data Quality Enforcement Blueprint chosen from the Blueprint dropdown. An arrow points to the Preview Blueprint icon (eye icon), with a tooltip reading "Preview Blueprint." The description, version info, and refresh icons are also visible alongside the dropdown.