Migrate from Variable Soft CRM to HubSpot

Variable Soft CRM's contact and lead records map directly to HubSpot Contacts. HubSpot uses a single contact object rather than splitting leads and contacts — all source records land as HubSpot Contacts regardless of their Variable Soft CRM record type. The original source record type is preserved as a custom property.

Variable Soft CRM company or account records map to HubSpot Companies. HubSpot's company object supports N:N associations with contacts — if Variable Soft CRM stores multiple company associations per contact, we migrate one as the primary company and surface the rest via HubSpot's company associations feature.

Variable Soft CRM deal or opportunity records map to HubSpot Deals. The source deal name becomes the HubSpot deal name, amount maps to deal amount, and close date maps to close date. Each Variable Soft CRM deal pipeline maps to a corresponding HubSpot deal pipeline.

Variable Soft CRM pipelines become HubSpot deal pipelines. If Variable Soft CRM supports multiple pipelines with different stage sets per pipeline, we create a matching HubSpot pipeline structure. Each pipeline stage in Variable Soft CRM maps to a corresponding stage in the target HubSpot pipeline with stage order preserved.

Variable Soft CRM activity records — calls, emails, meetings, and notes — map to HubSpot Engagements. Call activities become HubSpot call engagements, emails become email engagements, meetings become meeting engagements, and notes become note engagements. Original timestamps and the associated contact or deal are preserved.

Variable Soft CRM user and owner records are resolved by email match against HubSpot users. If a Variable Soft CRM owner has an email address matching an existing HubSpot user, records are assigned to that HubSpot user. Unmatched owners are flagged before migration — teams either invite them to HubSpot or assign records to a fallback owner.

Variable Soft CRM custom fields across contacts, companies, and deals are evaluated against HubSpot's existing property set. Properties with direct equivalents (same data type and semantic meaning) map automatically. Properties without a HubSpot equivalent require a custom property creation in HubSpot before the migration runs — FlitStack includes this in the pre-migration schema plan.

File attachments stored against Variable Soft CRM contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files attach to the corresponding HubSpot record via the file associations API. HubSpot's file size limit applies — files exceeding the limit are flagged for manual handling.

Variable Soft CRM task records map to HubSpot Tasks. During migration we map the task title to HubSpot's task subject, the due date to the due date property, and the status to the task status field. The original contact or deal association is transferred using HubSpot's association API, and owner assignment relies on email lookup against HubSpot users.

If Variable Soft CRM stores product or line-item records associated with deals, these map to HubSpot Line Items. The product name becomes the line item's name property, unit price maps to the amount field, and quantity maps to the quantity property. Each line item is linked to the corresponding HubSpot deal using the deal-to-line-item association, preserving the relationship across platforms.