Migrate from Click to HubSpot

Click person records map directly to HubSpot Contacts. Email, phone, name, and address fields transfer 1:1. Custom fields on the person record become HubSpot contact properties with type-aware conversion (text, number, date, dropdown, checkbox, etc.). Original create dates and last-modified timestamps are preserved in custom datetime properties.

Click business records map to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue fields transfer directly to their HubSpot equivalents with matching property names where possible. Parent-child company hierarchies in Click translate to HubSpot's Parent Company association if present in the source data, preserving organizational structures during the migration.

Click Lists used as deal pipelines translate to HubSpot Deal Pipelines. Each distinct List becomes a named HubSpot pipeline with its own stage set. List stage names become HubSpot stage names with probability and forecast category assigned per stage during migration.

Click List items that represent deals (with amount, close date, and owner fields) migrate to HubSpot Deals. The dealname, amount, closedate, and hubspot_owner_id equivalent map to HubSpot Deal fields. Stage value is resolved through the pipeline mapping established for the parent List.

Click custom fields are not scoped to a single object in the same way HubSpot properties are. FlitStack AI identifies the primary object each custom field belongs to in Click's data model and creates the corresponding HubSpot custom property on Contact, Company, or Deal. Multi-value custom fields (tags, multi-select) map to HubSpot multi-checkbox or multi-select properties.

Click comments on List items migrate as HubSpot engagements. Notes attach to the migrated record (Contact, Company, or Deal) with the original timestamp and author preserved. Rich-text formatting in Click comments converts to HubSpot's note format, maintaining inline styles, bullet points, and basic formatting where supported.

Files attached to Click List items are downloaded and re-uploaded to HubSpot Files, then associated with the corresponding Contact, Company, or Deal record. File size limits (HubSpot default 25MB per file) apply. Inline images in notes are extracted and re-hosted as HubSpot file attachments.

Click allows a contact to belong to multiple Lists simultaneously, creating an N:N relationship pattern. In HubSpot, a contact can associate with multiple companies using the Company Associations feature with labels (Customer, Partner, Vendor). We map primary List membership to the primary Company association and secondary memberships to additional Company associations.

Click user records are matched to HubSpot users by email address before migration. Unmatched users are flagged for the customer team to create HubSpot accounts or assign to a fallback owner. Owner assignments on Deals and Contacts resolve to the matched HubSpot user ID.

If Click uses custom status values beyond standard open/closed (for example, In Review, Pending Approval, Blocked), these are mapped value-by-value to HubSpot Deal stage names or stored as a custom pick-list property on the Deal object for reporting clarity. All status mappings are documented in the migration specification for customer review before execution.

If Click has integrated email or call logging (via third-party integrations), those records migrate as HubSpot engagements on the correct contact timeline. Logged emails appear as Email type engagements; logged calls appear as Call type engagements, each with original timestamps and owners preserved.

If Click contains custom objects beyond the standard Contact/Company/List-item model, those map 1:1 to HubSpot custom objects on Enterprise plans. Custom object relationships (lookup, many-to-many) are preserved using HubSpot's association labels and custom relationship properties, maintaining referential integrity across the migrated dataset.