Migrate from Vocus to Odoo CRM

Vocus connected Gmail accounts map to Odoo res.users with the mail integration configured via IMAP or Odoo Discuss OAuth. Each Vocus user account becomes an Odoo user whose sent email is tracked through the mail.mail and mail.message tables. We preserve the Vocus user email address and display name; we configure IMAP sync settings in Odoo so that Gmail activity flows into Odoo's activity timeline rather than requiring a browser extension.

Vocus Snippets (reusable text blocks scoped at 50/100/200 depending on plan) map to Odoo mail.template records. We export Snippet content as the mail.template body field, Snippet title as template name, and apply formatting preserved as HTML. If the Odoo instance does not have the email marketing module, Snippets map to ir.actions.server records or stored in a Notes document for rep use. We flag Snippets exceeding the target plan limit for customer review before import.

Vocus Followup sequences with delay cadences and message content map to Odoo mail.activity records linked to crm.lead (opportunity) or res.partner. Each Vocus Followup step becomes a separate activity with an activity_type_id, user_id (assigned owner), and date_deadline offset computed from the sequence start date plus the Vocus delay. We preserve the message body as activity note, and we flag sequence counts against the source Vocus plan limit during scoping to identify any records that exceed tier limits and require customer decision on archiving.

Vocus personalized bulk email Campaigns map to Odoo utm.campaign records with campaign name, start date, and target audience preserved. Campaign reporting metrics (open rate, click rate, delivery rate) export as CSV and are delivered alongside the migration as a reference document because Odoo's native campaign reporting uses mail.mass_mailing which requires the email marketing module. File attachments from Campaigns download and are re-uploaded to Odoo document.attachment linked to the utm.campaign record.

Vocus real-time open and click tracking events are not independently exportable via API. We extract what is available through the Gmail connector export and map tracking event summaries to mail.message records attached to the relevant crm.lead or res.partner. Detailed per-recipient tracking data that cannot be extracted programmatically is documented in the CSV campaign report delivered with migration. Open and click timestamps are preserved in mail.message fields where available.

Vocus Teams share analytics, templates, and billing under a central account. We map Team members to Odoo res.users records and preserve team structure using Odoo access groups (res.groups) so that shared Snippets and Campaigns remain accessible to the same set of users post-migration. Shared billing information does not migrate; this is an Odoo account administration task.

Vocus auto-BCC integration writes email activity to Salesforce and Pipedrive but does not store records in Vocus. We do not migrate from the Vocus integration layer. Instead, we export email activity directly from the connected Gmail account using Gmail API or IMAP export and map sent emails to mail.mail records in Odoo, preserving the same activity timeline the auto-BCC was writing to the previous CRM.

File attachments included in Vocus Campaigns are stored in Vocus and downloaded during export. We preserve these as document.attachment records in Odoo, linking each file to the corresponding utm.campaign record via the res_model and res_id fields. Attachment filename, mime_type, and file size are preserved. Files over 10 MB are flagged for the customer to host externally and reference via URL field.

Vocus does not maintain a contacts database; it surfaces Gmail contacts. We source contact records from the connected Gmail account export (Google Contacts API or CSV export) and map them to Odoo res.partner. Individual contacts use partner_type = contact; company records use partner_type = company. Email address is the dedupe key. We map phone, company name, job title, and address fields to their Odoo equivalents.

Vocus browser extension settings (signature blocks, tracking domains, snippet folders, notification preferences) have no direct Odoo equivalent and do not migrate. We deliver a configuration checklist for the customer's admin to reconfigure email signatures in Odoo res.partner (partner_id field), set up tracking domains in Odoo's email alias configuration, and organize Snippet content inside mail.template folders.

Vocus does not expose custom objects or custom fields API. The platform has no equivalent to CRM custom records. We cannot migrate custom field definitions or values from Vocus because they do not exist in Vocus. If the customer has extended Vocus data through Google Sheets or third-party integrations, those extensions migrate as CSV imports to Odoo ir.ui.menu or custom models built by the customer's Odoo developer.

Vocus does not maintain a contacts or leads database. There is no Vocus-native contact record to migrate. We source all contact data from the connected Gmail account export and map Gmail contacts to Odoo res.partner. For leads that are not yet customers, we create crm.lead records in Odoo with partner_id left null until the lead is qualified, at which point the crm.lead converts to a res.partner following the Odoo standard Lead-to-Opportunity conversion workflow.