Migrate from Touchpoint MX to HubSpot

Touchpoint MX contacts map directly to HubSpot contacts. First name, last name, email, phone, job title, and address fields map field-by-field. The contact's primary company resolves via the Touchpoint MX company_id association to a HubSpot company record that must exist first.

Touchpoint MX companies map to HubSpot companies. Name, domain, industry, employee count, and annual revenue carry over. Parent-child company hierarchies map to HubSpot's Parent Company field. Multi-company contacts in Touchpoint MX collapse to a primary company lookup plus HubSpot contact-company associations.

Touchpoint MX deal name, amount, stage, close date, owner, and priority map to HubSpot deal fields. The deal pipeline name in Touchpoint MX maps to a HubSpot deal pipeline. Stage probability values are applied per HubSpot pipeline stage definition properly.

Touchpoint MX orders do not have a direct HubSpot equivalent. We model each order as a HubSpot deal with a linked line item for the product and quantity. Order status and tracking fields migrate as custom properties on the deal. This preserves the order-to-product relationship while fitting HubSpot's data model.

Touchpoint MX delivery records include delivery ID, status, date, carrier, and tracking number. Since HubSpot has no native delivery object, we map delivery data as custom properties on the associated deal (the order deal), or create a HubSpot custom object for delivery tracking if the volume warrants it — your team chooses before migration runs.

Touchpoint MX products with name, SKU, price, and description map to HubSpot products. Products are created in HubSpot first so that line items on deals can reference them via product_id lookup. Without an existing HubSpot product, the line item stores price and quantity directly.

Touchpoint MX custom fields on attendees (text, rating, choice types) migrate as HubSpot custom properties. Each custom field requires a corresponding property to be created in HubSpot Settings before migration. The field type maps: Touchpoint choice → HubSpot single-checkbox or radio; rating → HubSpot number; text → HubSpot single-line text.

Exhibitor lead custom fields in Touchpoint MX map to HubSpot custom properties on either the Company or Contact object, depending on whether the exhibitor is organization-scoped or person-scoped in your Touchpoint MX setup. We determine the target object during the field-mapping planning phase before migration.

Touchpoint MX notes with title, body, and creator map to HubSpot engagement notes on the associated contact, company, or deal record. Original created timestamps are preserved in HubSpot's engagement timestamp. Attachments are downloaded and re-uploaded to HubSpot Files for future reference.

Touchpoint MX users and owners are matched to HubSpot users by email address. If a Touchpoint MX owner has no matching HubSpot user, records are assigned to a designated fallback owner and flagged for your team to resolve before or after migration.

Files attached to contacts, companies, deals, orders, or deliveries in Touchpoint MX are downloaded and re-uploaded to HubSpot Files, associated to the corresponding CRM record. HubSpot's 25MB per-file limit applies; larger files are flagged before migration to ensure compliance with limits.