Migrate from Close to HubSpot

Close Lead is the primary person record. It maps to HubSpot Contact. The contact's name fields (first_name, last_name) from Close are split into HubSpot's structured firstname and lastname fields. Any contact records in Close that represent existing customers route to HubSpot Contact with lifecycle_stage set to 'customer' during migration.

Close also supports a secondary Contact object on a Lead. These map to HubSpot Contact directly. Each Close contact record receives the same HubSpot Contact field mapping as the parent Lead record. Multiple Close contacts on the same Lead create multiple HubSpot Contact records, each linked to the primary HubSpot Company.

Close Organization maps to HubSpot Company. Organization name maps to Company name. Domain is mapped to Website. Industry, employee count, and address fields map to their HubSpot equivalents. Close's Organization hierarchy (parent/child) maps to HubSpot's associated company relationships. Organizations without a domain receive a placeholder website entry.

Close Opportunity maps directly to HubSpot Deal. Deal name, amount, expected_close_date, probability, and stage_name all map to HubSpot Deal fields. The pipeline association in Close is preserved as a Deal Pipeline assignment in HubSpot. Each Close Opportunity is associated with a Contact and an Organization, both of which are resolved to their HubSpot equivalents before the Deal is written.

Close Pipeline maps 1:1 to a HubSpot Deal Pipeline. Each pipeline's stage names are mapped to HubSpot Deal Stages within that pipeline. Probability values per stage are preserved as HubSpot stage metadata. If Close has multiple pipelines, each becomes a separate HubSpot Deal Pipeline — the migration plan includes pipeline creation in HubSpot before any Deal records are written.

Close's built-in call records migrate to HubSpot as logged activities. Call duration, outcome (answered, voicemail, no answer), and caller ID are preserved as properties on the engagement record. Call notes from Close map to a HubSpot Engagement Note. The activity is associated to the correct HubSpot Contact by email match.

Close email history maps to HubSpot engagement records. Subject, body preview, timestamp, and sent/received status are preserved. HubSpot's email tracking and engagement logging captures the full thread history. If Close has email templates attached, those templates are exported as a JSON reference file for manual rebuild in HubSpot.

Close SMS message history migrates as HubSpot engagement notes with an SMS type marker. The phone number, message content, direction (sent/received), and timestamp are preserved. Note that HubSpot's native SMS tracking is a separate product — the migration preserves the data for reference; SMS sending capability requires HubSpot configure a separate calling or SMS integration.

Close Tasks map to HubSpot Tasks. Task subject, body, due date, status (completed/open), assigned user, and completion timestamp are all preserved. Owner assignment is resolved by email match against HubSpot users. Tasks associated with a specific Lead or Contact are linked to the migrated HubSpot Contact record.

Close Custom Activities (user-defined activity types like 'Demo Scheduled', 'Proposal Sent') require a case-by-case mapping decision. If the activity represents a deal milestone, it maps to a HubSpot custom Deal property (text, date, or picklist depending on the data type). If the activity represents a standalone event type, it maps to a HubSpot custom object — the migration plan documents which approach applies to each unique Custom Activity Type.

Close custom fields on Lead objects map to HubSpot Contact custom properties. Field data type is preserved — text, number, date, and Boolean map directly. Picklist fields require the picklist options to be created as HubSpot property options before import. Multi-select picklist fields in Close require a HubSpot custom property configuration step because HubSpot handles multi-select differently.

Close custom fields on Opportunity objects map to HubSpot Deal custom properties. The same type-preservation logic applies: text, number, date, and Boolean migrate directly; picklist fields require HubSpot property option pre-configuration. The migration plan includes a full inventory of all Opportunity custom fields with their data types to flag any that need HubSpot schema preparation.

Close allows multiple contacts to be associated with a single Opportunity. Each contact-opportunity association migrates as a HubSpot Deal-Contact association. If Close has a designated primary contact on the Opportunity, that contact is set as the primary contact in HubSpot; additional contacts are associated as secondary deal contacts.

Close Smart Views (saved filter configurations) have no HubSpot equivalent. They represent Close-specific filter logic that cannot be exported as reusable objects. FlitStack exports Smart View names and filter criteria as a reference document for the HubSpot admin to recreate as HubSpot saved filters or list filters manually after migration.

Close Workflows (Growth and Scale plans only) are automation rules with triggers, conditions, and actions. HubSpot has its own Workflows product with different trigger and action models. Workflows are not migrated. FlitStack exports the full workflow definitions — triggers, steps, conditions, and actions — as a structured JSON reference so the HubSpot admin can rebuild them in HubSpot's workflow builder.