Migrate your Lime CRM data

Companies (sometimes called Accounts in Lime CRM) hold the organisational record with address, industry, and relationship to Contacts. Standard fields map cleanly across CRMs. We preserve the company-contact relationship during migration to avoid orphaned Contact records.

Contacts are the primary person record linked to Companies. Name, email, phone, and custom properties are fully exportable. We normalise phone formats to prevent leading-zero stripping that commonly occurs in CSV exports.

Deals track the sales opportunity with value, stage, owner, and expected close date. Lime CRM allows custom deal pipelines and stages per industry. We map source stages to destination pipeline stages and flag any deprecated stages before import.

Activities represent logged calls, meetings, tasks, and notes attached to a Contact or Deal. We export these as chronological activity records and reconstruct the parent-child relationship in the destination system.

Ticket support is a core part of Lime CRM's helpdesk orientation. We migrate Ticket records with status, priority, assignee, and conversation history. Conversation messages require reassembly from individual exports.

Attachments are exported individually per record, potentially multiple files per Contact or Deal. We batch and rename files to preserve the parent relationship and flag any files exceeding 25 MB before upload to avoid API rejection.

Lime CRM's schema is built around configurable Limetypes. Custom objects require field-level mapping because their schema varies per customer implementation. We treat each custom Limetype as a separate export job and validate the schema before import.

Automations streamline ticket assignments and follow-up sequences. These rules do not export in a transferable format, so we document the automation logic from Lime CRM and reproduce equivalent rules in the destination platform as part of migration scoping.

Tags label Contacts, Deals, and Tickets for segmentation. We export tag values as a flat list per record and recreate tag taxonomies in the destination CRM, noting any platform differences in tag inheritance.

User records and Deal owners are mapped by email address. We validate that destination user accounts exist before assigning ownership to avoid orphaned records with null owner fields.

Documents are stored alongside Deals and Contacts with auto-fill templates. The export contains the document blob and its metadata. Template auto-fill fields require mapping to the destination system's equivalent fields.