Migrate from Visionary to HubSpot

Visionary contact records map directly to HubSpot contacts. The primary company association in Visionary becomes the primary company link in HubSpot. Records are de-duplicated on email address to prevent re-importing existing contacts already in HubSpot. During the mapping process, we verify that each contact's associated company exists in HubSpot or create it as part of the company migration batch before linking the contact record.

Visionary company records map 1:1 to HubSpot company records. Company name, domain, industry, employee count, and annual revenue transfer directly. Parent-child company hierarchies in Visionary map to HubSpot's parent company field using the same hierarchical relationship. We validate that parent company records are migrated before child records to maintain the proper hierarchical structure in HubSpot.

Visionary deals map directly to HubSpot deals. Deal name, amount, close date, and owner transfer as-is. Deal stage in Visionary is mapped value-by-value to HubSpot pipeline stages, with probability and forecast category reapplied on the HubSpot side based on your target pipeline configuration.

Stage names in Visionary are mapped to the corresponding HubSpot pipeline stage names. Each pipeline stage gets assigned a probability and forecast category in HubSpot. Stage-entry timestamps are preserved as HubSpot custom datetime fields if the source data includes them.

If Visionary supports multiple named pipelines, each Visionary pipeline becomes a separate HubSpot pipeline with its own set of stage names and probabilities. Single-pipeline Visionary instances map to the HubSpot default pipeline. We create the pipelines in HubSpot before data loads to ensure stage mappings resolve correctly.

Emails logged in Visionary migrate as HubSpot email engagements on the associated contact timeline. Subject, body content, direction (sent/received), and original timestamp are preserved. Attachments are downloaded and re-uploaded to HubSpot Files. Email engagement metadata including open and click tracking data is stored as custom properties in HubSpot where Visionary provides this information in the export.

Call records in Visionary migrate as HubSpot call engagements attached to the contact record. Call duration, direction, timestamp, and outcome (if present in Visionary) transfer. Notes logged with the call become HubSpot call body content. Call recordings associated with the call record are downloaded and re-attached to the HubSpot call engagement where the Visionary export format supports this attachment.

Visionary meetings map to HubSpot meeting engagements with original start time, end time, title, and body preserved. Meeting links and conference identifiers are stored as custom properties on the meeting record so they remain accessible in HubSpot. Attendee information from Visionary meetings is transferred to the HubSpot meeting engagement where supported by the export format.

Notes in Visionary migrate as HubSpot notes on the associated contact, company, or deal timeline. Rich-text formatting is preserved where Visionary's export format supports it. Timestamps and owner attribution are carried over so the activity history reads as a continuous record.

Visionary owner IDs are resolved by matching the owner's email address to HubSpot user records. Unmatched owners are flagged before the migration runs so your HubSpot admin can either invite the user to HubSpot or reassign records to a fallback owner. No record lands in HubSpot without a resolved owner.

Visionary custom fields are analyzed by data type (text, number, date, pick-list). HubSpot custom properties are created in the target portal with matching types before data loads. Pick-list custom fields in Visionary require value-by-value mapping to HubSpot pick-list options during the migration planning phase.

Files attached to Visionary records are downloaded and re-uploaded to HubSpot Files. They are then associated with the corresponding contact, company, or deal record. File size limits apply (HubSpot's default per-file limit is 25MB). We handle renames to avoid collisions when multiple records share the same filename.