Migrate from Lime CRM to Salesforce Sales Cloud

Lime CRM Company records map to Salesforce Account. The company name, address fields, industry classification, and any custom fields migrate as typed fields (text, picklist, number). The company name is the dedupe key during import. Account is inserted before Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. Lime CRM's industry-specific variants may include sector-specific custom fields that we map to Salesforce custom fields on Account.

Lime CRM Contact records map to Salesforce Contact with a direct 1:1 mapping for standard fields (name, email, phone, title). Phone number formats are normalized during transform to prevent leading-zero stripping that commonly occurs when moving between regional systems. The AccountId on Contact is resolved by matching the Contact's parent Company in Lime CRM to the Account record inserted in the prior phase. Any custom Contact fields defined as Limetype properties map to Salesforce custom Contact fields.

Lime CRM Deal records map to Salesforce Opportunity. The deal value, stage name, expected close date, owner, and custom properties migrate. Lime CRM allows custom deal pipelines and stages per industry; we map these to Salesforce Record Types and Sales Processes with stage probability percentages transferred from Lime CRM. Closed-Lost and Closed-Won reason custom properties become Salesforce Loss Reason and Win Reason fields. Deals are inserted after Accounts and Contacts to satisfy the AccountId and OwnerId lookups.

Each Lime CRM deal pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values. We capture the stage names and probability percentages from Lime CRM during schema extraction and replicate them in Salesforce. Stage ordering is preserved per pipeline. If the customer uses multiple deal pipelines in Lime CRM, each maps to a separate Salesforce Record Type with its own Page Layout.

Lime CRM logged calls map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any notes transfer to custom Task fields. The WhoId on the Task points to the resolved Contact; the WhatId points to the related Opportunity or Account. Activity ordering is preserved by setting ActivityDate to the original Lime CRM timestamp so that the Salesforce activity timeline reflects the historical sequence.

Lime CRM logged meetings map to Salesforce Event records. Start time, end time, location, and meeting title preserve directly. Attendees on the Lime CRM meeting link to Salesforce EventRelation records pointing at the resolved Contacts and Users. If the Lime CRM meeting record has no attendees, the Event is created as a private event on the Owner without EventRelation records.

Lime CRM standalone task records (not linked to calls or emails) map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving the Lime CRM owner reference to the Salesforce OwnerId via the User mapping. Completed tasks retain their completed timestamp from Lime CRM as the Task ActivityDate.

Lime CRM Ticket records map to Salesforce Case if the destination Salesforce org includes Service Cloud or if Cases are enabled in the Sales Cloud org. Ticket status maps to Case Status; ticket priority maps to Case Priority; assignee maps to Case Owner. Ticket conversations (threaded email messages) migrate as EmailMessage records linked to the Case. If Service Cloud is not in scope, we document the Case creation approach and the customer's admin enables Cases before migration.

Lime CRM exports email conversations as individual ConversationMessage files rather than threaded records. We detect this at scoping, reassemble threads by conversation ID and timestamp, and inject them into Salesforce as unified EmailMessage records linked to the parent Contact (WhoId) and related Account or Opportunity (WhatId). This transformation step is required before any email data is loaded; without it the migration arrives as hundreds of disconnected message files.

Lime CRM file attachments associated with Contacts, Deals, Companies, and Tickets migrate to Salesforce ContentDocument records linked via ContentDocumentLink to the parent record. We batch downloads (individually per Lime CRM record since no bulk export is available on base tiers), rename files to preserve the parent relationship, and validate against the export manifest before import. Any files exceeding 25 MB are flagged before upload to avoid Salesforce file size limits.

Lime CRM's configurable Limetypes map to Salesforce custom objects. Every Lime CRM customer has a unique Limetype schema, so this is the most variable mapping in the migration. We extract the live Limetype definitions during discovery, document each custom field with its data type, and provision matching Salesforce custom objects with __c API names before any Limetype data is imported. Lookup relationships between Limetypes are replicated as Salesforce lookup fields, requiring parent records to insert before child records.

Lime CRM tags on Contacts, Deals, and Tickets migrate to Salesforce as either a multi-select picklist field on the standard object or as Salesforce Topics with TopicAssignment records. Tags used for segmentation and filtering migrate as multi-select picklists; tags used for content or deal classification migrate as Topics. The customer chooses the tag strategy during scoping, and we apply it uniformly across all migrated records.

Lime CRM user records map to Salesforce User by email address match. We extract every distinct user referenced on Contacts, Companies, Deals, Activities, and Tickets, then match by email against the destination Salesforce org's User table. Any Lime CRM user without a matching Salesforce User is held in an Owner reconciliation queue for the customer's admin to provision before record import resumes. Inactive Lime CRM users map to inactive Salesforce Users with the original Lime CRM user ID preserved in a custom field.

Lime CRM document templates linked to Deals and Contacts are exported as document blobs with metadata. The document content migrates to Salesforce as ContentDocument records attached via ContentDocumentLink to the related Account, Contact, or Opportunity. Template auto-fill field mappings are captured during discovery and documented for the customer's admin to reconfigure in Salesforce's document generation tool (Documents, Salesforce Files, or a connected e-signature app).