Migrate from Snovio to Odoo CRM

Snovio Prospects with no deal association or early-stage outreach status map to Odoo Lead. Prospects with an associated pipeline Deal and explicit company affiliation map to Odoo Contact linked to a Company (Odoo partner). The split rule is computed during migration using the Snovio deal_id field: if deal_id is populated, the record becomes a Contact under the mapped Company; if deal_id is null, it becomes a Lead. We preserve the original Snovio prospect_id as a custom field snv_prospect_id__c on both Lead and Contact for reconciliation.

Snovio Company fields (name, domain, industry, size) map to Odoo res.partner records with type=contact for individual contacts and type=company for organization records. The Snovio company domain becomes the partner's website field and serves as the dedupe key during import. We create company records before contact import so the Contact-to-Company lookup relationship is satisfied at insert time.

Snovio Deals map to Odoo crm.lead records with type=opportunity. Deal name becomes the opportunity name; deal amount maps to planned_revenue; deal stage maps to stage_id with stage probability set from Snovio stage metadata. Owner assignment maps via email match to Odoo res.users. Deals without a linked company create an opportunity with partner_id = null pending company assignment.

Snovio Campaigns do not map to a single Odoo object because Odoo CRM does not have a native campaign concept for outbound sequencing. We map campaigns to Odoo Tags (crm.tag) on the Lead and Contact records, preserving campaign name and channel (email or LinkedIn) as tag metadata. If the customer uses Odoo Marketing Automation, we document the mapping to campaign model and recommend rebuilding Snovio email sequences as Odoo Marketing Automation actions. Active Snovio campaign status is not carried; all migrated leads are set to New status.

Recipients (unique leads who received at least one email) map to the same Lead or Contact record as the Prospect split. We export recipient status (active, bounced, replied) and preserve it as a custom field snv_recipient_status__c. Engagement history (opens, clicks, replies, sentiment) is exported but flagged as unreliable per Snovio's own documentation; we carry the raw timestamp data as Notes rather than structured analytics.

Snovio campaign KPIs (delivered, bounced, opened, clicked, replied counts) are not native Odoo CRM metrics. We map these to custom Opportunity fields (delivered_count, bounced_count, opened_count, clicked_count, replied_count) as integer fields on crm.lead so the data is available for reporting even though Odoo has no native campaign statistics view. The customer can visualize these in Odoo Custom Reports or via a spreadsheet export.

Snovio connected mailboxes and warm-up configurations are documented as metadata rather than migrated as live credentials. We export the list of connected sender accounts, warm-up rotation settings, and daily warm-up volume as a JSON configuration file. The customer's admin re-creates the SMTP servers in Odoo Settings > Technical > Email > Outgoing Mail Servers using the same credentials. OAuth token migration is not supported by Snovio's API.

Unibox reply metadata (sender email, timestamp, thread reference) migrates to Odoo mail.message records linked to the parent Lead or Contact via model and res_id. Full email body content is not migrated because threading context is not reliably extractable from Snovio's export. We carry the message subject, timestamp, and sender as a Note with a snv_unibox_ref__c external ID field. Customers who need full email threading should retain Snovio access or export email bodies manually.

Snovio custom fields on Prospects export as part of the Prospect schema export. We pre-create matching custom fields on Odoo crm.lead, res.partner, and crm.lead (opportunity) via Odoo Studio or direct XML-RPC field creation before data import. Field types are mapped: Snovio text to char, Snovio number to float, Snovio date to date, Snovio dropdown to selection, Snovio checkbox to boolean. Custom field API names prepend snv_ to avoid collisions.

LinkedIn message sequences and connection request records (available only on the $69/month add-on) export as structured metadata: LinkedIn profile URL, sequence step reached, connection status. We map these to Odoo Contact tags (linkedin_connected, linkedin_sequence_active) and a Note containing the LinkedIn profile URL and last activity timestamp. LinkedIn DMs do not migrate as Odoo records; the actual conversation content is not accessible via Snovio's export API.

Snovio campaign owners and deal owners map to Odoo res.users by email match. We extract every distinct owner across Prospects, Deals, and Campaigns and resolve against the destination Odoo instance's user list. Owners without a matching Odoo user are held in a reconciliation queue for the admin to provision before record import. Inactive Snovio owners map to inactive Odoo users by default.

File attachments to prospect profiles or campaign emails are not exposed via Snovio's documented export endpoints. We do not migrate attachments. Customers should download prospect-related files manually from Snovio before account cancellation and re-upload to Odoo via the portal or file management module. We provide a list of prospect IDs with attachment references as a separate download checklist.