Migrate from ClinchPad to HubSpot

ClinchPad Leads map directly to HubSpot Contacts. The contact's name, email address, phone number, and company link transfer as‑is. If ClinchPad stores a lifecycle‑aware status field, it is mapped to a custom HubSpot property because HubSpot's standard contact properties do not natively capture this type of stage‑aware flag.

ClinchPad Clients represent company records and map to HubSpot Companies, preserving fields such as company name, domain/website, industry classification, employee count, and annual revenue. If ClinchPad records parent‑child hierarchies, these relationships are transferred as HubSpot’s parent‑company association on the Company object, maintaining organizational context.

ClinchPad contacts attached to a Client are extracted as standalone HubSpot Contacts and linked to the corresponding HubSpot Company via a company association. Their independent fields—including name, email address, phone number, and job title—map directly to HubSpot’s standard contact properties for immediate usability.

ClinchPad Deals map to HubSpot Deals with deal name, amount, close date, and stage name preserved. The source ClinchPad pipeline name maps to a HubSpot Deal Pipeline (created in HubSpot if it does not already exist). Deal owner resolves by email match against HubSpot users.

Each ClinchPad deal stage name maps to a corresponding HubSpot Deal Pipeline stage. If ClinchPad uses per-deal custom stages, FlitStack consolidates them into a canonical stage list per pipeline before mapping. Stage order and probability re-applied based on the destination pipeline configuration.

ClinchPad workspaces with a single pipeline map to one HubSpot Deal Pipeline. Multi-pipeline ClinchPad setups (Enterprise tiers) map to multiple HubSpot Deal Pipelines. Each pipeline is created in HubSpot before the migration run so Deals land in the correct pipeline automatically.

ClinchPad custom fields on Deals (beyond the standard fields) become HubSpot custom deal properties. These properties are created in HubSpot before migration so all Deals can populate them during the import. Field types (text, number, date, picklist) are preserved with type-aware transformation.

ClinchPad custom fields on Leads or Contacts migrate as HubSpot custom contact properties. If ClinchPad stores a single combined contact profile, the custom fields attach to the resulting HubSpot Contact record. Property creation is done before migration so no data is dropped during import.

ClinchPad Notes attached to Deals or Clients become HubSpot Engagement notes on the corresponding Contact or Deal record. Original create timestamps and note authors (owner) are preserved. Rich-text formatting is simplified to plain text to match HubSpot's engagement note format.

ClinchPad tasks (to-dos, follow-ups) map to HubSpot Tasks. Task status (open/completed), due date, and owner are transferred. Completed tasks retain their completed state in HubSpot. HubSpot's task model does not support subtasks natively, so nested ClinchPad tasks are flattened to individual tasks with a reference note.

ClinchPad file attachments on deals or clients are downloaded and re-uploaded to the corresponding HubSpot Company or Deal record as Files. File size limits per HubSpot plan apply (25MB per file on most tiers). We flag any attachment exceeding the destination limit before the migration runs.

ClinchPad tags applied to Leads, Clients, or Deals are migrated as HubSpot multi‑select custom properties. When a record contains multiple tags, they are combined into pipe‑delimited values within HubSpot’s multi‑select field. For tags that represent a simple yes/no indicator, the migration creates a single‑select property instead, preserving the original intent.