Migrate from MetroLeads to Pipedrive

MetroLeads Lead records map to Pipedrive Person. The Lead name splits into first_name and last_name; embedded phones and emails extract to Pipedrive's phone and email arrays with type metadata preserved (Work, Mobile, Personal). The MetroLeads assigned_to user reference resolves by email against Pipedrive User records during import. Custom lead_fields keyed by MetroLeads property ID (e.g. customer_id_070) are mapped to Pipedrive custom fields using the property schema fetched before migration; we build an ID-to-name lookup table so destination fields use human-readable names.

MetroLeads' Lead state is a tenant-configurable string (e.g. contacted, qualified) that varies between instances. We extract all unique state values during the export scan, present them to the customer for mapping to Pipedrive Person labels or pipeline stages, and flag any unmapped values so no records arrive with an unresolvable state. State values with no Pipedrive equivalent are preserved in a custom field for manual disposition post-migration.

MetroLeads Company records map to Pipedrive Organization. The /companies/<company_uuid>/leads/ API establishes the parent-child hierarchy; we resolve this by creating Organization records first, then linking each Lead-to-Person record to its parent Organization by company UUID during insert. Company name and website migrate directly; industry and employee count map to Pipedrive's standard Organization fields or custom fields if configured.

MetroLeads source_tags are string arrays indicating lead disposition (e.g. disposition_answered, source_website). We export the raw tag strings and map them to Pipedrive Person labels during import. Multiple tags per Lead create multiple label assignments in Pipedrive. Tags that have no Pipedrive label equivalent are preserved in a custom field for manual review after migration.

lead_group is a MetroLeads-specific UUID reference grouping related leads without a standard CRM equivalent in Pipedrive. We export the group UUID and membership data. The customer chooses between mapping grouped leads to a Pipedrive custom field (group UUID stored as text) or creating shared Pipedrive Lists to replicate the grouping behavior manually post-migration.

MetroLeads Events track engagement history tied to Leads. The event_type field determines the Pipedrive Activity subtype: call-type events map to Pipedrive Activity with type=Call, meeting types to type=Meeting, tasks to type=Task, and notes to type=Note. We preserve event-to-lead associations by linking the Pipedrive Activity's PersonId to the migrated Person record. Activity timestamps migrate as ActivityDate for ordering in the Pipedrive timeline.

MetroLeads User records (id, name, role) export by email match to Pipedrive User records. MetroLeads assigned_to references on Leads resolve to Pipedrive OwnerId via this User lookup. Any MetroLeads User without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import proceeds.

Advanced Data Modules are tenant-specific data structures extending MetroLeads' base schema. Their field definitions vary per organization. We export the module schema alongside records and map each module's fields to Pipedrive custom fields on the relevant object (Person or Organization). Pipedrive must have the destination custom fields created before data import; we coordinate field creation via Pipedrive's custom field API or during the import mapping step.

Intellisearch is MetroLeads-specific lead scoring logic built on top of lead data. The scoring rules and saved searches do not map 1:1 to Pipedrive objects. We export the raw Intellisearch configuration as a JSON reference document for the customer's admin to manually implement using Pipedrive's workflow automation triggers or the Smart Docs and Insights features if scoring logic is business-critical.

MetroLeads embeds phones and emails as typed arrays within each Lead record. We flatten these into Pipedrive's standard Person phone and email fields, preserving type metadata (Work, Mobile, Home for phones; Work, Personal for emails). The primary phone and email indicators from MetroLeads map to Pipedrive's primary/sub-field flags.