Migrate from crmConnect to HubSpot

crmconnect contacts map 1:1 to HubSpot contacts. The contact's primary email, phone, name, and address fields map directly to HubSpot contact properties. Secondary phone numbers and custom contact properties migrate as HubSpot custom properties with the original crmconnect field names preserved in the property label for traceability.

crmconnect contact status values (e.g., New, Active, Inactive) map to HubSpot lifecycle_stage values. We map each crmconnect status to the nearest HubSpot lifecycle stage — Active contacts typically map to 'customer', Inactive to the last stage before churn, and New to 'subscriber' or 'lead' based on your specified rules. Status-change timestamps migrate as a custom datetime field (Lifecycle_Stage_Updated__c equivalent in HubSpot) for reporting continuity.

crmconnect companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map to the corresponding HubSpot company properties. Address, phone, and social link fields also migrate directly. HubSpot's parent-company hierarchy is supported if crmconnect stores parent-child relationships — these map to HubSpot's company associations. Custom company properties migrate as HubSpot custom properties with original field labels preserved.

crmconnect deals map to HubSpot deals. Each deal carries its name, amount, close date, owner, and associated contact/company links. crmconnect deal pipelines map to HubSpot deal pipelines — each pipeline in crmconnect becomes a separate HubSpot deal pipeline, and deal stages within each pipeline map to HubSpot deal stages with probability percentages applied per stage.

crmconnect pipelines become HubSpot deal pipelines. Each pipeline name in crmconnect creates a new HubSpot pipeline. Pipeline stage names map value-by-value to HubSpot deal stage names, with probabilities, forecast categories, and stage-order preserved. If crmconnect uses a single default pipeline, that migrates as one HubSpot pipeline; multiple crmconnect pipelines each get their own HubSpot pipeline to keep stage logic separate.

Stage names are mapped value-by-value from crmconnect to HubSpot deal stages. We capture each stage's probability percentage from crmconnect and apply it to the corresponding HubSpot stage. Closed-won and closed-lost statuses transfer with original close dates preserved so win-rate reporting starts accurately in HubSpot from the migration date.

crmconnect engagement history maps to HubSpot's timeline on contacts and deals. Call logs become HubSpot call engagements with duration and outcome. Emails become email engagements with subject and body. Meetings become meeting engagements with original start/end times and attendee lists. Notes become HubSpot notes with timestamps and owner attribution. Original engagement timestamps are preserved so the HubSpot timeline shows the full history.

crmconnect tasks map to HubSpot tasks. Task subject, due date, status, priority, and owner migrate. Open tasks land as open tasks in HubSpot; completed tasks migrate with their completion status and timestamps. Task associations to contacts and deals are preserved so task-to-record links are intact after migration.

crmconnect custom fields on contacts (beyond the standard fields) migrate as HubSpot custom contact properties. Property names are mapped from crmconnect field labels to HubSpot property format (alphanumeric, no spaces). Data types are preserved: text fields to text, number fields to number, date fields to date, pick-list fields to HubSpot dropdowns with value-by-value mapping.

crmconnect deal-level custom fields map to HubSpot deal custom properties following the same type-preservation logic as contact properties. Pick-list values in crmconnect become HubSpot deal property options. If crmconnect stores deal-weighted values or custom probability fields, those become custom number or currency properties on HubSpot deals.

crmconnect users and deal owners are resolved by email match against HubSpot users. We flag any crmconnect owner whose email does not match a HubSpot user before migration — your team either creates the HubSpot user or reassigns those records to a specified fallback owner. No record lands in HubSpot without an owner resolved.

crmconnect file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files attach to the corresponding HubSpot record by association. HubSpot's file size limits apply (default 25MB per file). If crmconnect stores inline images in notes, those are extracted and rehosted as HubSpot-hosted images.