Migrate your Salesflare data

Salesflare's Account object maps directly to Company/Organization. Standard fields include name, domain, industry, location, and custom fields. We migrate Accounts 1:1 via API export or CSV from the three-dot menu. Domain-based auto-enrichment triggers on import.

Contacts are linked to Accounts and include name, email, phone, title, social links, and enrichment data from email signature scraping. We preserve the Account-Contact relationship and any manually added or auto-enriched fields. Custom properties migrate as flat fields.

Opportunities link to Accounts and represent deal records with value, stage, and expected close date. Pipeline and stage names vary by account configuration. We map opportunity stages to destination pipeline stages by name matching, with manual review for non-standard naming.

Pipelines define the deal stages available to Opportunities. Pipeline names and stage labels are account-specific. We export pipeline definitions as metadata alongside opportunity records and map them to destination pipelines by sequence order when names do not match exactly.

Activities include logged calls, emails, and meetings. The API exposes activity history, but bulk export of full activity timelines requires pagination. We preserve activity type, date, outcome, and linked contact or opportunity. Notes and rich-text content migrate as-is.

Email sequences are configured at the workflow level. Growth tier limits to one sequence flow; Pro and Enterprise support multi-step workflows. Sequence steps, delays, and conditions migrate as workflow templates. Existing enrolled contacts require re-enrollment logic in the destination.

Users represent team members with name, email, role, and pipeline assignment. We migrate user records and assign them as Opportunity owners. Role and permission sets map to destination profiles; Enterprise-tier granular permissions may need manual post-migration review.

Tags are flat labels applied to Accounts, Contacts, and Opportunities. Tag names and associations migrate as a many-to-many join table. No hierarchy or inheritance — each tag assignment is an independent record.

Custom properties can be added to Accounts, Contacts, and Opportunities. Schema varies per account. We export the full property map per object and map property names to destination custom fields by label or API name. Hidden or read-only properties are flagged.

Lead credits are a metered resource on Growth/Pro plans, not contact records. Credit balance and usage history do not transfer as contacts. If the destination uses a similar credit model, we document the allocation separately as billing metadata.

Custom dashboards are report configurations stored as UI state, not data records. We do not migrate dashboard definitions. We export the underlying opportunity and activity data so dashboards can be rebuilt in the destination.

File attachments on Accounts, Contacts, or Opportunities are stored as URLs or binary blobs. We preserve attachment metadata (filename, linked object, size) and re-download files where accessible. Large files or inaccessible URLs are flagged for manual re-upload.

The Account-Contact junction is a first-class relationship in Salesflare. We preserve which Contacts belong to which Account and flag primary vs. secondary contact roles. This junction migrates as a linked record set.