Migrate from Vocus to Microsoft Dynamics 365 Sales

Vocus Snippets (reusable text blocks stored at 50/100/200 per plan) export as formatted plain text or HTML content. We map them to Dynamics 365 Email Template records, preserving the Snippet body as template body text and the Snippet name as template title. Snippets with merge field placeholders are noted and mapped to Dynamics template merge field format during migration. Tier limit checks happen during scoping: Snippets above the current plan limit are flagged and either archived or migrated selectively based on customer priority.

Vocus Followup sequences (automated one-on-one cadences with delay rules and message content) are exported as structured content defining the cadence order, delay in days, and message body. Microsoft Dynamics 365 Sales does not natively replicate Vocus Followup sequences without the separate Sales Engagement license. We deliver a written inventory of every active sequence with step order, delay, and content so the customer's admin can rebuild them as a task queue in Dynamics or a Power Automate flow. No live sequence is migrated as a Dynamics Sales Sequence because that feature requires additional licensing.

Vocus personalized bulk email campaigns with branded URL tracking export as Dynamics 365 Campaign records (Campaign Name, Description, Status) for structural continuity. Campaign definitions and reporting metrics (opens, clicks, send volume, attachment usage) export as CSV and are delivered alongside the migration as a reference document. Dynamics 365 Marketing or Sales Engagement is the proper replacement for ongoing campaign execution and tracking; we do not migrate campaign automation logic.

Vocus open and click tracking events are extracted through the Gmail connector export and mapped to Dynamics 365 Note records or custom activity fields on the relevant Contact or Account. We preserve open timestamp, click URL, and recipient as structured fields because Vocus does not expose these as API-accessible records. Cross-validation against Gmail sent mail ensures completeness when the Vocus browser extension has been unstable. Activity timeline ordering is preserved by setting the Note Created On date to the original tracking timestamp.

Vocus connected Gmail inboxes map to Dynamics 365 User records by email match. Each inbox owner becomes a Dynamics User with their Email field populated from the Gmail address. Owner resolution happens before any record migration because OwnerId is a required reference on most Dynamics standard objects. Users without a matching Dynamics User account are held in a reconciliation queue for the customer's admin to provision.

Vocus Teams share analytics, templates, and billing under a central account. Team members map to Dynamics 365 User records within a Dynamics Team, preserving the shared workspace structure where the team owner is the primary User and members are secondary Users with appropriate security roles assigned during migration.

File attachments included in Vocus Campaigns are downloaded during export and reattached as Notes or SharePoint document references in Dynamics 365, linked to the corresponding Campaign or Account record. We preserve original filenames and attachment size metadata. SharePoint integration must be enabled in Dynamics 365 before migration; if not yet configured, attachments land as Notes attachments as a fallback.

Vocus does not maintain a contacts or leads database. Contacts are surfaced through Gmail and synced via the auto-BCC CRM integration. We source contact records from the Gmail contacts export or the destination CRM directly rather than from Vocus, which eliminates double-counting. Migrated contacts land as Dynamics 365 Contact records with email, name, phone, and company fields populated from the Gmail contact export. Any existing Lead records in Dynamics are preserved; new Leads from Gmail contacts are created only where the customer requests a full Lead-to-Contact lifecycle.