Migrate from SalesSeek to Odoo CRM

SalesSeek Organizations map to Odoo res.partner records with the company_type field set to 'company'. Standard fields (name, street, city, country, phone, website, industry) map directly. The original SalesSeek Organization ID is preserved in a custom Char field for re-linking to People records. Parent company relationships in SalesSeek map to Odoo's parent_id on res.partner. Address fields require normalization before import if the source data contains unstructured address strings.

SalesSeek People map to Odoo res.partner records with company_type set to 'person'. Each Person is created as a separate Partner record and linked to its parent Organization Partner via parent_id. The original SalesSeek People ID is preserved in a custom field for relationship resolution. If the customer uses SalesSeek's lifecycle stage on People, that value migrates to a custom selection field on the Partner record. People without an associated Organization are created as standalone contact Partners.

SalesSeek Deals map to Odoo crm.lead records with type='opportunity'. The Deal name becomes the Opportunity name, monetary value maps to planned_revenue, and expected close date maps to date_deadline. The linked Organization resolves to the migrated res.partner record; the linked Person resolves to the migrated res.partner contact. Stage probability percentages migrate to Odoo's stage probability values. Lost and won reasons from SalesSeek become custom Char fields on the Odoo Opportunity.

SalesSeek's multiple simultaneous pipelines map to Odoo crm.team (Sales Team) records, each with its own kanban stage configuration. Stage names, sequence order, and probability percentages migrate to Odoo's crm.stage records associated with each team. If SalesSeek pipelines represent different business units or product lines, each becomes a separate Odoo Sales Team with independent stage sets. Stage renaming post-migration requires manual review in Odoo Studio.

SalesSeek pipeline stages are configurable enumerations that map to Odoo crm.stage records. We preserve stage labels, sequence order, and probability percentages from SalesSeek as stage_name, sequence, and probability fields on crm.stage. The stage's pipeline association maps to the sales_team_id on crm.stage. Stage colors in SalesSeek do not have a direct Odoo equivalent and are noted for manual configuration post-migration.

SalesSeek custom fields on Organizations, People, and Deals require pre-creation in Odoo before migration. Text fields map to Char or Text depending on length; number fields map to Float or Integer depending on the SalesSeek type; date fields map to Date. We create each custom field via Odoo Studio or custom module XML during the schema preparation phase, then map values during the data migration phase. Field labels and help text are preserved from the SalesSeek custom field definition.

SalesSeek dropdown fields require explicit option mapping to Odoo selection fields or many2one relations depending on whether the options represent a fixed enumerated set or a dynamic reference list. We generate a dropdown mapping spreadsheet during scoping that lists each SalesSeek dropdown field name, its options, and the recommended Odoo field type. Fixed-option dropdowns become selection fields with the options list as the selection tuple. Reference-style dropdowns (e.g., source campaigns, industry verticals) may become many2one relations to dedicated Odoo models if the option list is large or grows over time.

SalesSeek Tasks map to Odoo mail.activity records with activity_type_id resolved to the standard 'To Do' type. Task subject becomes activity_title, due date maps to date_deadline, and status (open/completed) maps to activity subtype. Assigned user maps via email lookup to res.users. Tasks linked to specific Organizations, People, or Deals resolve to the migrated res.partner or crm.lead records via the Odoo res_id and res_model references. Completed tasks are migrated with their completion date preserved.

SalesSeek Groups (collections of records used for filtering and sharing) map to Odoo crm.team records if they represent sales team assignments, or to res.groups if they represent security or permission groupings. Group membership of individual users is preserved by mapping SalesSeek group members to the corresponding crm.team member list or res.groups inmembers. We export group definitions and recreate them as Teams or User Groups in Odoo based on the group's primary use.

SalesSeek Filters that are associated with a Group are exported during scoping and recreated as Odoo ir.filters records with the same domain expression, field list, and sort order. Filters that are not associated with a Group may have already been deleted by SalesSeek's cleanup process before migration begins; we identify these during scoping and note them as requiring manual recreation. Orphaned filter definitions without a Group association are documented separately for customer review.

SalesSeek engagement activities (call logs, meeting records, email metadata) map to Odoo mail.message records attached to the migrated record (res.partner or crm.lead) via res_id and res_model. Activity type, date, and notes migrate as mail.message fields. Call duration and disposition notes from SalesSeek become plaintext in the message body. Meeting location and attendee information migrate as mail.message fields. Activity records without a parent Organization or Person are attached to the highest-level relevant record.

File attachments associated with Organizations, People, or Deals are downloaded from SalesSeek and re-uploaded to Odoo as ir.attachment records linked to the migrated res.partner or crm.lead via res_id and res_model. The original filename, MIME type, and file content are preserved. Attachments are imported after the parent record exists in Odoo so that the ir.attachment res_model and res_id references are satisfied. Attachments exceeding Odoo's default attachment storage size may require storage configuration adjustment.

SalesSeek Tags are exported as tag names and re-created as Odoo crm.tag records. Tag assignments on Organizations, People, and Deals migrate as crm.lead.tag.rel entries for Opportunities or res.partner.category entries for Partners. Tags that exist in both SalesSeek and Odoo (from previous imports or default data) are matched by name to avoid duplication. Tags used for both company and contact records map to the appropriate tag relation table per record type.

SalesSeek Owners (users who own Organizations, People, Deals, and Tasks) map to Odoo res.users records via email address lookup. Any SalesSeek Owner without a matching Odoo User is placed in a reconciliation queue for the customer's Odoo administrator to provision before record import continues. Owner assignments on Deals and Tasks are set as Odoo responsible_id on crm.lead and mail.activity records respectively. Inactive SalesSeek users may be mapped to inactive Odoo users with notes for the admin to reactivate.

SalesSeek automation rules including drip email sequences, lead scoring logic, and task trigger automations are not accessible through the SalesSeek REST API. They cannot be exported or transferred programmatically. During scoping, we capture screenshots or conduct a walk-through session with the customer to document each automation's trigger conditions, delay rules, and actions. We deliver a written automation inventory document that describes each rule and provides a recommended Odoo Workflow or Server Action equivalent. The customer's Odoo administrator or an Odoo implementation partner rebuilds the automations post-migration; this is a manual effort that should be accounted for in project timelines.