Migrate your Breakcold data

Breakcold Contacts are the primary object, supporting unlimited contacts per plan. We migrate Contact profiles including name, company, social handles, email, phone, and lifecycle stage. LinkedIn-sourced profile URLs are preserved as custom Properties rather than native fields.

Breakcold uses a distinct Leads object separate from Contacts. We map Leads to the destination CRM's Lead or Contact object, preserving the Lead status and source attribution. Where the destination lacks a separate Lead object, we merge into Contacts and carry the status as a custom property.

Pipelines are the core organizational unit. We migrate Pipeline names, stage counts, and stage ordering. Custom stage names and colors are preserved as metadata. We flag Pipeline-level automation rules since these require manual reconfiguration in the destination CRM.

Each Pipeline contains ordered Stages with optional probability percentages. We preserve stage order, name, and probability. When the destination has fewer standard stages than the source, we map multiple source stages to a single destination stage and flag the compression.

Breakcold logs Activities across Email, LinkedIn, WhatsApp, Telegram, and Call channels into a unified timeline. We preserve activity type, timestamp, channel, and body content. Channel-specific metadata (e.g., LinkedIn reaction type) is stored as a custom property. Activity count is preserved; full thread history depends on the destination CRM's API access to archived messages.

Breakcold supports unlimited custom Objects created by the user. We migrate custom Object records with their associated custom Properties. Schema mapping requires field-type translation since destination CRMs name and type custom Objects differently. We preserve the relationship between custom Object records and the parent Contact or Company.

Custom Properties on Contacts, Leads, Companies, and custom Objects are migrated with field-type translation. We handle text, number, date, boolean, and multi-select types. Multi-select values are serialized as delimited strings in CRMs that lack native multi-select support.

Breakcold supports Company profiles linked to Contacts. We migrate Company name, domain, industry, size, and custom Properties. Linked Company records are associated with their related Contacts during migration.

Breakcold supports cold email Sequences with personalization variables. We migrate sequence structure, step count, step types, and delay configuration. We do not migrate email account credentials or deliverability history; those must be reconnected in the destination CRM.

LinkedIn data including profile URLs, connection dates, post engagement data, and Sales Navigator prospects are stored as Contact Properties. We preserve the raw LinkedIn profile URL and scraped metadata. Direct API access to LinkedIn's own data is not available from Breakcold, so engagement history requires re-sourcing.

Tags are flat string labels applied to Contacts and Leads. We preserve tag names and apply them to the corresponding records in the destination CRM. Where the destination uses a different tagging model (e.g., HubSpot Lists), we map tags to equivalent segments or custom properties.

File attachments on Contact records and Activities are migrated as hosted URLs or downloaded blobs depending on size. We do not guarantee attachment rendering in the destination since compatibility depends on file format and storage limits.

Breakcold workspace Users and their role assignments (Admin, Member) are mapped to the destination CRM's user model. We preserve the Owner assignment on Contacts and Leads. Role and permission parity cannot be guaranteed across platforms due to differing permission architectures.

Breakcold workflow rules and automation triggers are not accessible via API and cannot be programmatically exported. We document the automation logic during discovery so it can be manually rebuilt in the destination CRM. No automated translation of automation logic is possible.