Migrate from Less Annoying CRM to Odoo CRM

LACRM Contact records map to Odoo res.partner with is_company=False. We resolve the LACRM Contact-to-Company relationship using LACRM's relationship API endpoint and create the partner hierarchy in Odoo: the linked company becomes a res.partner with is_company=True, and the individual contact is created as a child partner of that company record. LACRM's UID (31-digit numeric string) is stored as a char field on res.partner for traceability and foreign key reference. Standard fields (name, email, phone, address, tags) map 1:1. LACRM's soft delete state is not migrated; only active records move.

LACRM Company records map to Odoo res.partner with is_company=True. Company name maps to partner name; address fields map to Odoo's street, street2, city, state_id, zip, and country_id fields using country and state reference tables. Because LACRM maintains Companies as separate objects from Contacts, we create the company partner first in Odoo before inserting any child contact partners, ensuring the parent relationship is satisfied at insert time. LACRM company phone, website, and industry fields map to Odoo's phone, website, and industry fields or custom res.partner fields.

LACRM Pipeline Items map to Odoo crm.lead records with type='opportunity'. We map the LACRM pipeline stage name to an Odoo CRM stage, creating the stage in Odoo CRM's pipeline configuration before migration if it does not already exist. Probability percentages must be assigned to Odoo stages (unlike LACRM's free-text stages with no probability); we assign the customer's implied win rate per stage or default to Odoo's standard probability matrix if none is specified. The pipeline item's linked contact resolves to the Odoo res.partner record created in step 1. LACRM's pipeline item monetary fields (value, expected close date) map to Odoo's planned_revenue and date_deadline.

LACRM pipeline stages are free-text and fully customizable per account. Each LACRM stage becomes an Odoo crm.stage record in the CRM pipeline, assigned to the relevant team. Odoo requires a probability percentage (0-100) for each stage; we set this from the customer's historical close rate per stage or use Odoo's default probability curve. Stages are ordered to match LACRM's pipeline sequence. If the customer has multiple LACRM pipelines (rare but supported), we map each to a separate Odoo CRM Sales Team with its own stage sequence.

LACRM Notes attached to contacts, companies, or pipeline items migrate to Odoo mail.message records on the corresponding res.partner or crm.lead. Notes are created as message_ids with message_type='comment', preserving the body content, author, and creation timestamp. The note's linked record type (contact, company, or pipeline item) determines the Odoo res_model (res.partner or crm.lead) and the res_id of the target record. Notes authored by a LACRM user who has a corresponding Odoo user resolve to that Odoo user as the message author; otherwise the message is attributed to the Odoo admin user.

LACRM Tasks migrate to Odoo project.task records linked to the target res.partner or crm.lead. We preserve due date (date_deadline), assignee (user_ids), completion status (stage_id mapping: LACRM completed maps to Odoo 'Done' stage; open maps to 'To Do'), and any linked contact or pipeline item. LACRM tasks without a linked contact or pipeline item are created under a default 'General' Odoo project. Recurring tasks in LACRM (if configured) are not migrated as recurring; the pattern is noted in the documentation package for manual Odoo recurrence setup.

Calendar events (meetings, calls) logged against contacts in LACRM map to Odoo calendar.event records. The event title, start/end timestamps, duration, location, and linked contact reference migrate with the attendee linked to the target res.partner record. LACRM's meeting and call types are preserved as tags on the calendar.event or mapped to Odoo's event type field if configured. Event recurrence patterns are not natively supported in LACRM and are not present in the export.

Files attached to LACRM contacts or companies are exported as base64-encoded content. We re-create them in Odoo as ir_attachment records linked to the corresponding res.partner via res_model='res.partner' and res_id reference. LACRM's 25GB per-user storage allocation requires us to assess total attachment volume during scoping. If total file size exceeds the destination Odoo instance's storage allocation, we flag the constraint before migration and the customer provisions additional storage. Because LACRM's API does not support uploading files back to contacts, this phase involves a manual re-attach step guided by our documented file map.

LACRM tags applied to contacts or companies migrate as Odoo mail.tag records attached to res.partner or to a custom contact_category selection field, depending on tag count and usage. If LACRM has fewer than 50 distinct tags, we recommend Odoo's tag system (mail.tag). If tag count exceeds Odoo's 64-character name limit, we truncate and flag. For high-cardinality tag sets, we recommend a custom many2many or selection field in Odoo Studio. The customer's tag usage pattern is reviewed during scoping to choose the correct approach.

LACRM custom fields on contacts, companies, and pipeline items are mapped to Odoo custom fields created via Settings > Technical > Custom Fields or developer mode. Field data types are matched: LACRM text to char, LACRM date to date, LACRM number to float or integer, LACRM dropdown to Odoo selection, LACRM checkbox to boolean, LACRM multi-select to many2many tag. Custom fields on LACRM pipeline items map to custom fields on crm.lead. Odoo's custom field schema is deployed to the destination database before any data is inserted to ensure fields exist at insert time.

LACRM automations are not exposed in the public API and cannot be exported programmatically. We flag this as the highest-severity migration gap for this pair. During scoping, we request screen captures or exported screenshots of every automation rule from LACRM's UI. We deliver a JSON-structured inventory of each automation's trigger conditions, filter criteria, and action steps with a written Odoo automated action or Studio workflow equivalent recommendation. The customer's Odoo admin or an Odoo implementation partner rebuilds each automation post-migration. Budget 1-2 hours per automation depending on complexity.

LACRM user accounts (name, email, permission level) map to Odoo res.users records. LACRM admin users map to Odoo users with admin-level access; standard users map to Odoo internal users. We match by email address during migration. LACRM's role model is simple (admin vs. standard user); Odoo's user groups are more granular (Sales / Administrator / Portal / Custom). We map LACRM admin to Odoo 'Administration / Settings' group and LACRM standard users to 'Sales / User' by default, flagging any customer-specific permission requirements during scoping.

LACRM Groups (team-segmentation for access control) map to Odoo res.groups records. We export group names and membership during scoping and create matching Odoo access groups. Note that LACRM Groups control both record visibility and data access; Odoo separates access rights (via Groups) from record rules (via Access Control List record rules). We document the current group-to-user mapping during scoping and recommend that the customer's Odoo admin configures record rules in Settings > Technical > Record Rules to fully replicate LACRM's data access constraints.