Migrate from SoulCRM to Odoo CRM

SoulCRM Companies map to Odoo CRM Partners with company_type set to company. The Company Name maps to Partner name, registered address maps to street/city/state/zip fields, phone maps to phone, email maps to email, and website maps to website. SoulCRM custom fields capturing GST numbers map to custom Char fields on res.partner. SoulCRM regional segmentation fields map to Odoo custom country_group or region picklist fields. We import Companies first because every Contact in SoulCRM requires a parent Company link, and Odoo Partner records must exist before Contact import to satisfy the partner_id foreign key.

SoulCRM Contacts map to Odoo CRM Partners with company_type set to person. First name and last name split from SoulCRM full name field into Odoo partner name fields. Email, phone, mobile, and address fields map directly. The parent_id on Partner links to the imported Company (res.partner of type company) to preserve the SoulCRM Company-Contact relationship. We use email as the dedupe key during import to avoid creating duplicate Partner records for contacts that appear in multiple SoulCRM modules.

SoulCRM Leads map to Odoo CRM Lead (crm.lead model). Lead name, email, phone, source, and status migrate directly. SoulCRM lead scoring custom fields map to Odoo custom probability adjustment fields. SoulCRM assignment fields (owner) map to Odoo user_id. Unqualified leads stay as Odoo Lead until manually converted; qualified leads convert during migration based on the customer's criteria. The SoulCRM Marketing Module lead capture fields map to Odoo custom fields on crm.lead for campaign attribution.

SoulCRM Deals map to Odoo CRM Opportunities (crm.lead model with type = opportunity). Deal name maps to Opportunity name, amount maps to planned_revenue, probability maps to probability (as integer), and stage maps to stage_id via Odoo stage name matching. The deal owner (SoulCRM assignment) maps to user_id on Opportunity. Closed-Lost and Closed-Won statuses from SoulCRM map to Odoo stage_id values with probability set to 0 or 100 respectively. SoulCRM pipeline stage names require explicit mapping to Odoo CRM stage_ids via the customer's Odoo pipeline configuration.

SoulCRM deal pipeline stages map to Odoo CRM stage records. Each SoulCRM stage name becomes an Odoo stage_name, with probability percentages mapped to Odoo's stage probability field. If SoulCRM has a single pipeline, we create a single Odoo CRM team with that pipeline. If multiple pipelines exist in SoulCRM, we create multiple Odoo CRM teams (salesteam_id) with their respective stage sets. Stage order sequence numbers migrate from SoulCRM to Odoo's sequence field to preserve visual ordering in the pipeline kanban view.

SoulCRM call logs map to Odoo CRM Phonecall records (crm.phonecall model in Odoo apps, or Task with activity_type phone if using the Odoo native activity system). Call duration, disposition, and timestamp migrate to the corresponding Odoo fields. The phonecall or activity is linked to the resolved Partner (Contact) record via the partner_id lookup. Call notes from SoulCRM become the Odoo activity notes field. We resolve the parent Partner record by email match before inserting the activity.

SoulCRM email logs map to Odoo CRM Message records on the Lead, Opportunity, or Partner (mail.message model). Email subject becomes message_subject, body migrates to message_body as HTML. The email-from and email-to addresses migrate to mail.message fields. If SoulCRM stores emails as activity records, they map to Odoo mail.activity records with activity_type email. Email body HTML formatting may require normalization (stripping embedded styles) to render correctly in Odoo's mail thread interface.

SoulCRM tasks map to Odoo CRM tasks. Task subject, description, due date, and status migrate to Odoo task fields. If the customer uses Odoo Project app, tasks map to project.task; otherwise they map to CRM task records. Task assignment (SoulCRM owner) maps to user_id on the Odoo task. Completed status from SoulCRM maps to Odoo stage or kanban_state = done.

SoulCRM meeting records map to Odoo Calendar Event records (calendar.event model). Meeting title, start datetime, end datetime, location, and description migrate directly. Attendees linked to SoulCRM Contacts resolve to Odoo Partner records and appear as calendar.attendee records. We preserve meeting body or notes as the calendar event description. If SoulCRM stores meetings as activity records, they map to mail.activity with activity_type meeting.

SoulCRM Marketing Campaigns map to Odoo UTM Campaign records (utm.campaign model). Campaign name, type, start/end dates, and budget migrate to the corresponding Odoo fields. Campaign membership (Contacts and Leads linked to the campaign) maps to utm.mixin records on the Contact or Lead. Odoo UTM tags track campaign attribution on leads and opportunities. Note that SoulCRM campaign automation workflows do not migrate; we document the campaign names and membership counts for the customer's admin to recreate in Odoo marketing automation or a third-party email tool.

SoulCRM custom fields for GST numbers (India Goods and Services Tax identifiers) map to Odoo custom Char fields on res.partner. We create the custom field in Odoo via Studio or Python inheritance before Partner import, set the field label to GST Number, and set the field type to Char. GST format validation rules are documented for the customer's admin to configure in Odoo as a Python constraint or Studio validation. SoulCRM regional segment fields similarly map to Odoo custom selection or Char fields on res.partner.

SoulCRM file attachments linked to Companies, Contacts, or Deals migrate as Odoo IrAttachment records (ir.attachment model). We extract binary file data from SoulCRM CSV exports or separate file exports, create ir.attachment records with res_model pointing to res.partner or crm.lead, res_id set to the migrated record's ID, and store the file as base64 in the Odoo database. Folder hierarchy from SoulCRM flattens in Odoo; we document the original folder path in the attachment description field for reference.

SoulCRM Owner (assigned user on a record) maps to Odoo CRM User via email match. We extract distinct owner email addresses from all SoulCRM modules, match against the destination Odoo instance's res.users table, and resolve user_id on imported records. Any SoulCRM owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners can be set to Odoo User with active=false to preserve assignment history without granting login access.