Migrate from SuiteDash to Odoo CRM

SuiteDash Contacts with no deal history and no explicit qualification status map to Odoo CRM Lead. Contacts with active Deals or that represent established customers map to Odoo Contact (res.partner, customer=True) attached to the corresponding Company Partner (res.partner, company_type=company). We compute the split at migration time using the presence of deal_ids and the contact's status property. The original SuiteDash contact_type and any custom contact-level fields migrate as custom fields on both the Lead and Contact records.

SuiteDash Company records map directly to Odoo res.partner records with company_type=company. The company's domain name becomes the partner's website field and is used as the dedupe key during import. Company is created before any Contact import so that the child_id parent relationship is satisfied at the moment of Contact insert. We preserve Company Public and Company Private custom field scopes by mapping Public fields to visible partner properties and Private fields to internal note fields or custom res.partner fields gated by ir.model.access rules that match the SuiteDash Primary Contact visibility model.

SuiteDash Deals map to Odoo CRM crm.lead records with type='opportunity'. The dealstage property maps to the Odoo stage_id within the assigned Sales Team's pipeline. Probability percentages migrate from SuiteDash to crm.lead.probability, rounded to the nearest integer. Closed-Lost and Closed-Won status migrates to Odoo's lost reason and stage configuration. The Contact and Company lookups are resolved via the parent-record lookup we established in the Contact and Company phases.

Each SuiteDash deal pipeline and its stages map to an Odoo Sales Team (crm.team) with its own stage sequence. Stage order and names are preserved. Probability values per stage are stored on crm.stage as probability defaults. If SuiteDash has multiple pipelines, we create one crm.team per pipeline and assign the relevant crm.lead records to the corresponding team at migration time.

SuiteDash Projects map to Odoo project.project records with project.task records as children. Project-level custom fields migrate to project.project custom fields created via Odoo Studio before migration. Task hierarchy (parent-child relationships) is preserved by mapping SuiteDash task parent_id references to Odoo project.task parent_id. Project status (active, completed, archived) maps to Odoo's project state field. Owner or Project Manager from SuiteDash maps to the Odoo project.manager user reference.

SuiteDash Support Tickets map to Odoo Helpdesk tickets if the customer includes the Helpdesk app in their Odoo installation. Ticket status workflows (open, in progress, resolved, closed) map to Odoo stage_id values within a helpdesk team. Thread history and conversation attachments migrate as mail.message records linked to the ticket. Ticket priority and custom fields migrate to the corresponding helpdesk.ticket fields. If Helpdesk is not in scope, tickets are migrated as crm.lead records with a tag indicating their support origin.

SuiteDash Invoice records (including line items, payment status, and Invoice Custom Fields) map to Odoo account.move records with move_type='out_invoice'. Invoice Custom Fields are discovered via the Invoice API endpoints, not via GET /contact/meta — we run a separate Invoice-specific field discovery during scoping to capture these. Historical paid invoices migrate as records only; active or pending invoice workflows require additional configuration after migration. Odoo Accounting app must be installed for this object to be active.

SuiteDash Staff Members map to Odoo res.users records. Staff role assignments in SuiteDash are documented but do not automatically map to Odoo access groups — we deliver a role mapping table during scoping so the customer assigns Odoo access rights (Sales / Administrator / Portal User) per staff member. Owner and assignee references on Deals, Projects, and Tickets resolve via this User mapping after res.users records are created and activated.

SuiteDash Contact-scoped custom fields (CRM > Contacts type) map to Odoo res.partner custom fields created via Studio or the res.fields API. Field types are mapped: text to char/text, date to date, number to float or integer, dropdown to selection, checkbox to boolean. Multi-value fields (checkbox groups, multi-select) map to char with comma-separated values unless Odoo Studio supports an equivalent widget.

Company Public custom fields in SuiteDash are visible to all associated Contacts and map to custom fields on the res.partner company record. Visibility is equivalent in Odoo — the field is available on the Company partner form. We preserve the field display order and grouping as configured in SuiteDash's Custom Field builder.

Company Private custom fields in SuiteDash are visible only to the Primary Contact and are not exposed via Dynamic Data Placeholders. During scoping we identify all Private-scoped Company fields and confirm with the customer whether they should map to a restricted custom field in Odoo (with ACLs scoped to the Primary Contact's user record) or be stored as an internal note. Private fields that cannot be placed in an equivalent visibility bucket are flagged for manual review. This is one of the highest-risk custom field decisions in this migration pair.

SuiteDash Organization-level custom fields map to Odoo res.company custom fields. These are company-wide settings visible to all users with access to the company record. We map these after the Odoo company record is created during installation and confirm the customer's company setup before importing.

Project-scoped custom fields in SuiteDash map to custom fields on Odoo's project.project model. These are installed when the Project app is present in the Odoo installation. We confirm which Odoo apps are active before designing this part of the schema.

Support-scoped custom fields map to Odoo helpdesk.ticket custom fields if the Helpdesk app is included. If Helpdesk is not in scope, these fields are mapped to crm.lead custom fields or stored as internal notes on the associated ticket record.

SuiteDash Tags on Contacts and Companies are freeform labels used for segmentation. They map to Odoo CRM Tags (crm.tag) which can be assigned to Leads, Opportunities, and Partners. We export Tags as a comma-separated list from SuiteDash and create the corresponding tag records in Odoo during the staging phase. The customer chooses between tag-based segmentation or storing tag values as a custom field during scoping.

SuiteDash Appointments map to Odoo calendar.event records linked to the relevant Contact and Company partners. Scheduling status (confirmed, cancelled, pending) maps to Odoo's calendar event state field. The bidirectional calendar sync settings in SuiteDash (Google Calendar, Outlook) do not port; we document the booking page configuration separately for the customer to reconfigure in Odoo Calendar or a third-party scheduling tool.

SuiteDash Automations reference internal Contact IDs, Company IDs, and Staff IDs that are not stable across export. Even with access to the automation definition, the internal references would be stale in Odoo. We do not migrate Automations as code. Instead, we produce an Automation Audit Report listing every active automation with its trigger event, conditions, actions, and the Odoo Action Rule or Automated Action equivalent. The customer's admin rebuilds these in Odoo Studio or via Python server actions post-migration.