Migrate from SalesSeek to Freshsales

SalesSeek Organizations map directly to Freshsales Accounts. The organization name, address fields, industry classification, and any custom properties migrate to Freshsales Account fields. The original SalesSeek organization ID is preserved in a custom field salesseek_id__c for re-linking to People records that reference it. We create all Accounts before any People import so that the Account lookup relationship is satisfied at the moment of Contact or Lead insert.

SalesSeek People may represent both unqualified prospects and qualified customers depending on lifecycle stage or status field values. We define the split rule during scoping based on the customer's SalesSeek data: typically, People with a status indicating early-stage (e.g., New, Prospect, Unqualified) map to Freshsales Lead, while People with a status indicating engagement or customer (e.g., Active, Customer, Won) map to Freshsales Contact attached to an Account. The original SalesSeek status and lifecycle values are preserved in custom fields on both Lead and Contact for audit and reporting continuity.

SalesSeek Deals map to Freshsales Deals with the deal name, monetary value, stage, probability, and expected close date preserved. The linked Organization (Account) and Person (Contact or Lead) associations migrate as Freshsales Deal relationships. Deal custom fields migrate to Freshsales custom Deal fields with equivalent types. We resolve parent Account and Contact lookups before Deal insert to avoid orphaning.

SalesSeek pipeline stages are configurable enumerations with label, sequence order, and probability percentage. We export each pipeline's stage definitions and recreate them in Freshsales using the Deal stage editor. Stage probability percentages round to Freshsales-acceptable values. Stage renaming or reordering post-migration requires manual review in Freshsales admin settings.

SalesSeek supports multiple pipeline visualizations. Each SalesSeek pipeline becomes a Freshsales Deal pipeline. We export pipeline names, stage order, and any pipeline-specific configuration and recreate them in Freshsales before Deals migrate. Freshsales Growth tier supports multiple pipelines; the Free tier supports a single pipeline.

SalesSeek Tasks (to-do items with due dates, status, and owner assignment) map to Freshsales Tasks. Task subject, due date, status (open/closed), priority, and owner assignment migrate directly. Completed tasks include the completion timestamp. The owner mapping resolves SalesSeek hubspot_owner_id references to Freshsales User IDs via email match.

SalesSeek custom fields on Organizations, People, and Deals (text, number, date, dropdown types) require explicit mapping to Freshsales custom field types. Text fields map to Freshsales Text or Text Area; number fields map to Number; date fields map to Date; dropdown fields map to Picklist with enumerated options explicitly matched to Freshsales picklist values. We generate a custom field mapping spreadsheet during scoping listing each field name, type, and options for customer review before migration begins.

SalesSeek Filters segment records and are associated with Groups. The SalesSeek API supports creating filters but not updating or deleting them, and orphaned filters are periodically cleaned up by the system. We export all active filter definitions (field conditions, operators, values) during scoping. These are recreated as Freshsales Saved Views by the customer's admin post-migration using the export as a recreation guide. We flag any filters that were orphaned before scoping as potentially missing from the export.

SalesSeek Groups are collections of records used for filtering and sharing. We export Group membership (which People and Organizations belong to each Group). In Freshsales, Groups map to Teams (for access control) or Lists (for segmentation). The customer chooses the mapping strategy during scoping.

SalesSeek engagement activities (calls, emails, meetings, tasks) are exported with type, date, associated contacts, and notes. Freshsales stores activities on the timeline of the related Contact, Lead, Account, or Deal. Activity type mapping is preserved: calls become Freshsales call activities, meetings become meeting activities, and standalone notes become note records. The activity schema differs between platforms so we document the mapping per field for customer review.

File attachments associated with Organizations, People, or Deals are downloaded from SalesSeek and re-uploaded to Freshsales with the linked record association preserved. Freshsales attachments link to the parent Contact, Lead, Account, or Deal. We validate file size limits against Freshsales attachment constraints before migration.

SalesSeek Tags label records for categorization. We export tag names and reapply them as Freshsales Tags on the corresponding Contact, Lead, Account, or Deal. Tag-based segmentation from SalesSeek maps to Freshsales Lists or Tags depending on the customer's intended use case.

SalesSeek Users who own records must map to Freshsales Users. We resolve owners by email match against the destination Freshsales User table. Any SalesSeek User without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Unassigned records default to a migration owner during the initial load.