Migrate from User.com to Odoo CRM

User.com Contacts map to Odoo via a split: Contacts with active deal association or company link become Odoo crm.lead records that sales reps convert to crm.opportunity (and ultimately res.partner). Cold prospects with no deal history remain as Odoo crm.lead for follow-up routing. We use the User.com contact's last_heard timestamp and any deal association as the split determinant. Email address becomes crm.lead.email_from or res.partner.email; phone becomes phone; tags map to Odoo tag_ids on crm.lead.

User.com Companies map directly to Odoo res.partner with the is_company flag set to True and the company_type field set to company. The company name becomes res.partner.name, domain becomes website, address fields map to street, street2, city, state_id, zip, and country_id. We link the company's associated Contacts as individual res.partner records with parent_id pointing to the company record, preserving the User.com contact-to-company relationship in Odoo's partner hierarchy.

User.com Deals map to Odoo crm.opportunity. The dealstage property maps to Odoo's stage_id with the stage name and probability preserved. Deal value maps to Odoo's expected_revenue and planned_revenue fields. We map deal owners to Odoo res.users by email lookup, and preserve custom deal fields as Odoo custom Char, Float, or Selection fields on crm.opportunity before import. User.com's deal-contact and deal-company associations map to crm.opportunity.partner_id and the Odoo lead-contact link respectively.

User.com Events (calendar/activity events) map to Odoo calendar.event with name, start_datetime, stop_datetime, duration, and location preserved. We resolve attendee emails against the migrated res.partner and crm.lead records to populate calendar.event.partner_ids. Event-type attributes from User.com map to a custom description field on the calendar event. DateTime values are converted from User.com's ISO 8601 export to UTC for Odoo's datetime storage.

User.com Activities map to Odoo mail.activity records linked to the parent res.partner or crm.lead record. Activity type (call, email, meeting, task, note) maps to Odoo's activity_type_id. We preserve activity date, summary, and note body as mail.activity's date_deadline, summary, and note fields. Email opens, chat sessions, and push notification metadata are mapped to a custom description field because Odoo mail.activity has a richer type taxonomy than User.com's activity export.

User.com contact custom properties map to Odoo res.partner custom fields created via Settings > Technical > Database Structure > Custom Fields before migration. Selection and multi-selection properties map to Odoo Selection and Many2many fields respectively; date properties map to Date; text properties to Char or Text depending on length. Choice fields that used {} brackets in User.com's late-2023 export are normalized to plain string values before insert. The customer must pre-create the custom field schema in Odoo or authorize FlitStack AI to create fields via the XML data file import path.

User.com deal custom fields map to Odoo crm.opportunity custom fields using the same type-mapped approach as contact custom properties. We detect any JSON-typed custom properties in the User.com export and flatten them into Char fields with the JSON string preserved for downstream parsing. Custom fields that reference User.com contact IDs are flagged for cross-record resolution after the contact migration phase.

User.com Tags on contacts and deals map to Odoo crm.tag records via the tag_ids many2many relationship on crm.lead and crm.opportunity. We extract the distinct tag set from User.com, create matching crm.tag records in Odoo, and build the many2many relation table entries during import. Tags used for segmentation purposes in User.com are preserved as tag assignments even though Odoo's dynamic segment evaluation is a separate feature that must be rebuilt.

User.com Segments are dynamic groups based on contact attributes. We export segment membership (the static list of contact IDs that matched each segment at migration time) and map those IDs to crm.tag records labeled with the segment name. Odoo's ir.filters provides saved filter views that approximate segment behavior; we document the attribute criteria for each User.com segment as Odoo domain expressions for the customer's admin to create as ir.filters post-migration.

User.com conversation threads and chat transcripts export as bundled records that we flatten and re-associate to individual res.partner records in Odoo. Each message becomes a mail.message record with message_type = comment, posted to the partner's Odoo chatter (mail.thread) using the partner_id as res_id. Message timestamp, sender, and body content are preserved; attachments in the chat export map to Odoo ir.attachment records linked via the relation field.

Web push subscriptions in User.com trigger the contact-based billing count but have no native Odoo equivalent. We export the push subscription attribute as a custom field push_opt_in__c on res.partner and flag it for the customer's admin to configure a marketing integration (Odoo Email Marketing or a third-party push service) if needed. This avoids accidentally re-creating push-active contacts that would inflate the User.com bill during the transition window.

User.com Owners referenced on Contacts, Companies, Deals, and Activities map to Odoo res.users by email match. We extract the full owner roster from User.com, match each email against the destination Odoo instance's res.users table, and hold any unmatched owners in a reconciliation queue for the customer's Odoo admin to provision before record import resumes. Owner references on deals and activities are resolved at migration time using the validated User-to-res.users map.