Migrate from Lime CRM to Odoo CRM

Lime CRM Company records map to Odoo res.partner with partner_type set to 'company'. The Lime CRM company name, address fields, industry, and VAT number map to the corresponding Odoo partner fields. Odoo uses res.partner for both organisations and individuals; we set is_company=True on Company records and link Contacts as children. We resolve the company name as the dedupe key during import to prevent duplicate partners in Odoo.

Lime CRM Contact records map to Odoo res.partner with partner_type set to 'individual' and parent_id pointing to the related Company partner. Name, email, phone, mobile, and function/role fields migrate directly. Custom Contact fields defined as Lime CRM Limetype properties map to Odoo custom fields on res.partner. The parent_company_id (lookup to Company) migrates as parent_id on the Odoo res.partner record.

Lime CRM Deal records map to Odoo crm.lead with type='opportunity'. Deal name becomes crm.lead name, deal value becomes planned_revenue, deal stage maps to a stage_id in an Odoo pipeline, and expected close date maps to date_deadline. Lime CRM allows custom deal pipelines and stages per industry; we create corresponding Odoo CRM Pipeline stages and assign the stage_id on import. Owner resolves by email match against Odoo res.users.

Each Lime CRM deal pipeline with its stages maps to an Odoo CRM Stage within a crm.team pipeline. We create stages in Odoo matching the Lime CRM stage order and probability percentages. Stage names and order are preserved; probability percentages round to the nearest integer Odoo allows on stage configuration.

Lime CRM Activities (calls, meetings, tasks, notes) attached to a Contact or Deal map to Odoo mail.activity records linked to the migrated res.partner or crm.lead. Activity type, subject, body, date, and duration migrate. Odoo mail.activity is the primary activity tracking model in Odoo 15 and later; we link activities to the correct res_id and res_model using the migrated record IDs from the parent object import phase.

Lime CRM exports email conversations as individual ConversationMessage files rather than threaded objects. We detect conversation ID and timestamp across the export manifest, reassemble messages into chronological order, and inject them into Odoo as mail.thread records with mail.message children. The parent record (Contact or Deal) is linked via res_id and model. This reassembly step is unique to Lime CRM source migrations and adds time to the scoping phase.

Lime CRM Ticket records migrate to Odoo helpdesk.ticket if the destination includes the Odoo Helpdesk module. Ticket subject, description, status, priority, and assignee map to the corresponding Odoo fields. Ticket conversations migrate as mail.message on the ticket. We flag that the Odoo Helpdesk module is a separate install and add it to the scope if the customer requires ticket migration.

Lime CRM's configurable Limetypes are the most complex migration object because their schema is unique per customer. We extract the live Limetype field definitions from Lime CRM admin during discovery, map each Limetype to either an Odoo custom field on res.partner (if the Limetype is a person or company extension) or to a new Odoo model using ir.model.model inheritance (if the Limetype is a standalone entity). Each custom Limetype is treated as a separate mapping workstream with its own schema export and field mapping.

Lime CRM Tags applied to Contacts, Deals, and Tickets migrate to Odoo crm.tag records with tag_ids on crm.lead. We export tag values as a flat list per record and recreate the tag taxonomy in Odoo before import. Tags with the same name are deduplicated by tag name during import.

Lime CRM attachments are downloaded individually per record. We batch download by parent object (Contact, Deal, Ticket), rename files to preserve the parent relationship, and import them to Odoo ir.attachment linked to the migrated record via res_model and res_id. Files exceeding 25 MB are flagged before import because Odoo has a default attachment storage limit that may require configuration on the destination instance.

Lime CRM Documents stored alongside Deals and Contacts with auto-fill templates export as document blob plus metadata. We import the document blob to Odoo ir.attachment linked to the parent record. Template auto-fill field mappings are documented as part of the mapping spec for the customer's admin to reconfigure in Odoo using the Odoo document management module.

Lime CRM Users and Deal owners map to Odoo res.users by email match. We validate that the destination Odoo instance has a corresponding user account before assigning owner_id references on migrated records. Users without a matching Odoo account go to a reconciliation queue for the customer to provision before record import resumes, because OwnerId references are required on most Odoo crm.lead and helpdesk.ticket records.