Migrate from Vtiger Sales to HubSpot

Vtiger Contacts map directly to HubSpot Contacts. The primary Organization link becomes the 'associated company' property on the HubSpot contact. FlitStack resolves the organization lookup before writing each contact so the association lands correctly. During migration, any missing organization reference is flagged so you can either create a placeholder company in HubSpot or update the Vtiger record before re-running the import.

Vtiger Organizations map to HubSpot Companies. Fields including account_name, website, industry, and employee count migrate directly. Parent-child organization hierarchies map to the HubSpot Parent Company field; circular references are flagged before migration. If a parent organization does not yet exist in HubSpot, FlitStack creates a temporary entry and links children after the parent is confirmed, ensuring the hierarchy is preserved without orphaning records.

Vtiger Potentials migrate to HubSpot Deals with deal name, amount, and close date preserved. The Vtiger sales_stage pick-list maps to HubSpot pipeline stages — each Vtiger stage value requires a corresponding HubSpot stage to be created in the target pipeline first.

Vtiger Help Desk tickets map to HubSpot Service Hub tickets. Status values (Open, Wait, Resolved, etc.) translate to HubSpot ticket status. Priority maps to the ticket priority property. Related contact and organization lookups attach to the HubSpot ticket via theAssociations API.

Vtiger Products migrate to HubSpot Products with product name, unit price, and currency preserved. If Vtiger uses multiple currencies, FlitStack maps them to HubSpot's single currency setting — you specify the target currency before migration. All product records also retain their original Vtiger product ID as a custom property to support audit trails and cross-referencing after migration.

Vtiger document attachments on Contacts, Organizations, Potentials, and Help Desk records are downloaded and re-uploaded to HubSpot Files. File size limits apply (HubSpot caps files at 20MB by default). Inline images in notes are extracted and rehosted separately. If a file exceeds the 20MB limit, FlitStack splits the upload into multiple chunks or alerts you to reduce the file size before retrying.

Vtiger stores emails as attachments on module records. FlitStack extracts email content and imports it as HubSpot engagement logs on the associated contact timeline. Subject, body, sender, and timestamp are preserved; email attachments migrate as separate files. The imported email logs appear under the 'Email' engagement type, allowing you to view them alongside calls, meetings, and notes on each contact's activity feed.

Vtiger call logs and meeting records migrate as HubSpot engagements on the contact timeline. Call duration, outcome, and meeting notes map to HubSpot's engagement properties. Original timestamps and owner assignments are preserved. Each engagement record also retains a link back to the original Vtiger record ID for audit and reconciliation purposes.

Custom Vtiger modules require HubSpot Enterprise custom objects. Each custom module needs a HubSpot custom object created with equivalent properties before migration. Associations between custom modules and standard objects map via HubSpot's association types. If your HubSpot portal is not on Enterprise, FlitStack will flag this limitation early so you can plan an upgrade or decide on an alternative consolidation strategy before migration begins.

Vtiger users resolve to HubSpot users by email match. Unmatched owners are flagged before migration — your team either creates HubSpot users first or assigns records to a fallback owner. Vtiger role-based access does not migrate; HubSpot permissions are configured post-migration.