Migrate from Spin CRM to Odoo CRM

Spin CRM Companies map to Odoo res.partner records with partner_type set to 'company'. The company name maps to name, address fields map to street, city, state, country, and any industry custom field maps to a custom res.partner field. We export Companies first to establish the relationship anchor used by Contacts during the second export pass. Odoo's res.partner record serves as both company and person depending on the is_company flag, which we set to True for all migrated Companies.

Spin CRM Contacts map to Odoo res.partner with partner_type set to 'person' and parent_id pointing to the corresponding Company res.partner via name-based lookup after the Company pass. Email, phone, job title, and any custom contact fields migrate directly. The contact-to-company link is preserved by resolving the Spin CRM company association to the Odoo res.partner parent record.

Spin CRM Leads map to Odoo crm.lead records directly. Standard lead fields (name, email, phone, company_name, description) migrate as crm.lead name, email_from, phone, partner_name, and description. The Spin CRM lead status maps to Odoo's crm.lead stage_id (New, Qualified, Proposal, Negotiation, Won, Lost). Any Spin CRM custom fields on Leads map to custom fields on crm.lead.

Spin CRM Deals map to Odoo crm.lead records with type='opportunity' after the Lead pass. Deal name becomes crm.lead name, deal value becomes planned_revenue, owner becomes user_id via email match, expected close date becomes date_deadline, and the Spin CRM pipeline stage becomes crm.lead stage_id. Spin CRM's custom deal fields migrate to custom fields on crm.lead.

Spin CRM's fully customizable pipeline stages are extracted during scoping as a named list with stage order and probability values. Each stage becomes a crm.stage record within the Odoo sales team's pipeline. Stage names are preserved verbatim. Probability values map to Odoo stage probability percentages. If Spin CRM uses multiple pipelines, each becomes a separate Odoo sales team with its own stage sequence.

Spin CRM task management and calendar/reminder records map to Odoo mail.activity. Activity type, subject, due date, and assigned owner migrate. Odoo's mail.activity model includes an activity_type_id that maps from Spin CRM's task category. Owner resolution uses email match against Odoo res.users. We attempt this mapping based on the CSV column headers available in the exported file.

Spin CRM notes and meeting records map to Odoo mail.message (body content linked to crm.lead) for notes and calendar.event for meetings. Meeting records carry start, end, location, and attendee data. Spin CRM notes without a date/time component become mail.message records with a note subtype. The parent crm.lead is resolved via the Spin CRM record ID cross-referenced during the Deal/Lead import pass.

Spin CRM owner assignments (on Leads, Contacts, Deals, Activities) map to Odoo res.users records via email address matching. We extract the distinct owner list from all exported objects before migration and match against the Odoo destination's user list. Any Spin CRM owner without a corresponding Odoo user is placed in a reconciliation queue; the customer provisions the missing users before the production migration begins.

Spin CRM custom fields on Leads, Contacts, and Deals require pre-creation in Odoo before import. We identify custom field names and types from the Spin CRM export column headers during scoping, create matching Odoo custom fields (via Settings > Technical > Custom Fields for Enterprise or direct database/model work for Community), then reference them during import. Custom field types (text, date, integer, selection, boolean) are type-matched to Odoo field definitions. If Spin CRM exports omit a custom column, we flag and request a re-export with all columns selected before proceeding.

Spin CRM document storage is not migratable through any documented export mechanism. We do not attempt to migrate document blobs from Spin CRM. We flag document existence and suggest the customer download critical files manually before the freeze window. In Odoo, documents attach via ir.attachment linked to the migrated crm.lead or res.partner record. This step is outside standard migration scope and requires customer-side action.

Spin CRM forecast data is derived from deal values and stage probabilities. We extract deal values from the Deal export pass and apply the mapped stage probability percentages from the Odoo stage configuration to produce forecast projections. The Odoo Forecast reporting view recalculates these automatically from migrated crm.lead records, so no separate forecast object migration is required.

If Spin CRM manages a product catalog visible in the Deal export (line items, SKUs, prices), those records map to Odoo product.product. Product name, SKU (product.default_code), and list_price migrate directly. Price list and vendor associations in Spin CRM become Odoo seller_ids on product.product.