Migrate from UPNIFY CRM to HubSpot

Upnify contacts map directly to HubSpot contacts. Owner assignment resolves by email match to existing HubSpot users. Contacts without a primary company in Upnify land as HubSpot contacts with no company association — a HubSpot admin then links them manually or via association rules.

Upnify companies map to HubSpot companies. Company hierarchies (parent-child) in Upnify map to HubSpot's parent company association. Multi-company contacts collapse to the most recently modified company as primary, with secondary companies surfaced via HubSpot's association model.

Upnify opportunities map to HubSpot deals. The deal name, amount, close date, and owner transfer directly. Pipeline association maps to a named HubSpot pipeline. Stage names require value-by-value mapping since Upnify's free-form stage names must align with HubSpot's stage pick-list.

Upnify pipeline stages map to HubSpot deal pipeline stages. Each Upnify stage name gets a corresponding HubSpot stage pick-list value in the selected pipeline. Stage probability and forecast category are reapplied from HubSpot's pipeline configuration. Stage-entered timestamps in Upnify are preserved as HubSpot custom datetime properties for reporting continuity.

Upnify quotes transfer as HubSpot deal properties when the quote fields map directly to deal fields (amount, name, expiry). Full quote line items migrate as a custom object linked to the deal, or as deal-level custom properties if the quote structure is simple. Complex quote layouts require manual rebuild in HubSpot's quoting tools.

Upnify tasks map to HubSpot tasks. Original due dates, task subject, body, owner, and completion status transfer. Tasks linked to a specific contact or deal in Upnify maintain that association in HubSpot via record ID linking.

Upnify call logs, meeting records, and email activities migrate as HubSpot engagements. Original timestamps, owners, and parent-record associations (contact ID or deal ID) are preserved. HubSpot's engagement timeline surfaces these in the contact and deal record pages.

Upnify custom fields on contacts that have no direct HubSpot equivalent migrate as HubSpot custom contact properties. Field types (text, number, date, single-select) map to HubSpot property types. Multi-select dropdowns in Upnify map to HubSpot's multi-checkbox or single-checkbox property type depending on value structure.

Upnify opportunity custom fields map to HubSpot deal custom properties. Currency fields transfer as number properties with currency context preserved in a separate property. Region or product-category pick-lists in Upnify become HubSpot dropdown or radio-button properties with value-by-value mapping.

Upnify users resolve to HubSpot owners by email address match. Unmatched owners are flagged before migration — the team either creates HubSpot user accounts first or assigns records to a fallback owner. Inactive Upnify users map to inactive HubSpot owners so owner history is preserved but does not affect active workflows.

Upnify's WhatsApp conversation content does not migrate directly — HubSpot's WhatsApp Business integration uses its own conversation store. We preserve conversation metadata (last message date, thread ID) as custom contact properties so your team can re-associate threads in HubSpot's WhatsApp channel after migration.

Upnify leads and prospects map to HubSpot contacts. Since HubSpot does not split leads and contacts into separate objects, all Upnify lead-stage records land as HubSpot contacts. A lifecycle stage value can be assigned during migration to reflect the Upnify lead status for segmentation purposes.