Migrate from Sharpspring to Salesforce Sales Cloud

Sharpspring Contact maps to Salesforce Contact. Sharpspring contacts without a primary company land as Salesforce Contacts attached to a default 'Unassigned Accounts' record. Contacts with a primary company resolve via AccountId — the Account must exist before the Contact is created.

Sharpspring contacts with lifecycle stages earlier than 'Customer' route to Salesforce Lead based on the final lifecycle value. Sharpspring does not track historical stage transitions — the final value determines routing. The original lifecycle value is preserved in Lifecycle_Stage__c custom field on the Lead record.

Sharpspring contacts ending at 'Customer' or 'Evangelist' stage are migrated as Salesforce Contacts, not Leads. This routing rule ensures that paying customers and advocates land in the correct Salesforce object for account-based workflows, opportunity linking, and service-case management. The original Sharpspring lifecycle_stage value is written to Lifecycle_Stage__c on the Salesforce Contact for historical reporting continuity and segmentation. If Sharpspring exposed stage-transition history via API, we preserve the full progression in a custom datetime audit field.

Sharpspring Company maps to Salesforce Account. Parent-child company hierarchies in Sharpspring map via Salesforce ParentId. Sharpspring contacts can belong to multiple companies (N:N) — we migrate one primary company per contact as AccountId and surface the rest as AccountContactRelation records.

Sharpspring Deal maps to Salesforce Opportunity with a direct field-to-field translation. Each Sharpspring deal carries its associated pipeline, stage name, monetary amount, expected close date, and owner assignment. The pipeline-to-RecordType mapping is pre-resolved before Opportunity records are inserted so that the RecordTypeId foreign key is valid at load time. Deals without a linked Account are attached to a placeholder 'Unassigned Account' to satisfy Salesforce's required AccountId relationship on Opportunities.

Sharpspring Pipeline becomes a Salesforce Sales Process keyed by RecordType. Each Sharpspring pipeline requires its own Salesforce Record Type so Opportunity Stage pick-list values are scoped correctly per pipeline. We deliver a record-type setup plan as part of the migration spec.

Sharpspring pipeline stages map to Salesforce Opportunity Stage values on a per-Record-Type basis. Each Sharpspring stage name is matched to a corresponding Salesforce StageName value, with probability percentages and forecast categories reapplied according to your Salesforce configuration. Stage-entry timestamps are preserved as custom datetime fields on the Opportunity so reporting tools can reconstruct the original deal timeline even though Salesforce only tracks the current stage by default.

Salesforce has no native lifecycle_stage equivalent. The Sharpspring lifecycle_stage value migrates as a custom pick-list field (Lifecycle_Stage__c) on both Lead and Contact. SharpSpring's lifecycle history (stage-transition timestamps) is preserved in a custom datetime audit field if Sharpspring exposes this in the API.

Sharpspring's behavioral and demographic lead scoring migrates as a custom Number field (Lead_Score__c) on both Lead and Contact objects. The scoring weights and rules themselves are not exportable — we provide a reference export of the scoring configuration for your Salesforce admin to rebuild in Flow or a third-party scoring app.

Sharpspring calls and emails map to Salesforce Tasks with Type='Email' or Type='Call'. Meetings map to Salesforce Events with original start and end times preserved. Notes map to Salesforce Notes (the modern object, not legacy Note). All original timestamps, owners, and parent-record links are preserved.

Sharpspring tagging has no direct Salesforce equivalent. Tags migrate as a custom multi-select text field (Tags__c) on Contact and Lead objects. If a contact has more tags than the field character limit allows, the overflow is stored in a secondary custom field.

Sharpspring form submissions are converted to Salesforce Note records attached to the corresponding Contact or Lead. Each Note captures the form name as the title, the submission timestamp as a header line, and a formatted list of field-name/field-value pairs representing all data submitted through the form. This preserves a complete audit trail of the prospect's or customer's form-based interactions at the time of submission, including any UTM parameters or referral source data that Sharpspring stored with the submission record.

Sharpspring custom objects map 1:1 to Salesforce custom objects. Custom-object associations that use Sharpspring's N:N relationship model require Salesforce junction objects — we surface this in the migration plan and create the junction object schema as part of the Salesforce setup step.

Sharpspring VisitorID tracks anonymous website visitors and associates them with known contacts after form submission. The VisitorID identifier migrates as a custom text field (VisitorID__c). Salesforce does not have a native anonymous visitor tracking equivalent — this data is preserved for reference only.