Migrate from MetroLeads to HubSpot

MetroLeads leads map directly to HubSpot contacts. The primary name, email, phone, and job title fields migrate as direct property mappings. MetroLeads' embedded email and phone arrays require flattening — the first 'Work' entry becomes HubSpot's email and phone, with additional entries stored in custom properties.

MetroLeads' 'state' field (new, contacted, qualified, converted) maps to HubSpot lifecycle_stage on the Contact. Leads in MetroLeads 'converted' state also generate a corresponding HubSpot Deal. The mapping is: MetroLeads 'new' → HubSpot 'lead', 'contacted' → HubSpot 'lead', 'qualified' → HubSpot 'SQL', 'converted' → HubSpot 'customer' plus a Deal record.

MetroLeads stores assigned_to as a name + ID object per lead. We resolve each MetroLeads user by email match against HubSpot users and set the matched HubSpot user as the Contact and Deal owner. Unmatched owners are flagged before migration so your team can either invite them to HubSpot or reassign to a fallback owner.

MetroLeads source_tags are a string array (e.g., disposition_answered, follow_up_required) attached to each lead. HubSpot has no native equivalent for tag-style disposition labels on contacts. We map them to a multi-select custom property on the HubSpot Contact (Source_Tags__c) for reporting continuity. Your team can also use HubSpot Lists filtered on this property for segmentation.

MetroLeads lead_group is a UUID-based field that groups leads by team or territory. HubSpot has no direct equivalent. We create a custom property (Lead_Group__c) on Contact and optionally build HubSpot Lists per unique lead_group value so your team can filter by territory in dashboards and workflows. Lead_group hierarchies require manual planning — circular references are flagged before migration.

MetroLeads' lead_fields object holds custom key-value pairs specific to each deployment (e.g., customer_id_070, industry_segment). Each MetroLeads custom property becomes a HubSpot custom property on Contact. We preserve the MetroLeads property name as the HubSpot property label and apply type-aware mapping — text → string, numeric → number, date → date.

MetroLeads companies map directly to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map to HubSpot's standard Company properties. If MetroLeads stores a parent-company relationship, we map it to HubSpot's Parent Company field. Companies without contacts receive a placeholder contact or are flagged for manual review.

MetroLeads stores call events with disposition, duration, and caller metadata. HubSpot's Calls object captures call subject, body, and outcome. We map MetroLeads call disposition to a custom property on the HubSpot Call (Metro_Disposition__c) and call duration to Duration_Minutes__c. Original call timestamps and owner are preserved. HubSpot Sales Hub Starter or above is required for call logging.

MetroLeads email engagement events map to HubSpot Email engagements on the associated Contact. Subject, body, and timestamp are preserved. MetroLeads does not store the full email body for all email events — if the body is empty, we log the engagement timestamp and sender as a note on the HubSpot contact record.

MetroLeads meeting and note events map to HubSpot Meetings and Notes respectively. Original timestamps, meeting subject, and owner are preserved. Notes with rich-text formatting are migrated as HubSpot Notes with the original body intact. If MetroLeads stores a parent-record link for a note, we preserve the association in HubSpot.