Migrate from Vtiger All-In-One CRM to HubSpot

Direct 1:1 map. Vtiger Contacts migrate to HubSpot Contacts preserving first name, last name, email, phone, job title, address fields, and custom properties. The assigned_to user is resolved by email match to a HubSpot user; unmatched owners are flagged before migration commits. Original Vtiger timestamps and the Vtiger internal ID are stored as custom properties for traceability and deduplication.

Direct 1:1 map. Vtiger Organizations migrate to HubSpot Companies, preserving organization name, website domain, industry (pick‑list values translated to HubSpot’s industry options), employee count, annual revenue, and address fields. Vtiger’s parent‑child hierarchy maps to HubSpot’s parent‑company lookup; each child references its parent by the parent’s HubSpot ID. The Vtiger internal organization ID is stored as a custom property for deduplication, and original create/modify timestamps are retained as custom properties.

Direct 1:1 map at the record level. Each Vtiger Potential becomes a HubSpot Deal. Vtiger pipeline names map to HubSpot pipeline names; Vtiger sales stage pick-list values map value-by-value to HubSpot deal stage options in the corresponding pipeline. Probability percentages, close dates, and amounts migrate with direct field mapping.

Direct 1:1 map per pipeline instance. Vtiger supports multiple simultaneous pipelines. Each Vtiger pipeline becomes a separate named HubSpot Pipeline. The migration plan includes HubSpot pipeline creation and stage definition before records land, so stage pick-list values are scoped correctly from day one.

Value-by-value pick-list mapping per pipeline. Each Vtiger stage label (e.g., Prospecting, Proposal, Negotiation, Closed Won, Closed Lost) maps to the matching HubSpot deal stage within its target pipeline. Vtiger's closed-won and closed-lost conventions map to HubSpot's Closed Won and Closed Lost stages. Stage-entered timestamps preserved as HubSpot custom properties if tracked in Vtiger.

Vtiger Leads merge into HubSpot Contacts rather than becoming a separate object, because HubSpot uses a single contact model with lifecycle_stage to distinguish prospect status. Vtiger Lead status (New, Assigned, Converted) maps to HubSpot lifecycle_stage values (subscriber, lead, MQL, SQL) by the migration team and confirmed in the test migration before the full run.

Direct 1:1 map. Vtiger Tickets (subject, description, status, priority, assigned support agent) map to HubSpot Tickets in a configured ticket pipeline. Vtiger ticket status values (Open, Wait, Pending, Closed) map to HubSpot ticket pipeline stages. Owner resolved by email match to HubSpot user. Original Vtiger ticket create date preserved as a custom property.

Vtiger Products and Services merge into HubSpot's Products object. Each unique Vtiger product record creates one HubSpot Product. Unit price and quantity from Vtiger Potential-line associations become HubSpot Line Items attached to the migrated Deal, referencing the pre-created HubSpot Product by name. Vtiger product category stored as a HubSpot custom property on the Product record.

Vtiger custom modules created through Vtiger Studio migrate to HubSpot Custom Objects, which are only available on HubSpot Enterprise plans. We validate that the destination HubSpot portal has the appropriate plan tier before committing to this mapping. Custom module associations (e.g., N:N junction tables) require HubSpot custom association types defined during the schema setup phase.

Vtiger Email, Calendar (Events), and Tasks map to HubSpot Engagements — emails as email engagements, meetings as meeting engagements, and tasks as task engagements. Original timestamps, associated contacts, and assigned owners are preserved. Vtiger note content migrates to HubSpot engagement notes with original create dates stored as custom properties.

Vtiger file attachments (documents, images, PDFs) associated with contacts, organizations, potentials, or tickets are downloaded and re-uploaded to HubSpot Files. The original filename and any Vtiger internal ID are preserved in the HubSpot file metadata. HubSpot's 250MB file size limit per upload is enforced during the migration run.

Vtiger Process Designer workflow definitions and workflow rules do not migrate to HubSpot because HubSpot's automation engine (Flows) operates on a different event-action model with different trigger types. We export the Vtiger workflow definitions as a structured JSON reference document so your HubSpot admin can rebuild the logic in Flow. Sequence and autoresponder definitions are included in the export.

Vtiger Quotes, Sales Orders, and Invoices have no direct HubSpot equivalent. We migrate these records as custom objects if the destination HubSpot plan supports them, preserving the line-item structure and totals. Alternatively, they can be archived as PDF attachments linked to the corresponding Deal. We recommend archiving over live migration for financial documents unless your team actively uses them inside HubSpot.