Migrate from Vocus to Zoho CRM

Vocus connects to Gmail and G Suite inboxes via OAuth but does not expose an API for the inbox itself. We map each connected inbox to a Zoho CRM User record, using the Gmail address as the username and the user's display name from Vocus as the Zoho User name. If a Vocus inbox maps to a Zoho User who does not yet exist, the customer's admin provisions the Zoho User before the migration phase. The connected-inbox count from Vocus determines how many Zoho User licenses are required post-migration.

Vocus Snippets (reusable text blocks, 50/100/200 depending on plan) map to Zoho CRM Email Templates. We export Snippet title, body content, and any variable placeholders, then create Zoho Email Template records under the Templates module. Variable placeholders are preserved as plain text with [FIELD_NAME] notation rather than converted to Zoho CRM merge fields, since the field resolution logic differs between platforms. The customer reviews Email Templates in a Zoho sandbox before production migration.

Vocus Followup sequences define a multi-step cadence of emails with configurable delay rules (e.g., send follow-up A in 2 days if no reply). Zoho CRM has no direct Followup sequence object. We reconstruct each sequence as a series of Zoho Tasks and Events with ActivityDate set to the computed delay from the original sequence trigger, and we preserve the sequence content in the task description field. This gives the customer a written record of their cadence inside Zoho CRM. Actual sequence automation requires rebuild in Zoho Workflow Rules post-migration; we provide the written sequence map for the admin to use.

Vocus personalized bulk email Campaigns (available on Starter $10/user and above) define audience, subject, body, attachments, and branded URL tracking. We export campaign definitions as structured records and map them to Zoho CRM Campaigns. Campaign audience contacts map to Zoho CRM Contacts and Leads, with the original Vocus contact email used as the dedupe key. Campaign reporting metrics (open rate, click rate) from Vocus export as a CSV that we import as a Zoho CRM custom field set on the Campaign record rather than into native analytics, since Zoho's campaign analytics model differs from Vocus's campaign tracking model.

Vocus tracks opens and link clicks per recipient on tracked emails. These events have no independent export via API. We extract email engagement data from the connected Gmail sent-mail archive and the Vocus Gmail connector export, then create Zoho CRM Task records with call_type = Email for each tracked engagement event. Each Task links to the relevant Zoho CRM Contact or Lead via WhoId. Where open and click data cannot be fully extracted, we flag the gap in the scoping report and note it as a limitation of the migration.

Vocus stores file attachments per Campaign. We download campaign attachments from Vocus (customer-provided access or manual export) and upload them as Zoho CRM Attachments linked to the corresponding Campaign record via the Related To field. Attachment file names and MIME types are preserved. Attachments exceeding Zoho's file size limits are flagged during scoping and uploaded to Zoho WorkDrive as an alternative if the customer requires.

Vocus Teams share templates, analytics, and billing under a central account. We extract team member names and email addresses from the Vocus team workspace and map them to Zoho CRM User records. Each User receives the appropriate Zoho profile based on their team role. Shared analytics from Vocus (campaign performance by team member) cannot migrate into Zoho CRM Reports in structured form but can be appended to the migration deliverable as a structured CSV.

Vocus does not expose a custom objects or custom fields API. The platform has no schema API we can query for custom definitions. Any customer-specific custom fields used in Snippets or Followup sequences must be identified manually by the customer and re-created in Zoho CRM by the admin. We flag this as a manual preparation step in the scoping phase and do not include custom field recreation in the standard migration scope.

Vocus does not maintain a contacts or leads database. It surfaces Gmail contacts and syncs with CRM contacts via the auto-BCC integration, but there is no Vocus-native contact record to export. We source contact records from the customer's Gmail contacts export or the destination Zoho CRM directly rather than from Vocus. If contacts are already present in Zoho CRM, no duplication occurs. If contacts are not yet in Zoho CRM, the customer provides a Gmail contacts export or other source file for import.

The Vocus auto-BCC integration writes email activity to Salesforce Contacts and Pipedrive Deals. This integration layer does not store records inside Vocus itself. Migration from this integration layer means exporting from the destination CRM directly (Salesforce or Pipedrive) rather than from Vocus. We do not include CRM-to-CRM migration in this migration scope unless specifically contracted.