Migrate from Knack to HubSpot

Knack records in a people-type table map directly to HubSpot contacts. Each Knack record becomes one HubSpot contact. The HubSpot contact email property is populated from the Knack email field if present; records without email land as contacts but cannot receive HubSpot email sequences.

Knack records in an organization-type table map directly to HubSpot companies, with each Knack record becoming one HubSpot company. HubSpot's company-domain field can be auto-populated from contact email domains for immediate association. Parent-child company hierarchies in Knack, defined through connections between organization records, map to HubSpot's parent company field, preserving organizational structure.

Knack has no native deal object; a deal table is a user-built table with a status or stage field. We map this to a HubSpot Deal object, creating a HubSpot pipeline and stages that match the Knack status values. Stage probabilities are assigned per mapping plan before migration runs.

Knack's connection field linking a person table to a company table maps to HubSpot's primary company association on the contact. If a Knack contact links to multiple companies, the primary (most recently modified or user-specified) becomes the HubSpot primary company; others are preserved as secondary associations.

Knack connections linking contacts to a deal table become HubSpot deal contact associations. HubSpot surfaces these on the deal record as associated contacts. Knack does not have a native role label (e.g., Decision Maker), so no role property is set unless a Knack field explicitly captures it.

When a Knack deal table has a connection to a company table, we associate the resulting HubSpot deal with the corresponding HubSpot company. This replicates the 'deal belongs to account' model that HubSpot uses for reporting by company, enabling revenue attribution to specific accounts. The association is created by matching Knack connections between deal and company records to the equivalent HubSpot records after migration.

Any Knack table that does not map to Contact, Company, Deal, or Ticket becomes a HubSpot custom object. Custom objects require Enterprise-tier HubSpot; we verify your HubSpot plan before quoting. Custom object associations (N:N connections in Knack) require HubSpot junction objects, which we include in the migration plan.

Knack file fields (images, documents) are downloaded from Knack storage and re-uploaded to HubSpot's file manager. File names and original URLs are preserved in a custom text property on the record so the migration audit shows where each file came from.

Knack records carry a created date timestamp from the platform that reflects when each record was originally entered. HubSpot's native CreatedDate property is set at migration time, overwriting the original timestamp. To preserve reporting continuity and audit data, we store the original Knack created date in a custom datetime property — for example, Original_Created_Date__c — so historical reporting based on original record creation dates remains accurate.

Knack has App Users and Builders as role types but no CRM owner field by default. If your Knack tables include a user assignment field, we resolve each Knack user email against HubSpot users and assign OwnerId on the destination record. Unmatched users are flagged for pre-migration onboarding.