Migrate from VBOUT to HubSpot

VBOUT contacts migrate to HubSpot contacts with all standard properties (email, firstname, lastname, phone, jobtitle) mapped directly. VBOUT custom contact properties become HubSpot custom properties. Original create timestamps are preserved in Original_Create_Date__c for reporting continuity. During migration, we validate field data types to ensure compatibility between VBOUT and HubSpot property schemas, handling format conversions where needed such as date/time standardization or numeric field precision.

VBOUT tags serve two purposes: static segmentation labels and behavioral flags. We map frequently-used tags (over 100 contacts) to HubSpot contact properties as multi-select pick-lists for immediate visibility on each contact record. Low-frequency tags migrate as HubSpot list memberships for reference without cluttering the property schema. The tag inventory report shows usage counts for each tag so your team validates the mapping strategy before migration commits.

VBOUT's built-in lead scoring translates to a custom numeric property (Lead_Score__c) on HubSpot contacts. The numeric score value from VBOUT is preserved in the custom field, enabling the same segmentation logic for lead prioritization. HubSpot's native HubSpot Score property is available on Sales Hub Professional and above tiers, providing an alternative scoring mechanism if your team prefers HubSpot's own scoring algorithms.

VBOUT companies map to HubSpot companies with direct field mapping for name, domain, industry, employee count, and annual revenue. HubSpot company properties use snake_case naming (domain, numberofemployees) matching VBOUT conventions. Additional VBOUT company fields that have no direct HubSpot equivalent become custom properties, with a property creation checklist delivered before migration runs.

VBOUT parent-child company relationships map to HubSpot's Parent Company field. Circular references where Company A points to B and B points back to A are flagged during migration planning and resolved by collapsing to the root company in the hierarchy. This prevents invalid parent-child loops in HubSpot's company association model.

VBOUT deals migrate to HubSpot deals with deal name, amount, close date, owner, and stage mapped directly. VBOUT deal custom fields become HubSpot deal custom properties, preserving all custom data points your team has tracked in VBOUT. Owner resolution uses email matching against HubSpot users, with unmatched owners flagged for fallback assignment before the full migration run.

VBOUT pipeline stage names map to HubSpot deal stage names value-by-value per pipeline. Stage probability percentages migrate as custom fields (Stage_Probability__c) since HubSpot stages carry default probabilities that may differ from VBOUT's custom values. Each stage name and its corresponding probability are documented in the pipeline configuration plan for HubSpot setup.

VBOUT email activities, calls, and meetings map to HubSpot engagements. Original timestamps, owners, and subject lines are preserved. HubSpot's engagement timeline surfaces these activities on the contact and company record pages, providing your team with a complete communication history from VBOUT visible in the HubSpot CRM interface.

VBOUT workflows (visual automation builder flows) do not migrate. We export the workflow definition as a JSON specification including triggers, conditions, and actions for your HubSpot admin to rebuild in HubSpot's Workflows tool. Workflow logic cannot be automatically translated between platforms.

VBOUT email campaigns including templates, send history, and subject lines do not migrate automatically. We export template content as HTML files ready for re-import into HubSpot's email template manager. Campaign send history and open/click engagement data remain available in VBOUT's analytics export for historical reference.

VBOUT users resolve to HubSpot users by email address. Unmatched owners are flagged with their unassigned record count before migration. Teams can invite unmatched users to HubSpot or assign their records to a designated fallback owner before the full run.

VBOUT custom fields on contacts, companies, and deals require HubSpot custom properties to be created before migration. We deliver a custom property creation checklist specifying field name, type (text, number, date, picklist), and whether it accepts multiple values. VBOUT picklist values map to HubSpot picklist options value-by-value.