Migrate from Breakcold to Salesforce Sales Cloud

Breakcold Contacts map to Salesforce Lead for prospects without an assigned Account, and to Salesforce Contact for qualified buyers attached to an Account. We define the split rule during scoping based on Breakcold's Lifecycle Stage property and any pipeline stage progression. The original Breakcold Lifecycle Stage is preserved in a custom field bc_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Breakcold Company records map directly to Salesforce Account. The company domain becomes the Account Website field and is used as the dedupe key during import. Account is created before any Contact import so that the AccountId lookup relationship is satisfied at Contact insert time.

Breakcold's distinct Lead object (separate from Contact) maps to Salesforce Lead. Lead status and source attribution from Breakcold migrate as Salesforce Lead Status and LeadSource. Any Breakcold AI-generated lead score stored as a custom property migrates to a custom field bc_lead_score__c.

Breakcold Pipelines map to Salesforce Record Types on Opportunity, with each Record Type assigned a corresponding Sales Process that whitelists the relevant stage values. We pre-configure the Record Types and Sales Processes in a Salesforce Sandbox before migration so that stage values are valid at insert time.

Breakcold stage names, colors, and probability percentages migrate to Salesforce StageName, a custom stage color field, and StageProbability. Stage ordering is preserved in the Sales Process sequence. When Breakcold has more stages than the destination Sales Process supports, we map multi-stage segments to consolidated stages and document the consolidation in the mapping spec.

Breakcold email activities migrate to Salesforce Task (the activity timeline entry) and EmailMessage (the email content and headers). The WhoId on Task points to the migrated Lead or Contact; the WhatId points to the related Opportunity or Account. Email body content preserves formatting.

Breakcold LinkedIn activities map to Salesforce Task with a custom field bc_linkedin_url__c carrying the profile URL and bc_linkedin_data__c holding any scraped metadata. We flag records where the LinkedIn connection was stale (broken sync) during extraction so customers can re-enrich via LinkedIn Sales Navigator post-migration if desired.

Breakcold WhatsApp activities migrate to Salesforce Task with TaskSubtype preserved as a custom field bc_channel__c = 'WhatsApp'. Message body migrates as the Task Description. We do not migrate WhatsApp attachment blobs but preserve hosted URL references where accessible.

Breakcold Telegram activities migrate to Salesforce Task with bc_channel__c = 'Telegram'. Message body migrates as Task Description. Telegram-specific metadata (chat ID, message ID) migrates to custom fields for audit trail.

Breakcold call activities map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any recording URL preserved in custom fields. ActivityDate is set to the original Breakcold timestamp to preserve timeline ordering.

Breakcold meeting activities migrate to Salesforce Event. StartDateTime, EndDateTime, and Location preserve. EventRelation records are created linking attendees to the migrated Lead, Contact, and User records.

Breakcold notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body preserves rich text formatting where supported.

Breakcold unlimited custom Objects migrate to Salesforce custom objects with __c API names. We pre-create the destination schema in a Sandbox—including all custom fields, field types, and lookup relationships to standard objects—before any data import. Any custom object with a lookup to a standard object (Contact, Account, Opportunity) is imported after the parent standard object to satisfy the relationship constraint.

Breakcold custom Properties on Contacts, Leads, Companies, and custom Objects migrate to Salesforce custom fields. We handle text, number, date, boolean, and multi-select types with field-type translation. Multi-select values are serialized as comma-separated strings in Salesforce multi-select picklist fields.

Breakcold flat string tags migrate to Salesforce multi-select picklist fields on the corresponding object. We discuss the tag strategy during scoping: if tags are used for classification, multi-select picklist is the preferred destination; if tags are used for reporting segments, we can alternatively map them to Salesforce Topics with TopicAssignment records.

File attachments on Breakcold Contact records and Activities migrate as ContentDocument records with ContentDocumentLink to the parent record. Attachment rendering in Salesforce depends on file type and size; we do not guarantee visual fidelity for non-standard file formats but preserve the raw file blob.

Breakcold workspace Users and their role assignments (Admin, Member) map to Salesforce User records. We match by email address. Any Breakcold Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Breakcold Sequences with personalization variables are documented during scoping but not migrated as active cadence records. We deliver a written inventory of every Sequence including step count, step types, delay configuration, and personalization variable mappings, so the customer's admin can rebuild in Salesforce Sales Engagement (High Velocity Sales) or a third-party cadence tool post-migration.