Migrate from Vocus to HighLevel

Vocus Snippets (reusable text blocks stored at 50/100/200 depending on plan) export as formatted plain text and map to GoHighLevel Email Templates. Each Snippet's title becomes the Template name and the body becomes the HTML/text content. Placeholder tokens like {{first_name}} in Vocus Snippets migrate as GoHighLevel contact merge field syntax {{contact.first_name}}. We preserve any Snippet category tags as template tags in GoHighLevel for segmentation during the review phase.

Vocus automated Followup Sequences with configurable delay rules and message content do not migrate as executable code. GoHighLevel Workflows use a different trigger model (record-triggered, time-based, or form-submission) that requires rebuilding. We document each Vocus Followup Sequence as a written brief: trigger conditions, step count, delay between steps, message content, and a recommended GoHighLevel Workflow trigger equivalent. The customer's admin rebuilds Workflows using the documented brief post-migration.

Vocus personalized bulk email Campaigns with attachments and branded link tracking export as Campaign definitions (name, audience size, send date, subject, body) plus performance metrics as CSV. We import Campaign names and content as GoHighLevel Campaigns with associated Email Templates. Campaign performance metrics (opens, clicks, unsubscribes) are documented in CSV format for manual entry into GoHighLevel campaign reporting by the customer's admin.

Vocus open and click tracking events are extracted through the Gmail connector export and mapped to GoHighLevel Contact activity records. Each tracked email event becomes a note entry on the Contact timeline with the event type, timestamp, and campaign attribution. We preserve the email subject and recipient as context. Where the Gmail connector fails (extension instability), we cross-validate against Gmail's sent-mail archive to ensure completeness.

Vocus connected Gmail inboxes map to GoHighLevel User records. The inbox owner email becomes the User email, and the inbox display name becomes the User display name. We resolve the GoHighLevel User ID before importing any activity records to satisfy the owner lookup on Contact and Campaign attribution.

Vocus Team members with shared analytics and template access map to GoHighLevel Users within the same Agency account. Each Vocus Team member email is matched to a GoHighLevel User by email. If a Vocus Team member has no corresponding GoHighLevel User, they are added to a provisioning queue for the customer's admin to resolve before activity attribution imports.

Vocus auto-BCC writes email activity OUT to Salesforce and Pipedrive but does not store records IN. There is no Vocus-native contact data to migrate from this integration layer. We source contact records from Gmail contacts export or from the destination GoHighLevel account directly, ensuring contacts are never double-counted. If the customer maintains an active Salesforce or Pipedrive instance, we can run a parallel extraction from that system.

File attachments included in Vocus Campaigns download during export and upload to GoHighLevel as Documents. We link each Document to the corresponding migrated Campaign record using GoHighLevel's document-campaign association. Attachment filenames and MIME types are preserved for audit.