Migrate from Lime CRM to Pipedrive

Lime CRM Company records map directly to Pipedrive Organizations. The organization's name, address fields, phone, website, and industry properties migrate as standard Organization fields. Any Lime CRM custom fields on the Company Limetype map to Pipedrive custom Organization fields created before migration. The Organization ID is created first so that the People import can reference it via the organization_id field.

Lime CRM Contact records map to Pipedrive People. Name, email address, phone number, job title, and owner assignment migrate as standard Person fields. Phone number formats are normalised during extraction to prevent leading-zero stripping that occurs in some CSV round-trip scenarios. Custom fields on the Lime CRM Contact Limetype map to Pipedrive custom Person fields.

Lime CRM Deal records map to Pipedrive Deals. Deal title, value (weighted by probability if applicable), stage, expected close date, and owner migrate directly. Lime CRM's custom deal pipelines and stages per industry variant map to Pipedrive pipeline stages. We resolve the mapping between each Lime CRM stage name and a Pipedrive stage ID during the configuration phase before any deal data is inserted.

Each Lime CRM deal pipeline (custom per customer) becomes a Pipedrive pipeline with corresponding stages. Stage probability percentages migrate as stage weights in Pipedrive. If the customer uses Lime CRM's industry variants, the pre-built stage terminology is mapped to Pipedrive stages that match the sales process language the team uses day-to-day.

Lime CRM Activity records (calls, meetings, tasks, notes) map to Pipedrive Activity records with the appropriate type designation (call, meeting, task, note). Activity timestamps are preserved via the add_time field. Assignments migrate by resolving the Lime CRM owner email to the Pipedrive user ID. The parent record link (person_id or org_id) is resolved at migration time using the lookup tables created during earlier phases.

Lime CRM exports email conversations as individual ConversationMessage files rather than threaded objects. We detect this at scoping, group message files by conversation ID and timestamp, reassemble the thread into chronological order, and inject it as a Pipedrive Activity note or as an email attachment linked to the Person record. This prevents the migration from delivering hundreds of disconnected individual files that the sales team cannot use as conversation history.

Lime CRM Tickets represent the helpdesk side of the platform. Pipedrive does not have a native Case or Ticket object at any tier; the Helpdesk integration is a separate product. We map Ticket records to Activity notes or Deal-linked activities with the ticket ID preserved in a custom field for traceability. If the customer requires full case management, we flag the Helpdesk product as a separate procurement decision.

Lime CRM's configurable Limetypes are unique per tenant and cannot be mapped to Pipedrive custom objects (Pipedrive does not expose a custom object API). We export the live schema definition from Lime CRM during discovery, analyse each custom field's data type and cardinality, and map it to a Pipedrive custom field on the closest standard object (Person, Organization, or Deal). Limetypes that represent a distinct entity type with multiple lookups to other Limetypes are flagged for restructuring as part of the migration inventory; these require a consultant or admin rebuild post-migration.

Lime CRM attachments download individually per record with no bulk export in the base tier. For migrations with 10,000+ files, we batch downloads by parent object, validate each file against the export manifest, and flag any truncated or missing files before the Pipedrive import begins. Files are linked to the parent Person, Organization, or Deal via Pipedrive's file attachment API. Files exceeding 25 MB are flagged and handled as separate transfers with a download-link handoff rather than a direct import.

Lime CRM tags on Contacts, Deals, and Tickets migrate as Pipedrive Person or Organization tags. Tags are stored as a flat per-record value during extraction and recreated as a tag taxonomy in Pipedrive. We note any tags that apply across multiple entity types and flag whether they should become Person tags, Organization tags, or both based on the customer's segmentation use case.

Lime CRM users and deal owners are resolved by email address against the Pipedrive destination User table. The destination Pipedrive account must have users provisioned before migration begins. Any Lime CRM owner without a matching Pipedrive user goes to a reconciliation queue for the customer's admin to resolve before record import proceeds.