Migrate from Vocus to HubSpot

Vocus.io contacts map directly to HubSpot contacts. The Vocus.io contact record holds name, email, phone, company name, and job title — all of which have native HubSpot equivalents. Vocus.io's company name stored on the contact record becomes a HubSpot company association rather than a text field. Owner resolution maps the Vocus.io user (by email) to the corresponding HubSpot user.

Vocus.io company records — name, domain, industry, phone, employee count — map to HubSpot company properties directly. Industry values in Vocus.io use a pick-list that maps to HubSpot's Industry pick-list. HubSpot company records can be merged if the migration discovers duplicate companies — FlitStack surfaces duplicates before the full import and applies a merge rule.

Vocus.io deals map to HubSpot deals. Each Vocus.io deal has a name, amount, stage, close date, and owner. The deal's stage value is mapped to a corresponding HubSpot deal pipeline stage. If Vocus.io uses multiple deal categories, each becomes a separate HubSpot deal pipeline. HubSpot's deal model supports multiple pipelines with custom stage sequences — this directly accommodates Vocus.io's deal organization.

Vocus.io snippets (text templates stored per user) are migrated as HubSpot email templates. The snippet body becomes the HubSpot template body; the snippet name becomes the template name. Vocus.io snippets can include {{contact.first_name}} style merge tags — FlitStack maps these to HubSpot's {{ contact.firstname }} token format during conversion. User-scoped snippets are consolidated into a shared HubSpot template library accessible to all CRM seats.

Vocus.io email sequences — the core product feature — cannot be extracted via API and do not have a HubSpot equivalent at the automation level. Each sequence step (trigger email, delay, conditional branch, follow-up email) must be rebuilt manually in HubSpot's workflow builder. FlitStack exports sequence logic as a documented rebuild reference, noting step order, delay intervals, and conditional rules, so HubSpot admins can reconstruct them in order.

Vocus.io tracks email opens, link clicks, and attachment opens per contact. This engagement history is migrated as custom contact properties in HubSpot — last_email_opened, last_link_clicked, email_open_count — rather than as individual engagement events, since HubSpot's engagement log is populated by its own email tracking extension and cannot be backfilled from an external source in the same data model.

Vocus.io Campaigns allow bulk personalized email sends with follow-ups and attachment support. These map to HubSpot lists (static or active) for segmentation and to HubSpot's Campaign object for reporting. A Vocus.io campaign with attached follow-up sequences requires the follow-up logic to be rebuilt as a HubSpot workflow enrolled from the associated list.

Vocus.io users (identified by email) are resolved to HubSpot users by email match. Vocus.io's team management (shared templates, reports, centralized billing on Professional) maps to HubSpot's user roles and permissions. Unmatched Vocus.io users — those without HubSpot seats — are flagged before migration and assigned to a fallback owner until seats are provisioned.

Files attached to Vocus.io contact records or deal records are downloaded and re-uploaded to HubSpot Files. HubSpot's file storage has a 250MB per-file limit. Files exceeding this limit are flagged and linked in a custom property pointing to the original source URL. Attachments are associated to the same HubSpot object (contact or deal) as in Vocus.io.

If Vocus.io is currently syncing contacts and deals to Salesforce via auto-BCC, those Salesforce records are a source of truth for some data but are not Vocus.io native records. The migration pulls from Vocus.io directly. Records that originated in Vocus.io and were forwarded to Salesforce carry Vocus.io's original create date — FlitStack preserves this as a custom property on the HubSpot record.