Migrate from Vocus to Nutshell

Vocus Snippets (reusable text blocks scoped 50/100/200/800 by plan tier) export as formatted text records. We map Snippets to Nutshell email templates, preserving text content, merge field placeholders, and any category tags. Snippets without merge fields become signature or boilerplate templates in Nutshell. The mapping is straightforward because both systems store templates as named text records with no structural schema dependency beyond the owner.

Vocus Followup sequences (automated one-to-one follow-ups with configurable delays) cannot migrate as a native automation because Nutshell has no equivalent Vocus-style cadence engine. We reconstruct each Followup as a sequence of Task records with ActivityDate timestamps set to the original delay intervals, preserving the message content and delay logic as task descriptions. The customer receives a written Followup inventory documenting the original cadence for rebuild in Nutshell Tasks, Pipedrive Smart Email, or a dedicated sales engagement tool.

Vocus Campaigns (personalized bulk email with branded URLs and open/click tracking) export as Campaign definitions plus recipient-level tracking metrics as CSV. We map Campaign definitions to Nutshell Campaign records, preserving Campaign name, status, and description. Recipient lists migrate to Nutshell People records with source campaign attribution stored in a custom field. Historical open/click tracking events export as CSV and attach as a linked report to the Nutshell Campaign record because Nutshell Campaigns track member status and sent count rather than individual engagement events.

Vocus real-time open and click tracking events are logged per-recipient but are not independently exportable via API. We extract tracking event data through the Gmail connector export where available, and reconstruct activity records as Nutshell Task or Email records linked to the recipient People record. TheNut timeline in Nutshell displays these as logged activities. Customers who need granular per-recipient engagement history after migration should enable Nutshell's email tracking or integrate a dedicated email engagement layer.

Vocus OAuth-connected Gmail inboxes map to Nutshell user accounts by email address. Each connected Vocus inbox represents one sales agent or shared team inbox. We map the inbox owner to the corresponding Nutshell User record, preserving the email address as the primary identifier. Shared inboxes without a single named owner map to a generic Nutshell User record designated as a shared mailbox during migration scoping.

Vocus Teams share analytics, templates, and billing under a central account. We map Team members to Nutshell User records and assign them to the corresponding Nutshell Team or leave them as ungrouped users depending on the Nutshell plan. Nutshell Teams are available on Professional and Enterprise plans and control shared pipeline visibility and reporting access.

The Vocus auto-BCC CRM sync writes email activity OUT to Salesforce Contacts and Pipedrive Deals but does not store those records inside Vocus. We do not migrate from this integration layer because the authoritative data lives in the destination CRM. We instead source contact, account, and deal records from the destination CRM directly, ensuring no duplicate records are created. Email activity already written to Salesforce or Pipedrive via auto-BCC is cross-referenced against the Nutshell migration target to avoid overwriting existing activity logs.

File attachments included in Vocus Campaigns download during export and attach to the corresponding Nutshell Campaign record or to individual recipient People records depending on attachment scope. Nutshell stores file attachments linked via its standard attachment model. We map campaign-linked attachments to Nutshell file records attached to the Campaign object or to the relevant People record.