Migrate from Cloze to HubSpot

Cloze People map directly to HubSpot Contacts. The primary company association in Cloze becomes Contact.Company (lookup). Any secondary company associations in Cloze that exist simultaneously are noted for manual secondary-company linking in HubSpot after migration, since HubSpot contacts have one primary company field.

Cloze Companies map 1:1 to HubSpot Companies. Parent-child company hierarchies in Cloze map to HubSpot's Parent Company field. Industry, employee count, annual revenue, and website domain all migrate as direct field mappings. Any Cloze company custom fields become HubSpot custom properties on the Company object.

Cloze Projects (the company's deal-oriented objects) map to HubSpot Deals. Deal name, value, close date, owner, and priority all migrate directly. Cloze's stage per project maps as a custom property (Project_Stage__c) since HubSpot's dealstage is tied to pipeline stage pick-lists. If Cloze uses multiple pipelines, each maps to a separate HubSpot pipeline.

Cloze stages (Lead, Potential, Active, Inactive/Past, Lost) split across two representations in HubSpot. For contacts, HubSpot's native lifecycle_stage property accepts the values directly. For deals, a custom pick-list property (Project_Stage__c) preserves the exact Cloze stage value per project record. Stage-change history is not preserved as a timeline but as a snapshot value on each record.

Cloze Score is a proprietary 1–100 relationship health metric with no native HubSpot equivalent. We migrate it as a custom Number property (Cloze_Score__c) on the HubSpot Contact. The score reflects the state at migration time; HubSpot does not recalculate it. If your team uses Cloze Score to prioritize outreach, you should set up HubSpot's own contact scoring model post-migration as a replacement.

Cloze timeline entries — calls, emails, texts, and meetings — map to HubSpot Engagements. Each activity preserves its original timestamp, direction (inbound/outbound), duration for calls, and outcome or note body. Owner is resolved by email match against HubSpot users. Inline images in note bodies are downloaded and re-uploaded as file attachments.

Cloze notes attached to People, Companies, or Projects migrate as HubSpot Notes. The note body, timestamp, and owning user all transfer. Rich-text formatting is preserved. Notes linked to specific records retain their association in HubSpot through the notes attach-to-object relationship.

Cloze Segments (audience groups like customers, buyers, sellers, partners) do not have a direct HubSpot equivalent. We create HubSpot static lists for named segments and populate them with the contacts that belonged to each segment in Cloze. If your Cloze segments overlap (one contact in multiple segments), those contacts are added to all applicable HubSpot lists. Segment definitions themselves do not carry over as dynamic rules.

Cloze's tag system applies to People, Companies, and Projects. Tags migrate as a comma-separated text string in a custom HubSpot property (Cloze_Tags__c) on the relevant object. This preserves tag names for reference but does not create HubSpot's native tag system — your team can rebuild tagging in HubSpot using its own property model post-migration.

Cloze Campaigns (automated follow-up sequences, reminder triggers, nurture rules) and any custom workflow logic are not migratable. They must be rebuilt in HubSpot using HubSpot workflows, sequences, and calling sequences. FlitStack AI exports your Cloze workflow definitions as a written reference document your HubSpot admin can use to rebuild equivalent logic in HubSpot's automation engine.

Cloze integrations connected to external apps (calendar, email, LinkedIn, etc.) are connection-level settings that do not transfer. Each integration must be re-connected in HubSpot from scratch. Third-party integrations that were driving Cloze workflows (e.g., Zapier automations triggered by Cloze) must be rebuilt as HubSpot-connected Zaps or native integrations.

Files and attachments stored in Cloze are downloaded and re-uploaded to HubSpot Files. File size limits in HubSpot apply (25MB per file for standard storage). Files are associated back to the originating record (Contact, Company, or Deal) after re-upload. Inline images embedded in note bodies are handled separately as part of the note migration.