Migrate from Lime Go to Pipedrive

Lime Go Customers map directly to Pipedrive Organizations with a 1:1 relationship. We preserve all standard fields (name, address, phone, website), custom fields, tags, and the owner assignment. The Customer's unique identifier is preserved in a custom field lime_customer_id__c for audit and cross-reference. GDPR consent flags and anonymisation status migrate as custom fields on the Organization because Pipedrive stores consent at the Person level by default.

Lime Go Contacts map to Pipedrive Persons with full field fidelity including name, email, phone, title, and custom properties. We link each Person to its parent Organization via the Person-Organization relationship resolved at migration time. GDPR consent flags (granted, withdrawn, timestamps, consent type) migrate as custom fields on the Person record to preserve the compliance timeline in Pipedrive.

Lime Go's built-in Nordic company database of 3.7 million records is a read-only enrichment layer licensed to Lime Go, not user-owned CRM data. It does not migrate as standard Organization records. We extract these as enrichment context records and flag them separately during scoping so customers understand that prospecting enrichment data persists only if the destination CRM has its own enrichment provider (Pipedrive's AI-powered data enrichment or a third-party enrichment tool) or they retain Lime Go for that purpose.

Lime Go's pipeline configuration—stage names, stage order, probability percentages, and visual layout—transfers to Pipedrive Pipeline as a configuration step before Deal migration. Each Lime Go stage maps to a Pipedrive stage within the same Pipeline, preserving probability settings. Multiple Lime Go pipelines map to multiple Pipedrive pipelines for multi-line-of-business accounts.

Lime Go Deals map to Pipedrive Deals with a 1:1 relationship. We preserve deal title, value, expected close date, owner, custom fields, stage assignment, and pipeline reference. Stage transitions from Lime Go (open, won, lost with reasons) transfer as Deal activities for pipeline reporting. The Lime Go deal identifier is preserved in lime_deal_id__c on the Pipedrive Deal.

Lime Go Activities (calls, emails, meetings) map to Pipedrive Activities with type, subject, body, timestamp, duration, and linked Organization or Person preserved. Activity history sequences into Pipedrive's timeline view under the linked record. Email subject lines become Activity subjects; call durations and dispositions migrate to custom Activity fields.

Lime Go Tasks migrate to Pipedrive Tasks with assignee, due date, status, priority, and subject preserved. Task ownership resolves by matching Lime Go owner email to Pipedrive User email at migration time. Recurring tasks map as repeating Pipedrive Tasks with their recurrence pattern preserved. Batch operation limitations in Lime Go do not affect how we structure migrated Task records.

Lime Go Reminders attach to Contacts, Customers, or Deals and map to Pipedrive Tasks or Activities depending on the reminder type and linked record. We preserve the reminder timestamp, notification context, and linked Organization or Person reference. Reminders without a clear Pipedrive equivalent become Tasks with a custom type field lime_reminder_type__c.

Lime Go History Notes migrate to Pipedrive Notes linked to the parent Organization, Person, or Deal via ContentDocumentLink. We preserve the full note text, author name, timestamp, and any attachments. Note authorship is stored in a custom note_author__c field because Pipedrive Notes do not have a native author field. Large attachments are extracted and linked as Files.

Documents and attachments stored in Lime Go are extracted and linked as Pipedrive Files attached to the corresponding Organization, Person, or Deal record. We preserve file names, upload timestamps, and content. Files exceeding Pipedrive's storage limits are linked via external URL reference or stored in the customer's designated cloud storage with a link recorded in Pipedrive.

Lime Go tenant-specific custom fields on Customers, Contacts, and Deals are discovered during scoping and recreated in Pipedrive before any data loads. Field types (text, number, date, picklist, multi-select) map to their Pipedrive equivalents. Any custom fields without a direct Pipedrive type equivalent are flagged during scoping with a recommended resolution—either a custom field type in Pipedrive or a note explaining the limitation.

Tags stored as flat label arrays on Customers, Contacts, and Deals in Lime Go transfer to Pipedrive Tags using the Tag API endpoint. Tags used for segmentation map as-is; tags used for content classification are documented as Pipedrive Label alternatives if the customer prefers a label-based taxonomy in Pipedrive. Tag strategy is confirmed during scoping.