Migrate from SmartDesk to Odoo CRM

SmartDesk Contacts map directly to Odoo res.partner records. We set partner_id to the matched Contact record and set customer=True to distinguish from Company-type partners. SmartDesk's contact lifecycle stage maps to a custom Char field smartdesk_lifecycle_stage__c on res.partner for audit. Email, phone, address, and custom contact properties migrate field-to-field. The res.partner record is created before any Deals to satisfy the partner_id required field on crm.lead.

SmartDesk Accounts (Companies) map to Odoo res.partner with is_company=True. The SmartDesk company domain becomes the partner's website field and is used as the dedupe key during import. Industry classification and employee count map to Odoo industry_id and employee_size fields (custom Many2one fields that the customer configures via IrProperty before migration). Custom properties attached to the Account migrate to custom fields on res.partner.

SmartDesk Leads map to Odoo crm.lead records with type='lead'. Lead Source and Lead Status from SmartDesk custom fields migrate to crm.lead's source_id (Many2one to crm.lead.lost_reason or a custom Char) and stage_id (Many2one to crm.stage) respectively. The customer's SmartDesk pipeline stage names are reconciled against the Odoo stage sequence, and any unmatched stages are flagged for stage creation in Odoo Studio before migration.

SmartDesk Deals map to Odoo crm.lead with type='opportunity'. The SmartDesk dealstage maps to Odoo stage_id, deal_value maps to planned_revenue, expected close date maps to date_deadline, and owner maps to user_id resolved via email match to res.users. Deals linked to SmartDesk Contacts resolve to res.partner partner_id; Deals linked to SmartDesk Accounts resolve to the company-type res.partner parent_id on the Contact.

SmartDesk Pipelines and Stages require Odoo stage configuration before Deal migration. We enumerate every distinct SmartDesk pipeline and stage combination and create corresponding crm.stage records per Sales Team in Odoo. Stage probability percentages from SmartDesk migrate to the stage's sequence and probability fields. If SmartDesk stages have no probability data, we default to Odoo's standard stage probability curve and flag for customer review.

SmartDesk Tasks attached to Contacts or Deals map to Odoo crm.lead records with type='lead' for standalone tasks, or to Task records linked via mail.activity with type='other'. We preserve task assignee (resolved to res.users by email), due date, status, and description body. Linked Contacts resolve to res.partner partner_id; linked Deals resolve to crm.lead id via SmartDesk deal ID lookup.

SmartDesk call activities map to Odoo mail.activity records with activity_type_id set to the Call type (created in Odoo as a custom activity type). Call duration and disposition migrate to custom fields on the activity record. The activity's related SmartDesk Contact or Deal resolves to the target res.partner or crm.lead in Odoo via the parent record lookup step.

SmartDesk email engagements map to Odoo mail.message records with message_type='email'. The email body, subject, and timestamp migrate directly. The related SmartDesk Contact resolves to res.partner for display in Odoo's mail thread. Email tracking data (opens, clicks) does not migrate as Odoo does not store this metadata in the same schema.

SmartDesk meeting activities map to Odoo calendar.event records with start, stop, duration, and location preserved. Attendee mapping creates calendar.attendee records linked to the res.partner contacts and res.users for internal attendees. The related SmartDesk Contact or Deal resolves via the parent record lookup step.

SmartDesk note activities map to Odoo mail.message records with subtype='mt_notes'. The note body and timestamp migrate directly. Internal notes are distinguishable from emails in Odoo's mail thread by message_type='notification' or a custom note flag.

SmartDesk Campaigns are mapped to Odoo crm.lead records with a campaign tag applied via crm.tag. Campaign metadata (name, type, status, start/end dates) is stored in custom fields on the lead. The customer chooses whether to create individual crm.lead records per contact within a campaign or to tag existing leads; this is decided during scoping.

SmartDesk Email Templates migrate as mail.template records in Odoo with the template body, subject, and merge field placeholders preserved as static text. Dynamic conditional content and personalization logic embedded in SmartDesk templates is flagged for manual post-migration review in Odoo's template editor.

SmartDesk Tickets do not map to a native Odoo Helpdesk object unless the customer purchases the Odoo Helpdesk module (~$129/user one-time). Without the module, we migrate Tickets as crm.lead records tagged with a 'ticket' tag, carrying priority, status, and conversation body as custom fields. If the Helpdesk module is active, Tickets map directly to helpdesk.ticket with conversation threads as mail.message records.

SmartDesk KB Articles migrate to Odoo knowledge.article records with title, body (HTML), category, and isublished status preserved. Attachment URLs are re-linked post-migration. The knowledge.article schema in Odoo requires the Knowledge app to be installed; if it is not, we migrate KB content as crm.lead records or documentation attachments and flag the Knowledge module as a separate activation item.

File attachments associated with SmartDesk Contacts, Deals, or Tickets are downloaded from the source and uploaded to Odoo ir.attachment records linked via res_model and res_id to the corresponding res.partner or crm.lead. We preserve original filenames and file type metadata. Large attachment volumes require batched upload to avoid Odoo's attachment storage limit on certain hosting configurations.

SmartDesk custom fields require pre-creation in Odoo via IrProperty before migration. We provide a custom field manifest listing every SmartDesk custom field name, data type, and target object so the customer can configure the corresponding Odoo field definitions via Settings > Technical > Custom Fields or via module development before the migration run begins.

SmartDesk Owners map to Odoo res.users by email match. We resolve each SmartDesk owner email to the corresponding Odoo user and apply as user_id on crm.lead records and user_id on mail.activity records. Any SmartDesk owner without a matching Odoo user goes to a reconciliation queue; the customer's admin provisions missing users before record import resumes.