Migrate from Sellsation CRM to Odoo CRM

Sellsation Customers (account-level records with company information, address, and industry) map to Odoo res.partner records with partner_type set to 'company'. We preserve the Sellsation Customer name as partner display name, address fields as address child records, and any industry or classification data as Odoo custom tag fields. Customer is imported before Contact Persons to satisfy the partner_id lookup on the contact-side import.

Sellsation Contact Persons map to Odoo res.partner records with partner_type set to 'person' and parent_id pointing to the linked Customer partner record. We resolve the parent link at migration time by matching Contact Person's customer reference to the imported Customer record, then insert Contact Persons with parent_id populated. Email, phone, and role/title data migrate to standard partner fields; custom fields map to Odoo custom ir.model.fields.

Sellsation Sales Projects (pipeline-stage-tracked deals with values and phase history) map to Odoo crm.lead records with type='opportunity'. The Sellsation pipeline stage name becomes the Odoo stage_id reference, which we configure as a named stage in the target CRM pipeline before migration. Deal value migrates to Odoo's expected_revenue or planned_revenue field. The traffic-light stagnating-deal flag migrates as an Odoo tag (crm.tag) so sales managers can filter neglected opportunities in Odoo's pipeline view.

Sellsation Activity records (calls, appointments, notes, tasks) linked to Contact Persons or Sales Projects map to Odoo mail.activity entries on the corresponding res.partner or crm.lead record. We batch activities by parent object and chronological window to avoid Odoo request-timeouts on high-volume timelines. Appointment records with date, time, duration, and attendees map to Odoo calendar.event with calendar.event.type set to the Sellsation activity type label. Activity timestamps and user assignments migrate as activity_date_deadline and create_uid respectively.

Sellsation multi-level campaigns (combining emails, letters, conditional stage movements, and task creation) do not have a single Odoo equivalent. We export campaign structure, enrollment data, and stage movement rules as a written inventory. Email-based campaign steps migrate to Odoo mail.mass_mailing with audience lists rebuilt from the Sellsation campaign member records. Automated task-creation steps migrate to Odoo crm.activity.plan entries. Conditional stage movements require manual rebuild in Odoo Studio or via a consultant because Sellsation's campaign logic does not export as machine-readable rules.

Sellsation Tasks assigned to Contact Persons or Sales Projects map to Odoo project.task if the customer uses Odoo Project, or to mail.activity on the parent crm.lead or res.partner if only CRM is deployed. Task status, due date, description, and assignment (user_id) migrate directly. We resolve Sellsation user assignments by email match against Odoo res.users; any unresolved assignments go to a reconciliation queue for the customer's admin to provision.

Sellsation custom fields on Customers, Contact Persons, and Sales Projects are enumerated during scoping and mapped to Odoo custom ir.model.fields. We pre-create the Odoo field schema (with correct field type: char, selection, text, float, date, etc.) before any data import. Picklist-style custom fields migrate as Odoo selection fields with matching key-value pairs; formula or computed fields cannot be migrated and are flagged in the scoping report for manual rebuild in Odoo Studio.

Sellsation geo map and heatmap data stores territory and region context as internal map state rather than standard geographic coordinates. We export the linked Sales Project location data as standard address fields (street, city, zip, country) on the associated Customer partner record. The geographic context is preserved in address form even though the native heatmap visualization cannot be replicated. If the customer requires territory visualization, Odoo Map plugin or a third-party Odoo App provides basic pin-plotting on partner addresses.

Sellsation standard reports and custom KPI dashboards do not export as definitions. We deliver the underlying Sales Project, activity, and deal-value data as structured CSV exports so the customer's Odoo team can rebuild reports from complete source data. Pipeline performance reports, deal aging reports, and sales activity summaries are among the highest-priority rebuilds identified during scoping.

Sellsation user assignments on Contact Persons, Sales Projects, Activities, and Tasks map to Odoo res.users records. We resolve by email match against the destination Odoo instance's user table. Any Sellsation owner without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId references are required on most crm.lead fields.

Each Sellsation pipeline stage name becomes a named crm.stage record in Odoo's CRM pipeline configuration. We capture stage order, probability percentage (where set in Sellsation), and stage type (new, working, won, lost) from the Sales Project phase change history. The Sellsation traffic-light stagnating-deal logic is not a stage property; it migrates as a tag on records that exceeded the stagnation threshold.

Sellsation captures survey responses attached to Contact Persons as part of the activity history. We export survey question and answer pairs as structured records linked to the Contact Person partner. In Odoo, survey responses are handled by the Odoo Survey module, which is not part of a standard CRM-only deployment; we map survey data to mail.message notes or to a custom Odoo field depending on whether the customer licenses Odoo Survey.