Migrate from Sales Snap to Odoo CRM

Sales Snap Contact records map to Odoo res.partner with is_company=False. Name, email, phone, and custom fields migrate directly from CSV. The parent company is resolved by matching Sales Snap company_name against the Odoo partner created from the Companies export (deduped by name). Lifecycle stage from Sales Snap maps to a custom Char field x_lifecycle_stage on res.partner because Odoo has no native equivalent. Contacts without a matched company parent are created as standalone partners and flagged for manual review.

Sales Snap company records map to Odoo res.partner with is_company=True. Multiple Sales Snap contact rows referencing the same company name are deduplicated on company name during the transform phase and merged into a single Odoo partner record with is_company=True. All individual contact records are then linked to this parent partner via parent_id. Company-level fields (domain, industry, employee count if present in the export) migrate as custom fields on the res.partner record.

Sales Snap Owner records are matched to Odoo res.users by email address during import. Any Owner without a matching Odoo user is held in a reconciliation queue. The customer's Odoo admin provisions missing users before the record import phase resumes. Sales Snap does not export owner records as a standalone object; owner is a field on each contact, company, and task row, so we extract distinct owner emails first.

Sales Snap sequence campaign data has no native Odoo CRM equivalent. We map sequence name and step order to crm.lead tag_ids using the sequence campaign name as the tag value, with step order stored in the lead description field as a reference string. The full sequence template (email subject, body, personalization tokens, delay rules) is documented in a written handoff inventory and delivered to the customer for manual rebuild in Odoo's CRM automations. This is a reference-data migration, not an automation migration.

Sales Snap follow-up tasks map to Odoo project.task records. Task type, due date, completion status, and linked contact migrate directly. Orphaned tasks (no linked contact in the Sales Snap export) are imported as standalone tasks with a note flagging the missing parent. We create a default project in Odoo (CRM Tasks) to host all imported tasks; if the customer uses the Project module, tasks are routed to the appropriate project during scoping.

Sales Snap email engagement logs (opens, clicks, replies) aggregate per contact as metrics in the CSV export. We map these to Odoo mail.message records with mail_activity_type=False and a custom body field carrying the engagement summary. The original email content (subject, body) is not separately exported from Sales Snap; if the customer has exported email templates separately, those are noted as reference files for manual re-upload to Odoo.

Sales Snap call logs migrate to Odoo project.task with the display_name prefixed by Call:, duration stored in x_call_duration (seconds), and call outcome stored in x_call_disposition. The linked contact is resolved via the res.partner parent record. Call recording URLs in Sales Snap are not exported in the standard CSV; we flag any record containing a recording URL as a separate line item for manual retrieval.

Sales Snap meeting engagements map to Odoo calendar.event. Start datetime, end datetime, location, and meeting title migrate. Attendee resolution uses the res.partner records linked to the meeting contact. Sales Snap meeting notes migrate to the event description field. If multiple contacts attended a single meeting in Sales Snap (as separate rows), we create one calendar.event per contact to preserve individual attendance records.

Sales Snap lifecycle stage values (new, active, churned, etc.) from the contact export are mapped to Odoo crm.stage records per CRM team. We create stage records in Odoo before any lead import and map each Sales Snap lifecycle value to a corresponding Odoo stage. The stage sequence order and probability percentages are set during Odoo CRM configuration. If Sales Snap exposes additional pipeline metadata in exports, we extend the mapping to crm.lead.stage_id and x_original_lifecycle_stage.

Sales Snap custom fields visible in the CSV export are mapped 1:1 to Odoo custom fields on the res.partner model. We pre-create the custom fields in Odoo using field types that match the Sales Snap export column type: text columns become Char or Text, date columns become Date, picklist values become Selection fields. Any field requiring type conversion (for example, a Sales Snap datetime column importing into an Odoo Date field) is flagged for explicit customer approval before the transform runs.

If the customer's Odoo instance runs multiple companies, we map Sales Snap data to the appropriate res.company by matching a company identifier in the Sales Snap export against the destination Odoo company records. Single-company Odoo setups ignore this mapping. We confirm the multi-company configuration during scoping because it affects the company_id field on every partner and lead record.

Sales Snap engagement metrics per contact (total opens, total clicks, total replies, last contact date) are not native Odoo fields. We store the aggregate counts as custom fields on res.partner: x_total_email_opens, x_total_email_clicks, x_total_replies, and x_last_engagement_date. Individual engagement events (per-email opens) are not available in the standard Sales Snap export and are noted as a data gap in the scoping document.