Migrate from SalesSeek to Salesforce Sales Cloud

SalesSeek Organizations map directly to Salesforce Account. Standard fields including name, address, industry, website, and any custom fields migrate as-is. Organization ID is preserved in a custom text field salesseek_org_id__c for re-link auditing. Account is created before any Contact import so that the Account-Contact lookup is satisfied at the moment of insert.

SalesSeek People with an explicit Organization link map to Salesforce Contact under the corresponding Account (AccountId resolved via Organization ID). People with no Organization link (orphaned contacts) map to Salesforce Lead. We resolve the split during scoping using the salesseek_organization_id property, preserve the original People lifecycle stage or role label in a custom field salesseek_person_role__c on both Lead and Contact, and carry over email, phone, and title.

SalesSeek Deals map to Salesforce Opportunity. Deal value maps to Amount, deal stage maps to StageName via a lookup table, and expected close date maps to CloseDate. OwnerId resolves via email-matched User. The salesseek_deal_id__c custom field preserves the source identifier for reconciliation.

Each SalesSeek pipeline stage (configurable enumeration) maps to a Salesforce Opportunity StageName value. Probability percentages migrate as StageProbability, rounded to the nearest integer. We configure the destination Sales Process in Salesforce Sandbox to whitelist exactly the stages used in the migration before any Opportunity record inserts run.

SalesSeek's multiple named pipelines map to Salesforce Record Types on Opportunity. Each Record Type gets a corresponding Sales Process that scopes the relevant stage values per pipeline. Page Layouts per Record Type are configured in the destination org before migration so that the correct layout loads on each Opportunity record post-import.

SalesSeek custom fields on Organizations, People, and Deals require explicit type mapping. Text fields map to Salesforce Text fields; number fields map to Number; date fields map to Date; dropdown enumerations map to Picklist with all options explicitly created in Salesforce before data insert. We generate a custom field mapping spreadsheet during scoping that lists each field name, type, Salesforce equivalent, and picklist options for customer review before any migration begins.

SalesSeek Filters segment records within the platform. The API supports creating filters but not updating or deleting them, and orphaned Filters (those not linked to a Group) are periodically cleaned up. During scoping we export all active Filter definitions and recreate them as Salesforce List Views or Reports post-migration. We note that some Filters may already be absent from the source if scoping is delayed.

SalesSeek Groups are collections of records used for filtering and sharing. We export Group membership and recreate Groups as Salesforce Teams (for sharing-based Groups) or Public Groups (for visibility-based Groups) in the destination org. Group-to-Team strategy is decided with the customer during scoping.

File attachments associated with Organizations, People, or Deals are downloaded from SalesSeek and re-uploaded to Salesforce via the Chatter API or UI-API, linked to the target record via ContentDocumentLink. We preserve the linked record association, original filename, and content type. Attachments are migrated after the parent record has been confirmed in Salesforce.

SalesSeek Tags label records for categorization. We export tag names and reapply them as Salesforce Tags on the corresponding record. Tag strategy (standard tags vs. custom tag fields) is confirmed with the customer during scoping.

SalesSeek users referenced as record owners map to Salesforce User records by email address match. Owners without a matching Salesforce User are placed in a reconciliation queue for the customer's admin to provision before record import proceeds. Unresolved owner references default to a designated migration administrator.

SalesSeek Tasks migrate to Salesforce Task with Status, Priority, ActivityDate, and description preserved. Owner resolution maps the SalesSeek user to the Salesforce User by email. Tasks with a linked Deal associate to the corresponding Opportunity via WhatId after Opportunity insert is confirmed.

SalesSeek engagement activities (calls, emails, meetings) map to Salesforce equivalents: calls become Task with TaskSubtype=Call and CallDurationInSeconds; emails become EmailMessage records linked to a Task on the activity timeline; meetings become Event with StartDateTime and EndDateTime. The WhoId resolves to the migrated Contact or Lead; the WhatId resolves to the related Opportunity or Account. Activity timestamps are preserved for timeline ordering.

SalesSeek workflow automation rules including drip email sequences, lead scoring logic, and task triggers are not exposed through the SalesSeek REST API and cannot be exported programmatically. We document each active automation through a guided walkthrough with the customer and deliver a written reconstruction guide that maps each SalesSeek automation trigger, condition, and action to the nearest Salesforce Flow equivalent. Rebuilding in Flow is a manual effort handled by the customer's admin or a Salesforce partner.