Migrate from Onpipeline to HubSpot

Onpipeline People map 1:1 to HubSpot Contacts. The organization's Company link in Onpipeline becomes a HubSpot Company association via the primary company lookup. If the contact has no organization, it lands as a standalone HubSpot Contact with no CompanyId. We preserve the Onpipeline person ID as a custom property for traceability.

Onpipeline Organizations map directly to HubSpot Companies. Company name, domain, website, industry, employee count, and annual revenue all migrate to HubSpot's matching native fields. When Onpipeline contains multi-level parent/child organization hierarchies, those relationships transfer to HubSpot's parent Company association feature to maintain the original structure.

Onpipeline Deals map to HubSpot Deals with deal name, amount, currency, and close date preserved directly. The Onpipeline deal stage name is stored in a HubSpot custom text property (Deal_Stage_Source__c) so original stage labels are not lost. Pipeline association is resolved by mapping the Onpipeline Pipeline to a HubSpot Deal Pipeline.

Onpipeline Pipelines define the sales process; each Pipeline contains Stages. We map each Onpipeline Pipeline to a HubSpot Deal Pipeline and each Stage to a HubSpot Deal Stage value within that Pipeline. Stage order and probability weights need HubSpot-side configuration before migration. If Onpipeline has more than 15 stages in a single pipeline, Enterprise HubSpot access is required.

Onpipeline custom fields on People are read from the API and mapped to HubSpot Contact properties. If a matching HubSpot property exists (by name or API label), data writes directly. Otherwise, we create the property in HubSpot before the migration run. Required vs. optional flags are respected. Multi-select picklist values in Onpipeline map to HubSpot checkbox or multi-checkbox properties.

Onpipeline deal-level custom fields migrate to HubSpot Deal properties using the same approach as contact custom fields. We scan Onpipeline's field schema via API, match by name, and create missing HubSpot properties before migration. Data type is preserved: text → string, number → number, date → date, picklist → picklist.

Onpipeline Activity records are distributed to HubSpot's corresponding activity types. Calls become HubSpot Calls, tasks become HubSpot Tasks, notes become HubSpot Notes, and emails become HubSpot Email records. Original timestamps, owners (via email match), and parent record associations are preserved. Activity type and subject are mapped to HubSpot's type/subject schema.

Onpipeline Quotes with e-signature and line-item data do not map to a HubSpot native object. We export the quote data (line items, totals, contact link, status) as a structured CSV reference for rebuilding in HubSpot Quotes or a third-party quoting tool. The deal association is preserved in the export so the quote can be relinked during rebuild.

Onpipeline Products and inventory records map to HubSpot Products (SKU, name, price, cost). Inventory stock levels are stored as a custom number property on the HubSpot Product since HubSpot Products object does not natively track real-time inventory quantities. Recurring revenue subscriptions map to HubSpot Associations with a custom deal type.

Onpipeline user records are matched to HubSpot Users by email address. Unmatched users are flagged before migration; your team either invites them to HubSpot first or assigns their records to a fallback HubSpot owner. Owner ID in Onpipeline deals and activities is resolved to a HubSpot OwnerId via this email match.