Migrate from X2CRM to HubSpot

Direct map. X2CRM contact fields map to HubSpot contact properties. Names, email, phone, job title, and social URLs transfer as-is. X2CRM contact status maps to a custom HubSpot property for lifecycle continuity — the actual lifecycle stage routing is handled separately based on business rules.

X2CRM contacts with status set to 'customer' route to HubSpot contacts with lifecycle_stage mapped to 'customer'. Other status values map to 'lead' or 'other' via value-mapping rules agreed upon during the migration plan review. We also preserve the original X2CRM status value in a custom HubSpot property, and any unmapped status values receive a default 'lead' assignment. The mapping table is stored in the migration workbook for future reference.

Direct map. X2CRM accounts map to HubSpot companies. Company name, website, industry, employee count, and annual revenue transfer to the corresponding HubSpot company properties. X2CRM parent-account hierarchy maps to HubSpot's parent company association. During migration we validate each parent-account link and flag orphaned accounts for your team to resolve before the load. If X2CRM accounts contain additional address fields, those map to HubSpot company address properties.

Direct map. X2CRM opportunities map to HubSpot deals. Deal name, amount, stage, probability, and close date transfer. Owner resolves by email match to HubSpot users. X2CRM's pipeline and stage names map to HubSpot deal pipeline and stage via value mapping agreed with your team.

X2CRM product links on opportunities require Products to be migrated to HubSpot first, then Line Items created linking each product to the corresponding HubSpot deal. This sequencing matters — Products must exist before Line Items can reference them. After Products load, we run a validation pass to verify each product's HubSpot ID before Line Items creation, and any unresolved product references are flagged for cleanup before deal migration.

Direct map. X2CRM cases map to HubSpot tickets. Subject, status (open/closed), priority, type, and description transfer to the corresponding HubSpot ticket fields. HubSpot ticket pipelines and ticket stages map from X2CRM case status via value mapping. Any custom case fields that do not match a standard HubSpot ticket property become custom ticket properties, and we validate that status transitions align with your HubSpot pipeline stages before the load.

Direct map. X2CRM products migrate to HubSpot products. Product name, SKU, price, and description transfer. If HubSpot Products are not active in your HubSpot tier, Line Items and products migrate as HubSpot custom objects. During migration we verify that each product's SKU is unique, flagging duplicates for your team to resolve before the load. Product images and custom attributes that lack a HubSpot counterpart become custom product properties.

HubSpot engagements (calls, emails, meetings) preserve original timestamps, owners, and associated contact links. X2CRM notes migrate as HubSpot notes attached to the corresponding contacts. Subject, body, and creation date transfer. Original engagement content is preserved verbatim, and any inline attachments are downloaded and re‑uploaded to HubSpot Files, linked back to the originating contact or deal.

X2CRM file attachments re-upload to HubSpot Files attached to the corresponding records. Inline images in notes download and rehost. File size limits apply per HubSpot's platform constraints — files over HubSpot's limit are flagged before migration so your team can decide on storage strategy.

X2CRM custom fields that have no direct HubSpot equivalent create HubSpot custom properties during migration. Custom properties use HubSpot's internal naming conventions and data types. Pick-list custom fields in X2CRM map to HubSpot option-based properties with values preserved. During the planning audit we document each custom field's data type, default value, and validation rules, and generate a custom‑field mapping table for your admin to review before the load.

X2CRM workflows and X2Flow automations do not migrate. We export your X2Flow definitions as a structured reference document (JSON) so your HubSpot admin can rebuild equivalent logic in HubSpot Workflows. This export is delivered as part of the migration package and includes a mapping of triggers, actions, and conditions to guide the rebuild. Admin should plan for rebuild effort after the data migration completes.

X2CRM owner and user records resolve by email match against HubSpot users. Unmatched owners are flagged before migration so your team can either invite them to HubSpot or assign a fallback owner. No record lands without a valid HubSpot owner.