Migrate from VBOUT to Microsoft Dynamics 365 Sales

VBOUT Contacts with a lead score above the customer's defined threshold (typically 20+) map to Salesforce-style Dynamics 365 Lead. Unqualified Contacts with no lead score or zero score map to Dynamics 365 Contact. We compute the split at migration time using VBOUT's leadscore property and any associated Tags indicating pipeline stage. The original VBOUT lead score migrates to a custom field vb_lead_score__c on both Lead and Contact for audit. VBOUT Contacts without email addresses are flagged in a separate reconciliation report because Dynamics 365 requires an email on Lead or Contact records.

VBOUT Leads map directly to Dynamics 365 Lead. The lead score, source attribution (utm_source, utm_medium), and assignment data preserve in standard Lead fields (LeadScore, LeadSource, OwnerId). Any VBOUT Tags on the Lead record migrate to a custom multi-select picklist field vb_tags__c so that segment context is visible inside Dynamics 365 without rebuilding the Smart Audience logic.

VBOUT Smart Audiences are dynamic segmented lists based on behavioral and demographic criteria. The segmentation rules export as a JSON definition but do not transfer as a live segment. We document each Smart Audience's filter logic (field, operator, value, AND/OR connectors) and produce a step-by-step rebuild guide for Microsoft Dynamics 365 Sales using Advanced Find queries or Power Automate-based audience lists. The customer recreates the active segments in Dynamics 365; historical membership data is preserved as Tags on the Contact or Lead records for reference.

VBOUT Tags export as a flat list per record. Tags containing pipeline stage or lead status context (e.g., stage-qualified, funnel-top, churned) map to a Dynamics 365 multi-select picklist field vb_segment_tags__c for filtering and reporting. Tags used for campaign classification map to Dynamics 365 Topics with TopicAssignment records. The customer selects the tag strategy during scoping.

VBOUT custom fields on Contacts and Leads require type-aware mapping to Dynamics 365 field types. VBOUT dropdown fields map to Dynamics 365 Option Sets; conditional fields map to calculated fields or business rules; payment fields map to Decimal or Currency fields on the Opportunity object. We pre-create the destination custom field schema in the Dynamics 365 solution before import begins. Date fields use the ISO 8601 format accepted by Dataverse. Phone fields use E.164 format where available in source data.

VBOUT pipeline stages stored as Tags on Deals map to Dynamics 365 Opportunity Stage values. We extract every distinct pipeline stage name from VBOUT Tags, map each to a Dynamics 365 StageName value, and configure the corresponding Sales Process in the Dynamics 365 solution before migration. Stage order, probability percentages, and description text transfer. The customer configures any stage color coding in Dynamics 365 post-migration.

VBOUT Deals map to Dynamics 365 Opportunity. The VBOUT deal amount maps to Amount, close date maps to CloseDate, owner maps to OwnerId via email resolution against the Dynamics 365 User table, and Tags indicating pipeline stage map to the StageName via the stage configuration step above. Any VBOUT Deal custom fields map to custom Opportunity fields pre-created in the destination schema.

VBOUT email campaign records (subject, send date, open rate, click rate) export as CSV. The email body content is available for export but must be manually re-created in Dynamics 365 or Power Automate templates. We deliver a structured CSV with all campaign metrics so that Power BI reports can be rebuilt against the imported data. The email body HTML does not transfer as a reusable template in Microsoft Dynamics 365 Sales without manual rebuild.