Migrate from Snapforce CRM to Odoo CRM

Snapforce Account records map to Odoo res.partner with company_type set to 'company'. The Account Name maps to the partner name, and address fields (street, city, state, zip, country) map to standard Odoo address fields. Website from Snapforce becomes website field on the Odoo partner. Parent record linkage is not applicable on the company side. Accounts are created before any Contact import so that the Contact-to-Account lookup is satisfied at the moment of Contact insert.

Snapforce Contact records map to Odoo res.partner with company_type set to 'contact' and parent_id pointing to the mapped Account partner. Email, phone, mobile, job title, department, and custom fields migrate directly. The 2-way mail sync relationship in Snapforce is replaced by Odoo's mail.thread on the partner record — imported email history is attached via mail.message records with message_type='email'. Contact-account linkage is resolved at migration time via the pre-created Account partner records.

Snapforce Lead records map to Odoo crm.lead with type='lead'. The lead's lifecycle stage and lead status properties from Snapforce map to Odoo's stage_id on the CRM pipeline. Any lead scoring or custom lead fields migrate to custom fields on crm.lead. Leads are imported before Opportunities so that the opportunity create-from-lead flow can reference the original lead record if the customer wants to preserve the conversion chain.

Snapforce Opportunities map to Odoo crm.lead with type='opportunity'. The Opportunity name maps to the lead name, amount maps to expected_revenue, probability maps to probability (with Snapforce stage probability transferred to Odoo's stage probability values), and close date maps to date_deadline. Snapforce pipeline stages map to Odoo CRM stages — we configure the Odoo pipeline stages before migration to match the exact stage names and probability assignments from Snapforce. The linked Account is resolved via the Account-to-res.partner mapping done in the first migration phase.

Snapforce VoIP call logs write duration, timestamp, and disposition to the Contact record, but the actual call recording audio and voicemail files are separate file objects stored on the Snapforce platform. We extract call metadata and audio files during discovery, preserve the Contact linkage by filename and contact email, and re-attach them to the corresponding Odoo res.partner record as ir.attachment documents. Call disposition and duration are written as a mail.message note on the Contact record for timeline visibility. This is a manual per-file association step scoped explicitly before migration begins.

Snapforce voicemails are stored per-user mailbox (500-voicemail cap per mailbox) and linked to Contact records by filename. We extract voicemail metadata and audio files, preserve the contact linkage by filename, and re-attach them to the target Odoo res.partner as ir.attachment records with res_model='res.partner' and res_id set to the migrated Contact partner ID. This requires the Contact migration to complete before voicemail re-association so that the target partner ID is known.

Snapforce Tasks map to Odoo mail.activity records linked to the parent crm.lead or res.partner. Task subject becomes activity summary, description becomes note content, due date maps to date_deadline, and task status maps to activity state (overdue, today, planned, done). Assigned owner resolution follows the User mapping phase. Tasks that were marked done in Snapforce appear as completed activities in Odoo's activity timeline.

Snapforce meeting records map to Odoo calendar.event entries. Meeting title, start time, end time, location, and attendee list transfer directly. Attendee resolution uses the User-to-partner mapping so that employee attendees appear as calendar.event attendee records linked to Odoo User partners. External attendee emails are preserved as email addresses on the event.

Snapforce Mailbox email threads auto-sync to Contact records and contain the full message content, headers, and thread linkage. We migrate each email as a mail.message with message_type='email' on the target res.partner record (for Contact emails) or crm.lead record (for lead emails). The from/to/cc fields map to mail.message email_from, email_to, and email_cc fields. Thread continuity is preserved by setting parent_id on subsequent messages in the same thread.

Snapforce Campaigns (available as an $8/user/month add-on) map to Odoo's utm.campaign for campaign tracking and crm.tracking.metric for email campaign performance data. Campaign membership (Leads and Contacts targeted by the campaign) maps to crm.lead line records with the campaign reference set. We verify during scoping that the customer has the Snapforce Campaigns add-on active before including this object — if not, the mapping is omitted from scope.

Snapforce Documents uploaded to Deals, Contacts, and Organizations migrate to Odoo ir.attachment records with res_model set to the corresponding Odoo model (crm.lead for Opportunities, res.partner for Contacts and Accounts) and res_id set to the migrated record ID. The document name, file content, and file type are preserved. Documents that were shared via Google Drive sync in Snapforce are exported to local storage first, then re-attached to Odoo records.

Snapforce custom fields are defined per-module and carry field labels, data types, and required/unique flags. We capture the full custom field schema during discovery for each module (Account, Contact, Lead, Opportunity). Custom fields are recreated in Odoo as ir.model.fields with matching labels and type-mapped field definitions — text fields become char or text, numeric fields become float or integer, date fields become date, etc. Snapforce field IDs are organization-scoped and non-portable; Odoo field IDs are generated at creation time and cannot be pre-specified. Any workflow rules or reports referencing Snapforce custom fields are documented separately for Odoo rebuild.

Snapforce User records carry role assignments and are tied to data ownership across all modules. We export the full user list and map each Snapforce Owner to an Odoo res.users record by email match. Owner-to-record linkage (OwnerId on Snapforce records) resolves to Odoo res.users id via this mapping. Any Snapforce Owner without a matching Odoo User is placed in a reconciliation queue — the customer provisions the Odoo user before record import resumes. In Odoo, data access is managed through access groups and record rules rather than per-owner assignment, so post-migration access configuration is required.