Migrate from Floww.ai to Salesforce Sales Cloud

Floww.ai Contact records migrate to Salesforce Contact with standard fields (Name, Email, Phone, Title) preserved. We use email as the external ID dedupe key during import. Any custom Contact properties defined in Floww.ai are mapped field-by-field to Salesforce custom fields on Contact, with type conversion applied (e.g., multi-select from Floww.ai maps to a multi-select picklist or a junction object depending on cardinality). Custom fields are pre-created in the destination org before migration begins.

Floww.ai Lead records migrate to Salesforce Lead with all standard and custom fields preserved. We use email as the external ID dedupe key. The Floww.ai lead categorization properties map to Salesforce Lead Status and any custom picklist fields representing lead source, industry segment, or qualification tier. Owner matching is resolved by email against Salesforce User records before import.

Floww.ai Company records map to Salesforce Account. The company name becomes Account Name; the domain or website becomes the Website field. We use Account Name and Website as compound dedupe keys to prevent duplicate Accounts from multiple Floww.ai exports. Account is created before Contact import so the AccountId lookup is satisfied at the moment of Contact insert.

Floww.ai Deal records migrate to Salesforce Opportunity. Deal value maps to Amount, expected close date maps to CloseDate, owner maps to OwnerId, and the linked pipeline and stage assignment maps to a Salesforce Record Type and Sales Process combination we configure before migration. Closed-Won and Closed-Lost reasons from Floww.ai become custom Opportunity fields for loss and win analysis.

Floww.ai pipelines map to Salesforce Record Types on Opportunity. Each pipeline's stage set becomes a Salesforce Sales Process that whitelists only the relevant stage values for that pipeline. We extract the live pipeline definitions from Floww.ai during scoping, including stage names, stage order, and any probability values, and configure the equivalent Salesforce schema in a Sandbox org before deploying to production.

Stage definitions from each Floww.ai pipeline are extracted and mapped to Salesforce Opportunity Stage values within the corresponding Sales Process. Stage probability percentages migrate to StageProbability, rounded to the nearest integer. We flag any stages that do not map cleanly to standard Salesforce stages and document custom stage values required.

Floww.ai Custom Object records migrate to Salesforce Custom Objects (with __c API name suffix). We require a schema map from the customer covering all Custom Object definitions, their custom properties, and their relationship cardinalities before writing to the destination. This mapping step cannot proceed without the schema map because the destination custom object API names and field definitions must be pre-created in Salesforce before data import.

Floww.ai Custom Objects use one-to-many and many-to-many relationships that do not map directly to Salesforce's standard relationship model. For many-to-many relationships, we construct a junction object in Salesforce with two master-detail or lookup fields pointing to the related custom objects. For one-to-many relationships, we configure a standard lookup or master-detail from the child to the parent custom object. The customer's schema map drives the junction object design during the configuration step.

Floww.ai call activity records migrate to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any recording URL stored in Floww.ai are mapped to custom Task fields. Activity timestamps are preserved by setting ActivityDate to the original Floww.ai activity timestamp. Calls are written after Contact and Lead records are confirmed in Salesforce so that the WhoId reference is satisfied.

Floww.ai email activity records migrate to Salesforce EmailMessage (the email content) linked to a Task record (the activity timeline entry). The WhoId on Task points to the migrated Contact or Lead; the WhatId points to the related Opportunity or Account. Email body content migrates as plain text or HTML depending on the destination org's EmailMessage configuration.

Floww.ai meeting activity records migrate to Salesforce Event. StartDateTime, EndDateTime, Subject, and Location are preserved directly. Attendee records from Floww.ai map to EventRelation records linked to the corresponding Contact, Lead, or User in Salesforce.

Floww.ai notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Contact, Lead, Account, or Opportunity). Note body migrates as rich text. File attachments embedded in Floww.ai notes migrate as separate ContentDocument records and linked to the same parent record.

Floww.ai task records migrate to Salesforce Task with Status, Priority, Subject, ActivityDate, and OwnerId preserved. Task assignment migrates by resolving the Floww.ai owner reference to Salesforce OwnerId via the User email matching step.

Floww.ai tags and segments applied to Contacts, Leads, and Deals migrate to a Salesforce custom field. If the tag count is small (under 20 distinct tags), we use a multi-select picklist on the relevant object. If tags are numerous or used across multiple object types, we create a custom Tags__c junction object with lookups to Contact, Lead, and Opportunity, allowing flexible tag assignment at scale.

Floww.ai user and owner references on Contact, Lead, Deal, and Activity records are resolved by matching email addresses against Salesforce User records. Any Floww.ai owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references must be resolved before Deal and Activity imports proceed.

Floww.ai file attachments and call recordings are flagged for separate file migration handling. Attachments linked to Contacts, Deals, and Activities are retrieved from the platform's storage layer where the customer grants access, then uploaded to Salesforce as ContentVersion records linked to the relevant parent record via ContentDocumentLink. Call recordings are optional migration targets and are included only upon explicit customer confirmation.