Migrate from Lime Go to Odoo CRM

Lime Go Customer records map to Odoo res.partner with is_company=True. Customer name becomes the partner display name, address fields (street, city, country, zip) map to res.partner address fields, phone maps to phone, website maps to website, and custom properties on Customer map to res.partner custom field columns. Customer owner assignments map to Odoo User records via email match. We create the Company partner record before importing any related Contact records so that the child_id relationship is satisfied on insert.

Lime Go Contact records map to Odoo res.partner with is_company=False, linked as children of the corresponding Customer-Company record via parent_id. Contact name splits into firstname and lastname fields on res.partner using the name split plugin if installed; otherwise name maps as a single display field. Email, phone, mobile, job title, and custom fields migrate directly. GDPR consent flags migrate as custom partner properties (x_lime_consent_status, x_lime_consent_date) to preserve compliance posture in Odoo.

Lime Go's visual adjustable sales pipeline maps to Odoo's CRM Team (crm.team) for team assignment and CRM Stage (crm.stage) for pipeline stage values. Each Lime Go pipeline becomes an Odoo CRM Team with its own stage sequence. Stage names, order, and probability percentages migrate to Odoo stage records. If Lime Go uses multiple pipelines, each becomes a separate Odoo CRM Team with stage sequences configured accordingly.

Lime Go Deals map to Odoo crm.lead records with type=opportunity. Deal name becomes the lead name, deal value maps to expected_revenue, expected_close maps to date_deadline, pipeline stage maps to stage_id via the stage sequence mapping, and owner maps to user_id via email-matched User resolution. Custom fields on Deals migrate to crm.lead custom columns (x_ prefix per Odoo convention). Historical stage transitions migrate as log notes on the crm.lead chatter.

Lime Go Activities (calls, emails, meetings, tasks) map to a combination of Odoo mail.message records for communication history and project.task records for action items. We parse the activity type from Lime Go to route to the correct Odoo model: email-type activities become mail.message records linked to the partner; call activities become project.task records with activity_type_id set to phone call; meeting activities become calendar.event records; generic task activities become project.task records. All migrated activities link to the parent res.partner or crm.lead via res_id and model fields to preserve the timeline view in Odoo.

Lime Go Tasks migrate to Odoo project.task records within the CRM project (or a dedicated migration project). Task title, description, due date, priority, and status (stage_id) map directly. Task assignee resolves by email match to the Odoo User record. Recurring tasks map as task templates with recurrence rules stored in project.task.type. We preserve the original Lime Go task creation timestamp as x_lime_created_on for audit.

Lime Go Reminders attached to Contacts, Customers, or Deals map to Odoo project.task records (for action reminders) or calendar.event records (for time-based alerts). Reminder text becomes task description or event description. The original reminder timestamp is preserved as the task deadline or event start time. If the reminder is attached to a Deal (crm.lead), the task is linked to the opportunity record via res_id and model='crm.lead'.

Lime Go History Notes migrate as Odoo mail.message records on the res.partner (for Contact/Customer notes) or crm.lead (for Deal notes) chatter. Note text becomes the message body, author maps to the Odoo User who created the note, and timestamp preserves the original note creation date. File attachments on History Notes migrate as ir.attachment records linked to the same res_id/model pair as the note.

Lime Go's built-in Nordic company enrichment database (3.7 million records) is a read-only enrichment layer, not user-owned CRM data. It does not migrate as Contact or Company records. We flag these records separately during scoping and preserve the enrichment reference as a note field on the corresponding Customer or Contact record (e.g., x_lime_enrichment_id storing the Lime Go enrichment record ID). Customers who rely on this enrichment data should configure an Odoo-compatible enrichment provider (such as an Odoo app with Nordic company data) post-migration.

Documents attached to Lime Go Customers, Contacts, or Deals migrate as Odoo ir.attachment records linked via res_model and res_id to the corresponding res.partner or crm.lead. File names, mime types, and upload timestamps are preserved. We handle binary file extraction from Lime Go's export format and re-upload to Odoo's ir_attachment table. Large files (over 25 MB) are handled separately via Odoo's filestore management to avoid upload timeout.

Lime Go tenant-specific custom fields on Customers, Contacts, and Deals vary per installation. We discover the tenant schema during scoping (including field names, types, and picklist values), pre-create the equivalent custom columns in Odoo using the Settings > Technical > Custom Fields interface (or directly in the database for Community edition), and map field types: text fields to char/text, numbers to float/integer, dates to date/datetime, picklists to selection fields or many2one relations, and multi-select to char with comma-separated values or tags. Fields with no Odoo equivalent are flagged in the scope document for the admin to review.

Lime Go tags apply across Customers, Contacts, and Deals for segmentation. We extract all distinct tag values, pre-create corresponding crm.tag records in Odoo, and link them to the appropriate res.partner (for Customer/Contact tags) or crm.lead (for Deal tags) via the crm.tag.rel many2many table. Tags used for deal categorization also appear on the crm.lead form in Odoo's tag_ids field. The customer confirms tag usage strategy during scoping.

Lime Go's GDPR consent history (granted, withdrawn, timestamps, policy versions) migrates as custom fields on res.partner: x_lime_consent_status (selection: granted, withdrawn, pending), x_lime_consent_date (date), x_lime_consent_policy_version (char), and x_lime_consent_source (char). We preserve the full consent timeline to maintain GDPR compliance posture in Odoo. Customers using Odoo Enterprise can optionally configure the built-in gdpr module to manage ongoing consent requests post-migration.

Lime Go Owners referenced on Customer, Contact, Deal, and Activity records map to Odoo res.users records by email match. We extract every distinct Owner email, validate against the destination Odoo instance's user list, and flag any Owner without a matching Odoo User in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Odoo users can receive records if the admin sets the user's active flag accordingly during migration.