Migrate from Vocus to Twenty CRM

Vocus OAuth-connected Gmail inboxes map to User records in Twenty by email match. We extract the connected account list from Vocus during scoping and resolve each to a Twenty User. Any inbox without a matching Twenty User goes to a reconciliation queue for the customer to provision the account first. Owner assignment on migrated records (tasks, campaigns) uses this lookup.

Vocus Snippets are reusable text blocks stored at the plan tier limit (50/100/200/800). We export Snippets as formatted text records and map them to Twenty Note records attached to the relevant People or Company, or to a workspace-level Template if the customer uses Twenty's template feature. We preserve the Snippet name, body content, and category tag. The plan-tier count is validated during scoping to flag any Snippets that exceed the destination tier limit.

Vocus Followup Sequences define one-to-one email cadence with delay rules and message content. We reconstruct these as a series of Twenty Task records with sequential due dates calculated from the original delay configuration. Each step in the sequence becomes a Task with the original message content stored in the Task description. The sequence owner maps to the User lookup via the Gmail inbox owner. We flag Followup count against the current Vocus plan (50/100/500) during scoping; records above the tier limit are archived rather than migrated.

Vocus personalized bulk email Campaigns with attachments and branded URL tracking are exported as Campaign definition records (name, audience, send date, subject) mapped to Twenty Campaign objects. Campaign reporting metrics (opens, clicks, bounces, unsubscribes) do not have a native Twenty equivalent and are delivered as a structured CSV export with campaign-level and per-recipient rows, attached to the Twenty Campaign record. The customer references the CSV for campaign performance analysis.

Vocus open and click tracking events are logged per-recipient for sent emails. These events are not independently exportable via API. We extract what is available through the Gmail connector export (sent mail archive cross-referenced with Vocus tracking data) and log them as completed Task records in Twenty with the original send timestamp and a description noting the tracking event type. The Gmail sent-mail archive is the primary source; Vocus tracking data validates which emails had opens and clicks.

File attachments included in Vocus Campaigns are downloaded during export and attached to the corresponding Twenty Campaign record. We preserve original file names and MIME types. Attachments are stored in Twenty's file management system linked to the Campaign.

Vocus does not maintain a contact database. We source contact records from the customer's Gmail contacts export (Google Takeout or contacts.google.com export). People records are created in Twenty with name, email, phone, and address fields mapped from the Gmail contact schema. If the Gmail contact includes a company association, we create or match the corresponding Company record first to satisfy the People-Company lookup.

The Vocus auto-BCC CRM integration writes email activity to Salesforce Contacts or Pipedrive Deals. This is a write-through from Vocus to the destination CRM, not a data store inside Vocus. We do not migrate from this integration layer. If the customer has existing Salesforce or Pipedrive data, that data migrates directly from those platforms using their APIs, not from Vocus. Contact records are sourced from Gmail contacts export.

Vocus does not support custom objects or custom fields. There is no Vocus-native schema for custom record types to migrate. If the customer needs custom objects in Twenty, we provision them as part of the destination schema setup during migration, but the source data for those objects must come from another system (Gmail contacts, a separate data export, or the customer's records). This is scoped separately.

Vocus Teams share templates, analytics, and billing under a central account. We map Team members to Twenty User records by email match, preserving the shared workspace membership structure. Billing information does not migrate. If the Team has multiple connected Gmail inboxes, each maps to its respective User owner as described above.