Migrate from Lime CRM to Freshsales

Lime CRM Company records map to Freshsales Account. The company domain and address fields map to Website and Billing Address fields. We use domain as the dedupe key and validate that no existing Freshsales Account with the same domain exists before inserting. Account is created before any Contact import so that the Account lookup is satisfied at Contact insert time.

Lime CRM Contact maps to Freshsales Contact with phone number normalisation applied before import to prevent leading-zero stripping on international numbers. The Contact-Company link maps to Freshsales AccountId lookup. Email address is used as the unique identifier for duplicate detection. Any custom Lime CRM fields on Contact are mapped to Freshsales custom fields if they exist in the target schema, or held in a catch-all custom text field with the original field name preserved in the label.

Lime CRM Deals map to Freshsales Deals with dealstage mapped to the Freshsales pipeline stage. Lime CRM's custom deal fields (industry-specific stages, probability, closed-won reasons) map to Freshsales custom fields that we create during schema design. Owner assignment uses email-based user matching.

Lime CRM Activities split across Freshsales Task (for calls, tasks, and notes) and Event (for scheduled meetings). Activity timestamps preserve chronological ordering. Meeting attendees map to Freshsales Event relations. Notes from Lime CRM become Freshsales Notes attached to the parent Contact, Account, or Deal via the Notes module.

Lime CRM Tickets map to Freshsales Cases. Ticket status and priority map to Case Status and Priority. Ticket conversations reassembled from individual message files are injected into the Case's conversation view. Assignee maps via email-based owner matching. If the customer uses Lime CRM's helpdesk orientation, we confirm that Service Cloud equivalent features are available on the target Freshsales tier before mapping.

Lime CRM's configurable Limetypes have no direct Freshsales equivalent because the schema is unique per tenant. We export the live Limetype field definitions during discovery, design Freshsales custom objects with equivalent custom fields, configure lookup relationships to Accounts and Contacts, and then import the data. Each custom Limetype becomes its own Freshsales custom object. We treat this as a separate schema workstream scoped and priced independently.

Lime CRM tags are a flat list per record across Contacts, Deals, and Tickets. Freshsales does not have a native tag taxonomy equivalent. We export tag values as a normalised list and inject them into Freshsales multi-select picklist fields. If the tag taxonomy is large (over 100 distinct values), we scope this as a configuration step requiring the customer to define which fields become multi-select picklists versus plain text.

Lime CRM attachments are individual files per record exported from a per-record download path. We batch download with integrity checks, rename files to preserve the parent-relationship manifest, and upload to Freshsales using the Files module. Files are linked to the parent Contact, Account, Deal, or Case via the Attachments relationship. Files exceeding 25 MB are flagged before import and handled as oversized attachments separately.

Lime CRM Users and Deal Owners resolve to Freshsales Users by email match. We validate that destination user accounts exist in Freshsales before assigning ownership. Any Lime CRM Owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. The admin must use the login email address as the import value, not the display name.

Lime CRM Products map to Freshsales Products. Product name, code, and price migrate directly. If the customer uses Products on Deals, we also create corresponding Price Book entries in Freshsales before Deal import to satisfy the price book lookup on any deal line items.