Migrate from MetroLeads to Freshsales

MetroLeads Leads with lifecycle state of contacted, qualified, or converted map to Freshsales Contact tied to an Account. Leads with state of new, unqualified, or prospect map to Freshsales Lead. We extract the full tenant-specific state vocabulary during export, present it to the customer for explicit split rule definition, and preserve the original MetroLeads state value in a custom field metroleads_original_state__c on both Lead and Contact for audit and reporting continuity.

MetroLeads Companies serve as parent containers for Leads and map directly to Freshsales Account. The API path /companies/<company_uuid>/leads establishes the hierarchy. We export Company records first and resolve the parent AccountId on each Lead during import so that Contact-to-Account lookups are satisfied at insert time rather than requiring post-migration parent reassignment.

Phones embedded in MetroLeads Lead records with type metadata (Work, Mobile, Home, etc.) extract into Freshsales Contact phone fields. We preserve type labels by mapping to Freshsales phone_type values. Multiple phones per Lead become multiple Contact Phone records linked via the contact_id lookup.

Emails embedded in MetroLeads Lead records with type metadata (Work, Personal) extract into Freshsales Contact email fields. Type metadata maps to Freshsales email_type labels. Primary email flag from MetroLeads determines which email becomes the primary contact email in Freshsales.

MetroLeads source_tags are string arrays on Lead records indicating disposition or source channel (e.g. disposition_answered, channel_web). We export raw tag strings and map them to Freshsales Tags. If the customer uses tags for data classification rather than marketing segmentation, we map to a custom multi-select picklist field on Contact to preserve the full tag set without creating Freshsales system tags that alter CRM behavior.

MetroLeads lead_fields store tenant-specific custom property values keyed by internal property IDs (e.g. customer_id_070). We fetch the MetroLeads property schema first, build an ID-to-name mapping table, and apply it during field mapping so destination custom fields carry the correct human-readable names rather than ID strings. Custom field types are inferred from the property data type in the schema and mapped to the equivalent Freshsales field type before import.

MetroLeads Events track engagement history tied to Leads with event_type and event_timestamp fields. We map Events to Freshsales Appointments, preserving the event_type as appointment title, event_timestamp as StartDateTime, and any disposition notes in the appointment description. Event-to-Lead associations require join mapping across the MetroLeads API response structure to resolve the correct Freshsales Contact or Lead contact_id.

MetroLeads Users with id, name, and role assignments export and map to Freshsales User records by email match. Owner assignments on Leads (assigned_to, user_assigned_to) resolve to Freshsales OwnerId via the User lookup. Any MetroLeads User without a matching Freshsales User email goes to a reconciliation queue for the customer's admin to provision before record import resumes.

MetroLeads lead_group is a UUID reference grouping related Leads. This is not a standard Freshsales concept. We export the UUID and map grouped Leads to Freshsales Contact Lists or a custom text field holding the original lead_group UUID, depending on whether the customer uses Lists for segmentation or needs the grouping preserved as a data attribute for reference.

Intellisearch is a MetroLeads-specific search and scoring layer built on Lead data. The scoring logic and saved searches do not map 1:1 to Freshsales. We export the raw Intellisearch configuration and scoring parameters as a JSON document attached to the primary Contact record via a long-text custom field for reference. Any pre-calculated lead scores map to a numeric custom field freshsales_intellisearch_score__c.