Migrate from Salesforce Sales Cloud to Freshsales

Salesforce Account maps to Freshsales Company as the primary company record. Account Name maps to Company Name, Industry maps to Industry picklist, Annual Revenue maps to Annual Revenue, Website maps to Website, and Phone maps to Work Phone. Parent-Account hierarchies require flattening during migration since Freshsales Company does not natively support hierarchical parent-child structures; we flatten to a single-level parent relationship using a custom Company field if the source hierarchy depth exceeds one level.

Salesforce Contact maps to Freshsales Contact. Freshsales uses a unified contact model where each Contact record holds personal fields (Name, Email, Phone, Title) and a Company lookup linking to the destination Company. We import Contacts after Companies are committed so the Company lookup is satisfied at insert time. Salesforce's Account Contact Relation junction (many-to-many) is not a native Freshsales object; we assign each Contact to its primary Account and store any additional Account relationships in a custom multi-select picklist field hs_additional_accounts__c for audit.

Salesforce Lead maps directly to Freshsales Lead. Lead.Status maps to Freshsales Lead Status picklist via the pre-built translation table; LeadSource maps to Lead Source; Rating maps to Rating; Industry maps to Industry. Any custom Lead fields migrate to Freshsales custom Lead fields pre-created before migration. Converted Leads in Salesforce should have already produced Contact and Account records and are excluded from the Lead migration pass.

Salesforce Opportunity maps to Freshsales Deal. StageName maps to Deal Stage via the stage translation table (e.g., Prospecting maps to New, Qualification maps to Qualification, Closed Won maps to Won, Closed Lost maps to Lost); Amount maps to Deal Amount; CloseDate maps to Close Date; Probability maps to Deal Score or is stored as a custom field probability__c since Freshsales does not use a native probability model; OwnerId maps to Deal Owner by email resolution against Freshsales User records.

Salesforce Product2 maps to Freshsales Product catalog items. Product Name and Product Code migrate directly. Freshsales pricing works from a simple currency amount per product rather than Salesforce's Price Book Entry model; we extract the Standard Price Book price and load it as the product's default price during migration.

Salesforce Campaign maps to Freshsales Sales Campaign with Campaign Name, Status, Type, and Budget Amount carried over. Campaign Members (Contact and Lead associations) map to Freshsales Sales Campaign members by resolving each member's Salesforce ID to the equivalent Freshsales Contact or Lead ID via the email-based lookup table.

Salesforce Task maps to Freshsales Task with Subject, Status, Priority, Activity Date, and Description preserved. TaskSubtype is not a Freshsales field; we store the subtype value (Call, Email, Letter, etc.) in a custom field task_subtype__c for historical reference. Owner resolves by email match to the Freshsales User.

Salesforce Event maps to Freshsales Task with the activity type stored as event_meeting__c and Start DateTime and End DateTime preserved in custom datetime fields. Event attendees resolve to Freshsales Contact or Lead records via email match and are stored in a custom multi-select field event_attendees__c since Freshsales does not have a native EventRelation equivalent.

Salesforce Note migrates to Freshsales Note linked to the parent Contact, Lead, or Deal by resolving the Salesforce parent record ID to the equivalent Freshsales record via the lookup table built during migration. Note Title maps to Note Title, Body maps to Note Content.

Salesforce Case maps to Freshsales Case only if the destination Freshsales org is on the Ultimate tier, which includes the service desk. Standard and Pro tiers do not include Case management. We flag this during scoping; if the customer's Freshsales plan does not include Cases, we migrate Cases as Deals with a custom case_status__c picklist and deliver a written recommendation to either upgrade to Ultimate or use a dedicated service desk tool for post-migration case management.

Salesforce custom objects (with __c suffix) map to Freshsales custom objects that must be pre-created in the Freshsales schema before migration begins. We create the Freshsales custom object via the Freshsales Settings API, add all custom fields with matching types, and configure any lookup relationships to other Freshsales objects before the data migration pass. The custom object must be manually provisioned by the customer's Freshsales admin during the scoping phase because Freshsales does not expose a public API for programmatic custom object creation in all plan tiers.

Salesforce User records are the owners of all migrated objects and must exist in Freshsales before any data import begins. We extract distinct OwnerId values from every Salesforce object (Contact, Lead, Deal, Task, Event, Note) and match by email against the Freshsales User table. Any Salesforce Owner without a matching Freshsales User goes into a reconciliation queue; the customer provisions missing Users before the migration continues. This step is a prerequisite gate for every subsequent object pass.