Migrate from Breakcold to Nutshell

Breakcold Contacts migrate to Nutshell People. We map name fields, email, phone, social handles (LinkedIn profile URL, Twitter handle), and lifecycle stage as a custom field on People. LinkedIn profile URLs stored as Contact properties in Breakcold migrate to the standard LinkedIn URL field on Nutshell People. Any stale LinkedIn metadata (profile image, connection count) from Breakcold's social sync that went stale due to connection drops migrates as text fields with a staleness flag so the customer can decide whether to re-enrich via Nutshell's Growth plan AI or a third-party enrichment tool.

Breakcold's distinct Lead object migrates directly to Nutshell Leads, preserving Lead status, source attribution, and owner assignment. If the customer uses Breakcold's lead scoring based on token-credit AI, we preserve the numeric score as a custom field on Nutshell Lead rather than attempting to replicate the scoring logic, which cannot be exported.

Breakcold Company profiles linked to Contacts migrate to Nutshell Company records. We map company name, domain, industry, size, and all custom Properties (text, number, date, boolean, multi-select). Multi-select values from Breakcold are serialized as pipe-separated strings in Nutshell custom fields since Nutshell does not have a native multi-select type. Parent-child company relationships in Breakcold map as custom fields or a notes field in Nutshell.

Breakcold Pipelines migrate to Nutshell Pipelines with stage ordering preserved. Pipeline-level automation rules are not accessible via API and are documented in the handoff inventory rather than migrated. We map each Breakcold pipeline to a Nutshell pipeline, preserving custom stage names and stage colors as metadata notes since Nutshell supports stage colors.

Breakcold Pipeline Stages migrate to Nutshell Pipeline Stages with stage order, name, and probability percentage preserved. When Breakcold stages map to fewer Nutshell stages, we collapse multi-stage groupings into the closest equivalent and document the mapping in the handoff sheet. Probability percentages round to the nearest integer as Nutshell accepts.

Breakcold multichannel Activities migrate to Nutshell Activity records with activity type, timestamp, channel, and body content preserved. Channel metadata (LinkedIn message thread, WhatsApp thread ID) transfers as text fields in Nutshell. Call duration and disposition notes migrate as custom fields on the Activity. We preserve the original timestamp for activity timeline ordering. Note that Nutshell's activity timeline shows all activities on the People and Companies record; channel-specific metadata allows reps to reference the original thread context.

Breakcold supports unlimited standalone custom Objects with their own properties. Nutshell does not have a standalone custom object type; instead, custom data lives as custom fields on People, Companies, and Leads. We pre-create the destination custom fields in Nutshell during schema setup, then migrate custom Object records by linking them to the appropriate parent record (Person, Company, or Lead) via a custom lookup field. If a Breakcold custom Object has no natural parent in Nutshell's model, we create a dedicated People record to serve as the container and document this design decision.

Breakcold flat string tags on Contacts and Leads migrate to a Nutshell custom multi-value text field or a dedicated Tag field if the customer enables tagging in Nutshell Settings. Tag names are preserved verbatim. If the customer uses Breakcold tags for segment-based outreach, we document the tag-to-segment mapping for rebuilding in Nutshell.

File attachments on Breakcold Contact records and Activities migrate as hosted URLs or downloaded blobs depending on size. We preserve the original file name and MIME type. Attachment rendering compatibility in Nutshell depends on file format; PDF and image attachments typically render inline. We do not guarantee full fidelity for non-standard file formats and document any attachments that did not transfer cleanly.

Breakcold workspace Users and their role assignments (Admin, Member) map to Nutshell Users. We resolve by email match. Owner assignments on Contacts, Leads, and Companies are preserved by resolving the Breakcold user ID to the Nutshell User email. Any Breakcold user without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before the final migration run.