Migrate from SalezShark to Freshsales

SalezShark Lead records map directly to Freshsales Lead. Auto-assignment rules and conversion scoring from SalezShark do not transfer — assignment rules are documented as a written specification for the admin to configure in Freshsales Lead assignment settings post-migration. Any lead scoring values stored in custom fields carry over as numeric custom fields on the Freshsales Lead object. The conversion mapping during migration (Lead-to-Contact-and-Account) is handled as a post-import step by the customer's admin, or we provide a mapping spreadsheet specifying the target Contact and Account for each converted Lead.

SalezShark Contact records map to Freshsales Contact with a direct field-to-field mapping on standard fields (first_name, last_name, email, phone, address). SalezShark's built-in enrichment fields (company email format, employee count, revenue range) export as text or numeric custom fields but lose their verified/enrichment semantics — we flag these as candidates for Freddy AI enrichment post-migration. Contacts are imported after Accounts so that the AccountId lookup resolves at import time.

SalezShark Account records map directly to Freshsales Account. The Account Name field is the primary dedupe key during import. Any custom fields on the SalezShark Account object (industry classification, employee range, revenue tier) are pre-created in Freshsales as matching custom fields before the account import batch runs. Accounts are the first object imported to satisfy the AccountId foreign key required by Contact and Deal imports.

SalezShark Opportunity records map to Freshsales Deal. The pipeline stages from SalezShark are exported as a configuration record and re-created in Freshsales as pipeline stages before deal import begins. Deal value, close date, owner assignment, and stage status transfer directly. Any custom fields on Opportunity are pre-created in Freshsales; picklist values are mapped individually to avoid silent import failures caused by unlisted stage values.

SalezShark Pipelines and their configured stages are exported as a configuration specification. We create matching Freshsales Pipelines with the same stage names and ordering before Deal import. Probability percentages are set per stage in Freshsales to match the source values. If SalezShark uses multiple pipelines for different business lines, each becomes a separate Freshsales Pipeline with its own stage set.

SalezShark custom field definitions (field names, data types, picklist values) are extracted during scoping and pre-created in Freshsales as matching custom fields before any record import. Field types are mapped: SalezShark text fields map to Freshsales text fields, picklists map to dropdowns, numeric fields map to number fields. Any picklist values present in SalezShark but absent in Freshsales are created before import to avoid validation errors blocking record inserts.

SalezShark Tasks map to Freshsales Tasks. Task status, priority, due date, owner, and associated record reference migrate directly. Tasks are imported last among standard objects to ensure the parent Contact, Account, and Deal records already exist in Freshsales with their destination IDs resolved. Freshsales API rate limits (per-hour cap by plan tier) determine the chunk size for task batches.

SalezShark Professional-tier Workflow Automations and Custom Event Triggers cannot be migrated as executable code. We export the full automation configuration — trigger conditions, filter logic, action sequences, and downstream field updates — as a written specification document delivered alongside the migrated records. The customer's Freshsales admin uses this document to rebuild equivalent workflows in Freshsales Admin Settings > Workflows. Custom Event Triggers are documented as API webhook configurations for the admin to set up in Freshsales' webhooks section.

SalezShark Documents attached to records are exported as file metadata (file name, type, associated record) and re-associated with the corresponding Freshsales Contact, Account, or Deal after import. The actual file content is re-uploaded manually by the customer or via Freshsales' file attachment API, linked to the target record by ID resolved during migration.

SalezShark User records map to Freshsales User via email address match. User provisioning in Freshsales is a manual step the customer's admin performs before migration — we cannot create Freshsales users programmatically. We provide a user mapping table listing every SalezShark owner email and the corresponding Freshsales User ID, which the admin populates before we run the record import. Any SalezShark owner without a Freshsales user creates orphaned records that require post-migration owner reassignment.