Migrate from Vocus to Salesforce Sales Cloud

Vocus Snippets are reusable text blocks scoped by plan tier (50/100/200/800). We export Snippets as formatted plain text or HTML content and map them to Salesforce EmailTemplate records. Template type maps to Salesforce's Text, HTML, or Custom (with merge fields) variants. Vocus merge field syntax is normalized to Salesforce merge field syntax during transformation. Snippets above the current plan tier are flagged during scoping and archived rather than migrated to avoid incomplete imports.

Vocus Followup sequences are one-to-one email cadences with configurable delay rules (e.g., follow up in 2 days, then 4 days, then 1 week). We reconstruct these as Salesforce Tasks with a sequential chain using Task.WhatId and a custom NextStep field to encode the cadence logic. Each Followup step becomes a Salesforce Task record; the sequence order is preserved using a custom sort order field. Salesforce Sales Cloud Engagement (an add-on) provides a native Cadence feature that more closely mirrors Vocus sequences; we document the mapping to that feature if the customer licenses it.

Vocus Campaigns are personalized bulk email sends with attachments and branded URL tracking. We export campaign definitions (subject, body, recipient list, send date) and map them to Salesforce Campaign records. Campaign type, status, and budgeted cost are populated from Vocus campaign metadata. Recipient lists are mapped to Salesforce CampaignMembers; the customer chooses whether to import recipients as Leads or Contacts based on their Salesforce data model.

File attachments included in Vocus Campaigns are downloaded during export and uploaded to Salesforce as Document records (for Classic) or ContentVersion/ContentDocument records (for Lightning) linked to the parent Campaign. We preserve the original file name and MIME type and attach to the Campaign using ContentDocumentLink with a Visibility setting of AllUsers.

Vocus open and click tracking events per-recipient are not independently exportable via API. We export what is available through the Gmail connector and aggregate campaign reporting metrics as CSV. This CSV is attached to the Salesforce Campaign record as a Document and the open/click counts are stored in custom Campaign fields for reporting purposes. Real-time tracking events are not reconstructed as individual Salesforce records because Vocus does not expose this data in an exportable format.

Vocus does not maintain a native contact database. It surfaces Gmail contacts and syncs activity to Salesforce via auto-BCC. We source contact records from the customer's Gmail contacts export (Google Takeout) or from the existing Salesforce org directly. Contacts already present in Salesforce from the auto-BCC sync are identified by email address match and are not re-imported. We never double-count contacts between Vocus and Salesforce because the source of truth for contacts is Gmail or the existing Salesforce org, not Vocus itself.

Vocus connects to Gmail and G Suite inboxes via OAuth. We map each connected inbox to the corresponding Salesforce User record by email address match. The Gmail inbox serves as the owner reference for email activity extracted during migration. Users without a matching Salesforce User record are held in a reconciliation queue for the customer's admin to provision before activity import.

Vocus Teams share analytics, templates, and billing under a central account. We map Team members to Salesforce User records by email address. Team-level analytics are exported as CSV and documented as a reference for the customer's admin to recreate as Salesforce Reports and Dashboards post-migration.

The Vocus auto-BCC integration writes email activity to Salesforce Contacts and Pipedrive Deals. Since this data already exists in Salesforce, we cross-validate it against the Gmail sent-mail archive to confirm completeness. Any gaps (emails written by Vocus but not present in Gmail export) are flagged. We do not re-import data that already exists in Salesforce; we flag it as validated.

The auto-BCC CRM sync means that email activity tied to contacts and deals already exists in Salesforce. We do not migrate these records from Vocus; we validate them against Gmail exports and document any discrepancies. The migration scope covers Vocus-native objects (Snippets, Followups, Campaigns) and any activity that exists in Gmail but was never written to Salesforce by the auto-BCC sync.

Vocus does not expose a custom objects or custom fields API. The platform has no equivalent to Salesforce custom objects. We cannot migrate custom field definitions or values from Vocus because this data does not exist in a transferable format. If the customer has built any workaround data structures (e.g., Snippet naming conventions that encode custom data), we document these during scoping and advise the customer on Salesforce equivalents.

Real-time open and click tracking events are logged per-recipient in Vocus but are not independently exportable via API. We extract what is available through the Gmail connector export and log tracking event summaries as CSV files attached to the relevant Salesforce Campaign record. Individual tracking event records are not reconstructed as Salesforce objects because Vocus does not expose this granularity in an exportable format.