Migrate from RSoft CRM to Odoo CRM

RSoft Company records map to Odoo res.partner with type = 'company'. The company name maps to name, industry to industry_id, address fields to street, street2, city, state_id, zip, and country_id, and owner to user_id on the contact side. We create the company Partner first, then use its id as parent_id when creating the contact Partner records so that child contacts are properly linked to the organization.

RSoft Contact records map to Odoo res.partner with type = 'contact' and parent_id set to the Partner id from the mapped Company. Fields mapped include name, phone, email, address components, lifecycle stage (preserved as a tag or custom stage field), and owner (mapped to Odoo user_id). The parent_id linkage is critical for Odoo's contact hierarchy to function correctly. If a Contact has no Company in RSoft, it is created as a standalone Partner with type = 'contact' and no parent_id.

RSoft Lead records map to Odoo crm.lead in the Lead stage. Fields mapped include name (contact or company name), contact_name, email_from, phone, street, website (from company domain if available), lead_source (mapped to tag or source_id if Odoo has source tracking enabled), stage_id, and user_id (owner). RSoft lead score migrates to a custom integer field if configured in Odoo. The lead_type field in Odoo defaults to 'lead'; if the customer wants all records treated as opportunities, we set type = 'opportunity' during import.

RSoft Deal records map to Odoo crm.lead with type = 'opportunity'. The deal amount maps to planned_revenue, probability maps to probability (with Odoo's stage-based probability adjusted to match RSoft's custom percentages), expected close date maps to date_deadline, and owner maps to user_id. The RSoft pipeline assignment and stage name map to Odoo's stage_id within the CRM pipeline. We preserve the original deal name as the opportunity name in Odoo. If RSoft deals reference a Company and Contact, those ids are resolved to Odoo partner_id and contact_id before import.

RSoft pipeline stage names, positions, and probability values are extracted from the deal export and mapped to Odoo crm.stage records within the CRM pipeline. We create each stage with the correct sequence number to match the kanban column order in RSoft. Probability percentages are set on the stage if the customer uses stage-driven probability; if the customer uses custom probability per deal, those values migrate as override values on each opportunity record. Stage automation triggers from RSoft (such as automatic actions on stage entry) are documented in the automation handoff as Odoo Automated Actions equivalents.

RSoft Activities (calls, emails, SMS, notes) attached to Contacts, Leads, or Deals migrate to Odoo mail.activity records. Activity type maps to activity_type_id (call, email, meeting, sms, note), subject to activity_decoration, and date_deadline to the activity date. The user_id (owner) maps to the Odoo responsible user. Note body migrates as a mail.message record on the thread rather than as an activity. We flag that IVR call logs and autodialer call records are stored in RSoft-specific telephony modules that do not appear in the standard CSV export and cannot be migrated via standard Odoo import.

RSoft Ticket records map to Odoo helpdesk.ticket if the customer licenses the Odoo Helpdesk app. Subject, status, priority, and assignee map to name, stage_id, priority, and user_id. Ticket conversations from email, phone, chat, and social media migrate as mail.message thread entries. If the customer does not license the Helpdesk app, Tickets migrate as crm.lead records tagged as 'ticket' and the customer documents this as a post-migration decision. Custom ticket fields above the plan limit require Odoo Studio configuration before import.

Tags from RSoft Contacts, Leads, and Deals are extracted as a flat list, deduplicated, and created as crm.tag records in Odoo before any record import. Each migrated record's tag list is then linked via crm.lead.tag_ids (or res.partner.category_id for contact tags). The tag vocabulary is preserved exactly; Odoo does not impose a tag limit at any tier.

RSoft user accounts referenced as owners on Contact, Company, Deal, and Ticket records are mapped to Odoo res.users by email match. We extract the full user roster from RSoft during discovery, match against the destination Odoo instance's users, and flag any RSoft owner without a corresponding Odoo user. The customer's Odoo admin provisions missing users before record migration begins. Owner resolution is a prerequisite for all object imports because user_id is a required or strongly recommended field in Odoo's CRM model.

RSoft custom fields (those beyond the standard set) on Contacts, Leads, Deals, and Tickets are mapped to custom fields in Odoo. We pre-create the custom field schema in Odoo via Studio or direct model extension before data import. Field types are mapped: text to char or text, number to float or integer, date to date, dropdown to selection, multi-select to many2many or tags. Fields that exceed the destination plan's limit (if the customer is on a lower Odoo tier) are flagged during scoping for review. The original field names and values are preserved; we do not rename or retype custom fields without explicit customer approval.

RSoft does not expose document attachments via CSV export, so inline record migration does not include files. We identify any file attachments referenced in RSoft (documents linked to Contacts, Deals, or Tickets) during discovery and transfer them separately via file transfer into Odoo's ir.attachment table. The attachment is linked to the migrated record via res_model and res_id. We note the file size and count during scoping so the customer can allocate appropriate storage in the Odoo instance.

RSoft workflow definitions do not export from the platform and cannot be migrated as code. We document every active RSoft workflow during discovery: trigger event, conditions, sequence of actions (WhatsApp, email, call, SMS, field update), and delay configuration. This inventory is delivered as a written handoff document so the customer's Odoo admin can rebuild equivalent Automated Actions in Odoo Studio. We do not rebuild workflows as part of the migration scope.