Migrate from Breakcold to Twenty CRM

Breakcold Contacts map to Twenty CRM Contacts. We preserve name, email, phone, social handles (LinkedIn URL, Twitter handle), lifecycle stage, and all custom properties as custom fields in Twenty. The Breakcold contact identifier is stored in a custom field breakcold_id__c for audit traceability. LinkedIn profile data is preserved as text fields even if the LinkedIn sync connection is stale; we flag stale records during scoping so the customer can decide whether to re-enrich post-migration.

Breakcold Leads map to Twenty CRM Contacts with a custom status__c field set to 'Lead' to distinguish them from migrated Breakcold Contacts (status__c = 'Contact'). We preserve lead source attribution and any custom properties as Twenty custom fields. The original Breakcold Lead ID is stored in breakcold_lead_id__c. If the customer uses Twenty's opportunities for lead tracking, Leads may alternatively map to Opportunity records with a Lead record type; the customer chooses during scoping.

Breakcold Company records map directly to Twenty CRM Companies. Domain serves as the dedupe key during import. Company name, industry, size, domain, and all custom properties migrate as custom fields in Twenty. The Company record is created before any Contact import so that the Company-Contact relationship is satisfied at the moment of Contact insert. Breakcold's linked Company records are associated with their related Contacts via Twenty's domain matching or a manual company_id field.

Breakcold Pipelines map to Twenty CRM's Pipeline settings. Each Breakcold pipeline name becomes a named pipeline in Twenty's Opportunity pipeline configuration. If Twenty's pipeline configuration supports multiple pipelines, we create one per Breakcold pipeline; if only a single pipeline is used, we use a custom opportunity_type__c field to distinguish pipeline attribution and document the mapping for the customer's admin to configure in Twenty's Pipeline settings.

Breakcold Pipeline Stages map to Twenty CRM Opportunity stages within each pipeline. We preserve stage name, order, and probability percentage as Twenty stage configuration. Stage count differences between Breakcold and Twenty are resolved by merging adjacent stages or creating a catch-all 'Other' stage for overflow, with a written mapping document for the admin to finalize in Twenty's Pipeline settings.

Breakcold Deals map to Twenty CRM Opportunities. Deal name becomes Opportunity name; deal amount and currency migrate directly; the linked Contact and Company resolve via the Contact and Company imports. Deal custom properties migrate as Opportunity custom fields. We map the Deal's pipeline and stage to the corresponding Twenty pipeline and stage configuration set up in the schema design phase.

Breakcold's multichannel Activities (Email, LinkedIn, WhatsApp, Telegram, Call) map to Twenty CRM Activity records. We preserve activity type, channel (stored in a custom channel__c field since Twenty's activity model does not natively distinguish LinkedIn from Email), body content, timestamp, and direction (inbound/outbound). The activity is linked to the parent Contact via Twenty's targetObjectId. Note that Twenty does not have a native multichannel inbox UI; activities appear as separate timeline entries per channel rather than a unified threadable view.

Breakcold unlimited custom Objects map to Twenty CRM custom objects. We pre-create the destination schema in Twenty via its API or admin UI before any data import, including all custom fields with type translation (text, number, date, boolean, multi-select). Multi-select values are serialized as semicolon-delimited strings in Twenty text fields unless Twenty's schema supports multi-select picklists at the time of migration. Custom object relationships to Contacts, Companies, or Opportunities are preserved as Twenty custom relationship fields.

Breakcold Tags (flat string labels on Contacts and Leads) are collected as a migration artifact and applied to Twenty CRM Contacts as a custom text field (tags__c). If Twenty supports multi-select picklists at migration time, we use that field type instead for a closer semantic match. The customer chooses the tag strategy during scoping. Tags used for segmentation are documented separately for potential list rebuild in Twenty.

File attachments on Breakcold Contact records and Activities are preserved as URLs or downloaded and re-hosted depending on file size and Breakcold's storage access. We do not guarantee attachment rendering compatibility in Twenty since Twenty's attachment model differs. Large file attachments may require a separate file hosting strategy (S3, Dropbox, SharePoint) with links stored in Twenty's custom fields.

Breakcold workspace Users and their role assignments (Admin, Member) are mapped to Twenty CRM Users by email match. We resolve owners referenced on Contacts, Leads, Deals, and Activities. Users without a matching Twenty account enter a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission parity (Admin vs Member) is documented as a written recommendation for the Twenty admin to configure in Twenty's workspace settings.

Breakcold workflow rules and automation triggers are not accessible via API and cannot be programmatically exported. This includes any token-credit-based AI automation and lead-scoring logic. We document the automation structure during discovery (enumeration of triggers, conditions, and actions as observed in Breakcold's UI) and deliver a written inventory with recommendations for manual rebuild in Twenty's workflow tools. The customer or a Twenty implementation specialist handles the rebuild post-migration as a separate engagement.