Migrate from matrix to HubSpot

Direct object-to-object map. HubSpot contacts store all standard properties (name, email, phone, address) as native fields. Custom properties from Matrix that share a name with an existing HubSpot property (e.g. industry) map directly; others create new HubSpot custom properties. The contact's original create date is preserved as a custom datetime property since HubSpot Createdate is set at import time.

Direct object map. HubSpot companies store name, domain, industry, phone, and address as native fields. Matrix company hierarchies (parent-child relationships) are preserved using the HubSpot parent company association. Multi-company associations on a single contact are handled via HubSpot's Associations API after the primary company link is set.

Direct object map. HubSpot deals are called Opportunities in the underlying object model but are exposed as Deals in the UI. The Matrix deal name maps to Deal name, amount to Amount, close date to Close date, and owner to Owner. The deal's pipeline field from Matrix maps to a HubSpot deal pipeline — one Matrix pipeline equals one HubSpot pipeline.

Matrix pipeline names become HubSpot deal pipeline names. Each pipeline in Matrix requires a corresponding pipeline to be created in HubSpot before migration. Stage values from Matrix are mapped to stage names in the destination pipeline, with probability and forecast category re-applied based on HubSpot pipeline settings.

Matrix custom fields migrate as HubSpot custom properties. If a Matrix custom field name matches an existing HubSpot property name exactly, the mapping uses the HubSpot native field. Non-matching custom fields create new HubSpot custom properties. Field types are translated: Matrix text/number/date/pick-list/boolean map to HubSpot string/number/date/select/boolean property types respectively.

Matrix call logs migrate as HubSpot calls, appearing in the contact timeline. The original call timestamp, duration, outcome, and owner are preserved as HubSpot call properties. HubSpot call records are linked to the contact record via the association API. All original metadata is retained during the transfer.

Matrix email logs migrate as HubSpot emails, appearing in the contact timeline. The original email subject, body, direction (sent/received), and timestamp are preserved. HubSpot email records are linked to the contact record. Note that HubSpot's email tracking (via the sales email extension) is a separate feature and is not enabled by the migration.

Matrix meeting records migrate as HubSpot meetings, appearing in the contact timeline. The original meeting title, start/end time, location, and body are preserved. HubSpot meeting records are linked to the contact and optionally the deal record for comprehensive activity tracking.

Matrix notes migrate as HubSpot notes. The original note title, body, create date, and owner are preserved. HubSpot notes appear in the contact and company timeline and can be associated with deals. Rich-text formatting is preserved where supported, and any embedded file references are migrated as attachments.

Matrix file attachments are downloaded and re-uploaded to HubSpot Files. Each file is associated with the record it was attached to (contact, company, or deal) via HubSpot's file association API. HubSpot's file storage limits apply per plan tier, so verify your plan's storage allowance before migration.

Matrix owner IDs are resolved by email address against HubSpot users. If a Matrix owner email matches an existing HubSpot user, the deal and contact are assigned to that user. Unmatched owners are flagged before migration; the team either invites them to HubSpot first or reassigns their records to a fallback owner.

Matrix workflows and automation rules do not migrate to HubSpot. HubSpot has its own workflow engine that must be configured separately. We export Matrix workflow definitions as a JSON reference document so your HubSpot admin can rebuild them in HubSpot's workflow builder. Workflow export is included in the migration deliverables.