Migrate your MetroLeads data

Leads are the core object with rich fields including lead_id, name, state, source_tags, lead_creation_time, lead_fields for custom properties, assigned_to user reference, and lead_group. We export all standard fields plus custom lead_fields. The merge API accepts retain_fields and merge_fields parameters to control field priority during merges.

Companies serve as parent containers for leads. The API path /companies/<company_uuid>/leads/ establishes the hierarchy. We export Company records and associate each Lead to its parent Company during migration.

Events track engagement history tied to leads. Field structure is stable but event-to-lead associations require careful join mapping across the API response structure. We preserve event_type and event_timestamps during export.

Intellisearch is a MetroLeads-specific search and scoring layer built on top of lead data. The scoring logic and saved searches do not map 1:1 to standard CRM objects, so we export the raw configuration as a JSON blob and map saved search criteria to destination custom properties.

Advanced Data Modules are tenant-specific data structures extending the base schema. Their field definitions vary per organization. We export the module schema alongside records and map fields to destination custom objects or custom fields.

User records with id, name, and role assignments. We export Users and preserve owner assignments on Leads so that assigned_to and user_assigned_to references resolve correctly in the destination system.

Phones are embedded as an array within Lead records with type (Work, Mobile, etc.) and phone number. We flatten these into a standard contact-phone table and preserve type metadata during import.

Emails are embedded as an array within Lead records with type and address. We extract these into a standard contact-email table and preserve type metadata for Work, Personal, etc.

lead_fields on each Lead record store tenant-specific custom property values keyed by property ID. Property naming conventions are per-tenant and not self-describing, so we map property IDs to destination custom field names via a pre-migration field catalog.

source_tags are string arrays on Lead records indicating lead disposition (e.g. disposition_answered). We export the raw tag strings and map them to destination tag or label objects.

state is a string field on Lead (e.g. contacted) representing lifecycle stage. The valid values are tenant-configurable. We map known state values to destination lifecycle stage or deal stage fields and flag unmapped states for manual review.

lead_group is a UUID reference grouping related leads. This is not a standard CRM concept. We export the UUID and map grouped leads to destination shared lists, campaigns, or custom grouping objects.