Migrate from Sharpspring to Freshsales

SharpSpring contacts map 1:1 to Freshsales contacts. Email is the primary deduplication key. Contacts without an associated company in SharpSpring land in Freshsales as standalone contacts. Primary company assignment uses SharpSpring's primary company flag or most-recently-modified rule. If a contact has multiple associated companies, we select the most recently updated company as the primary account to maintain data consistency.

SharpSpring companies map to Freshsales accounts. Account Name, domain, industry, employee count, and annual revenue transfer directly. Parent-child company hierarchies in SharpSpring map to Freshsales Parent Account relationships, requiring topological ordering during migration. We also preserve the original company identifiers as a custom field to avoid confusion if duplicate company names exist across different SharpSpring accounts.

SharpSpring leads map to Freshsales leads. Both platforms treat leads as pre-contact records with status fields. SharpSpring lead status values map to Freshsales lead status via value mapping. Unconverted SharpSpring leads land as Freshsales leads; converted leads migrate as contacts.

SharpSpring deals map to Freshsales deals (Freshsales uses 'Deal' as the object name, distinct from Salesforce's 'Opportunity'). Deal name, amount, expected close date, owner, and stage all transfer. Pipeline-stage mapping requires value-by-value mapping since stage names differ between platforms. We also record the original SharpSpring deal ID in a custom field to support future cross-referencing and to aid in reconciling any duplicate deal names during the migration.

SharpSpring tasks map to Freshsales tasks. Task subject, due date, status, priority, and owner transfer. Tasks linked to specific contacts, companies, or deals preserve their parent record associations via Freshsales foreign key lookups. If a task references a contact that does not yet exist in Freshsales, we create a placeholder contact record to maintain the association until the full dataset is loaded.

SharpSpring email logs and sent emails map to Freshsales Sales Activities of type 'Email'. The original sent date, recipient, subject, and body text transfer. HTML formatting is preserved as plain text since Freshsales activities store plain text content. We also capture any inline attachments as linked file records in Freshsales, ensuring that important email assets are retained with the activity timeline.

SharpSpring notes map to Freshsales notes. Note body content, create date, and owner transfer. Notes attached to specific records maintain their parent associations. Rich-text notes are converted to plain text format. If a note contains any embedded images or files, we store them as attachments linked to the note record to preserve the full context of the original content.

SharpSpring form submissions are stored as engagement data on contacts. These migrate as Sales Activities with type 'Form' in Freshsales, capturing form name, submission date, and fields submitted. Source page URL transfers as a custom field. We also map each form field to the corresponding Freshsales custom field if one exists, otherwise we store the raw field data as a JSON blob for future reference.

SharpSpring behavioral and demographic lead scores are stored as contact properties. Since Freshsales calculates scoring through Freddy AI rather than storing static values, SharpSpring scores migrate to a custom number field (SharpSpring_Score__c) for reference and historical continuity. We also preserve the original scoring model version and any related thresholds as additional custom fields to help you replicate similar segmentation logic in Freshsales after migration.

SharpSpring VisitorID captures anonymous visitor data including company identification and page visits. Freshsales has no native visitor tracking equivalent. VisitorID data and tracked company associations are preserved as custom text fields (VisitorID_Source__c) for reference but do not create new records.

SharpSpring custom fields on contacts, companies, leads, and deals map to Freshsales custom fields. Field types (text, number, date, picklist, checkbox) are matched to Freshsales equivalents. Picklist values require value-by-value mapping if the options differ between platforms. We also validate that any default values set in SharpSpring are applied correctly in Freshsales and flag any fields that exceed Freshsales' maximum length restrictions for review.

SharpSpring file attachments on records are downloaded and re-uploaded to Freshsales as attachments linked to the corresponding contact, account, lead, or deal. File size limits apply (Freshsales default 25MB per file). We also verify the file checksum before upload to ensure data integrity, and we retain a mapping of original SharpSpring file IDs to Freshsales attachment IDs for audit trail purposes.