Migrate from Simplicity Enterprise CRM to Freshsales

Simplicity Contact records (name, email, phone, address, custom fields) map directly to Freshsales Contact. The email address is used as the dedupe key. We resolve any custom picklist values from Simplicity against Freshsales's picklist configuration during schema setup. If the Simplicity instance uses a loyalty or segment module, associated data links are preserved via custom fields on the Contact record.

Simplicity Company records map to Freshsales Account with a 1:1 field mapping for standard fields (name, domain, address). Company records are created before Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Contact insert. Custom fields on the Company object migrate to Freshsales Account custom fields pre-created during schema setup.

Simplicity Deal records map to Freshsales Deal with stage name translation from Simplicity pipeline stages to Freshsales deal stages. Deal value, expected close date, and owner assignment migrate directly. Custom fields on Deals are mapped to Freshsales Deal custom fields. Stage order and status logic require explicit mapping per the customer's specific Simplicity pipeline configuration.

Simplicity Activities (emails, calls, meetings, notes) are relational records linked to Contact and Company parents. We traverse and export the linked activity table explicitly rather than relying on a flat contact export. Activities are sequenced after Contact and Company imports so that parent-record lookups resolve correctly. Emails map to Freshsales Email records; calls map to Task with TaskSubtype=Call; meetings map to Event; notes map to Note records linked via ContentDocumentLink.

Simplicity Segmentation defines which contacts belong to which behavioural or demographic groups. Freshsales does not have a native segment object. We map segment membership to Freshsales Tags on Contact records, allowing sales reps to filter by tag for segment-based outreach. Customers choosing static list behavior use Freshsales Contact Lists as an alternative.

Simplicity Campaign records (campaign name, type, start/end dates, channel) map to Freshsales Campaign. Campaign-to-contact response associations in Simplicity do not have a direct Freshsales equivalent. We map campaign response records to tagged Task or Note records on the associated Contact to preserve the behavioural signal without leaving response data orphaned.

Simplicity Loyalty module stores program rules, reward tiers, and member point balances as distinct relational records. Freshsales has no native loyalty module. If the destination Freshsales instance includes custom objects, we archive loyalty data as a Loyalty_Program custom object with a lookup to Contact. If no custom object is available, we export loyalty data as a structured JSON attachment or CSV archive linked to the Contact record.

Simplicity's configurable data structure means nearly every object can have client-defined custom fields with custom picklist values. We map each custom field explicitly during schema discovery, pre-create the corresponding Freshsales custom field (Admin settings > Custom fields), and map picklist values individually. Custom field mapping is the primary scope driver for Simplicity-to-Freshsales migrations and requires per-instance scoping before any data moves.