Migrate from Salesflare to Salesforce Sales Cloud

Salesflare Account records map directly to Salesforce Account. Standard fields (name, domain, industry, location) migrate 1:1. We use the Salesflare account domain as the dedupe key during import to prevent duplicate Accounts. Any custom properties on the Salesflare Account object pre-create as Salesforce custom fields (__c) before Account migration begins.

Salesflare Contact records map to Salesforce Contact with the AccountId Lookup resolved from the parent Salesflare Account. We preserve the Account-Contact junction explicitly as a Salesforce Contact linked to the corresponding AccountId. Email, phone, title, social links, and enrichment data (from Salesflare signature scraping) migrate as standard and custom Contact fields.

The Salesflare Account-Contact junction is a first-class relationship. We preserve primary versus secondary contact roles in a custom field sf_primary_contact__c on Contact. The junction migrates as a lookup insert sequence: Accounts first, then Contacts with AccountId populated, then the junction role metadata as a custom field on Contact.

Salesflare Opportunities map to Salesforce Opportunity. Deal value, stage name, expected close date, and owner assignment migrate directly. We resolve the Salesflare pipeline and stage labels against a pre-created Salesforce Record Type and Sales Process. If Salesflare stages do not map cleanly to Salesforce stage values, we create custom stage names in the destination org before migration.

Salesflare pipelines (up to 5 on Pro/Enterprise) map to Salesforce Opportunity Record Types. Each Record Type gets a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages transfer from Salesflare to StageProbability on Salesforce. Pipeline names and stage labels export as metadata and are re-created in Salesforce Setup before Opportunity import.

Salesflare activity history (logged calls, emails, meetings) migrates to Salesforce Task, Event, and EmailMessage. Calls map to Task with TaskSubtype=Call and CallDisposition preserved. Meetings map to Event with StartDateTime, EndDateTime, and Location. Emails map to EmailMessage records linked to Tasks. We use the Bulk API 2.0 for large activity volumes with parent-record lookup resolution (WhoId, WhatId) before insert.

Salesflare standalone Tasks (follow-up reminders, to-dos) migrate to Salesforce Task. Status, Priority, ActivityDate, and description transfer directly. Owner resolution happens via email lookup against the Salesforce User table. Any Salesflare task assigned to an unmapped owner goes to a reconciliation queue.

Salesflare email sequences (Growth single flow, Pro/Enterprise multi-step) do not migrate as automation code. Salesforce Sales Cloud does not include a native sales engagement cadence feature without the Sales Engagement add-on. We export a written inventory of every active sequence: step order, delay intervals, conditions, CRM actions, and a recommended Salesforce Flow rebuild or Sales Engagement cadence equivalent. The customer's admin rebuilds sequences post-migration.

Salesflare Users (team members with name, email, role, pipeline assignment) map to Salesforce User records by email match. We extract all distinct owners from Accounts, Contacts, Opportunities, and Activities and cross-reference against the Salesforce org User table. Missing Users go to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission sets map to Salesforce Profiles and Permission Sets.

Salesflare Tags are flat labels applied to Accounts, Contacts, and Opportunities. Tag names and their associations migrate as many-to-many join data. In Salesforce, tags on Accounts and Contacts become a custom multi-select picklist field sf_tags__c; tags on Opportunities become a separate Opportunity-level multi-select picklist. The customer chooses the field strategy during scoping.

Salesflare custom properties on Accounts, Contacts, and Opportunities pre-create as Salesforce custom fields before any data import. We export the full property map per object, match by label to Salesforce field types (text, number, date, picklist), and create fields via the Salesforce Metadata API in the destination org. Property dependencies and conditional display rules do not transfer.

Salesflare lead credits are a metered enrichment quota, not contact records. Credit balance, monthly allocations, and purchase history do not map to any Salesforce object. We export credit metadata as a separate configuration document for the customer's billing team to re-establish enrichment budgets in Salesforce via Data.com, Apollo, or another AppExchange enrichment tool.

File attachments on Salesflare Accounts, Contacts, or Opportunities store as URLs or binary blobs. We preserve attachment metadata (filename, linked object type, file size) and re-download accessible files. Files re-upload to Salesforce as ContentVersion records linked via ContentDocumentLink to the parent Account, Contact, or Opportunity. Files behind authentication or expired URLs are flagged for manual upload.