Migrate from Sales Flow Technologies to Salesforce Sales Cloud

Sales Flow Contacts with no associated deal history, no company Opportunity, and an outreach-only status map to Salesforce Lead. We use the Contact's last_sequence_enrollment_date and outreach_enrollment_status to determine whether the record is a raw prospect (Lead) or a converted buyer contact. All original Sales Flow custom properties migrate as Salesforce Lead custom fields with __c suffix. The original Sales Flow contact_id preserves as sf_salesflow_id__c for dedupe and cross-reference.

Sales Flow Contacts that the customer marks as customers, closed-won, or high-intent (based on sequence engagement scoring in the source) map to Salesforce Contact linked to an Account. We use the Contact's associated Prospect List membership and sequence completion status to infer account context. If the source Contact has a company_name property but no separate Account in Sales Flow, we create the Account first during migration, then link the Contact.

Sales Flow Contacts carry a company_name property that maps to Salesforce Account Name. We extract all unique company_name values from the Contact export, create Account records using company_name as the Account Name and the domain extracted from email as the Website, then backfill AccountId on the Contact migration. If the customer has no separate Account creation workflow, this extraction step ensures that every Contact in Salesforce has an Account parent.

Sales Flow Prospect Lists are named groupings of Contacts used to organize outreach targets. We export list membership via CSV with a dedicated column indicating list assignment, then create Salesforce Campaigns (Campaign Type = Sales Flow Prospect List for lineage) and enroll the Contacts as Campaign Members with Member Status = Sent. List names and creation dates preserve as Campaign Name and Campaign Start Date.

Sales Flow Sequences define the cadence and channel steps (LinkedIn connection request, follow-up email, InMail) for a group of Contacts. Sequence step ordering and timing data migrate as Campaign Member history entries — each step becomes a Campaign Member with a custom field tracking the step number, channel, template used, and scheduled date. We preserve the sequence step order as a numeric sort field. Channel routing logic and A/B testing configurations do not transfer; we document them in the Workflow Reconstruction Summary.

Sales Flow Campaigns bundle multiple Sequences under a single objective. We migrate Campaign names, associated Sequence count, and the campaign-level reporting date range as Salesforce Campaign Start Date and End Date. Channel routing logic and A/B testing configurations are documented in the Workflow Reconstruction Summary and are not migrated as automation code.

Sales Flow provides per-sequence and per-step open rates, reply rates, and connection acceptance rates. We export these metrics as a structured CSV report and create custom fields on the Salesforce Campaign and Campaign Member objects (e.g., sft_open_rate__c, sft_reply_rate__c) to carry the historical engagement scores. These are reporting fields only; they do not trigger Salesforce workflows. The destination CRM may not have native equivalents for all Sales Flow analytics dimensions.

Sales Flow User accounts define who on the team is running outreach. We map source User accounts to Salesforce User records by email match. Seat assignments and role labels (Admin, Standard) from Sales Flow migrate as Salesforce User Role and Profile assignments. Any Sales Flow User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before Contact reassignment proceeds.

Sales Flow email engagement activity within Sequences maps to Salesforce Task records with ActivityDate set to the original Sales Flow timestamp, and EmailMessage records capturing the email body. The Task WhatId points to the Salesforce Campaign derived from the parent Sequence. We do not migrate the full email thread history if it exceeds the CSV export scope; the Workflow Reconstruction Summary flags this gap.

Sales Flow InMail and call engagement activity maps to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and outcome data migrate to custom Task fields (sft_call_duration__c, sft_call_disposition__c). Activity timeline ordering is preserved by setting ActivityDate to the original Sales Flow timestamp. LinkedIn InMail content migrates as Task Description if available in the CSV export.

Sales Flow Notes attached to Contacts or Sequences migrate to Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, or Account. Note body migrates as rich text. Attachments migrate as separate ContentDocument records linked to the Note.

Sales Flow Contacts may carry custom fields beyond the standard name, email, company, and LinkedIn URL. We map these to Salesforce custom fields on Lead and Contact using the __c suffix convention. Field type mapping follows Salesforce's type system: text properties become Text fields, numeric properties become Number fields, date properties become Date fields. Picklist-like values migrate to Picklist or Multi-Select Picklist depending on the source field cardinality.

Sales Flow Workflows define conditional branching logic for prospect responses and follow-up actions. The workflow builder configuration is not exposed via CSV or API and does not migrate as automation code. We produce a detailed Workflow Reconstruction Summary documenting every conditional rule, step order, timing delay, and channel routing so the customer's admin can manually reconstruct it in Salesforce Flow. This is the most common source of post-migration surprise; we surface it explicitly during scoping.