Migrate from MetroLeads to monday CRM

MetroLeads Lead records map directly to Monday.com CRM People items. The lead_id becomes the item name or a custom ID column. We extract all unique state values during export, present them for Monday.com status-column mapping, and flag any unmapped states so no records arrive with an unresolvable status. The assigned_to user reference resolves by email match against Monday.com team members during import. Source_tags migrate as Monday.com tags on the People item.

MetroLeads Company records map to Monday.com CRM Company items. The company hierarchy (/companies/<uuid>/leads/) is preserved as a linked-company relationship in Monday.com. We extract the company_name, domain, and any company-level custom properties for column mapping. Company is created before any linked Lead import so that the company relationship is satisfied at the moment of People item creation.

Phones embedded in MetroLeads Lead records (with type metadata: Work, Mobile, etc.) are flattened into a standardized contact-phone table during export. We map type metadata to Monday.com's Phone column type options, preserving the distinction between work and mobile numbers. Multiple phone numbers per Lead become separate rows in the phone table, associated to the People item by contact ID.

Emails embedded in MetroLeads Lead records (with type: Work, Personal) are extracted to a contact-email table during export. Monday.com's Email column accepts a single email per contact with an optional type. For Leads with multiple emails, the primary (first-listed) email maps to the Email column and secondary emails are added as custom text columns labeled by type.

MetroLeads Events track engagement history (call, email, meeting) tied to leads. Monday.com CRM does not have a native engagement timeline equivalent as a standard object. We export the full event log (event_type, timestamp, description) as a structured CSV and map it to a custom Activity Log board or to manual timeline entries depending on the customer's Monday.com plan. Event-to-Lead associations are preserved by item ID cross-reference.

MetroLeads User records (id, name, role) export with owner references on Leads. We resolve assigned_to by email match against Monday.com team members. Any MetroLeads User without a matching Monday.com team member goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive MetroLeads users are mapped to inactive Monday.com members with a note.

MetroLeads source_tags are string arrays on Lead records indicating lead disposition (e.g., Google Organic, disposition_answered). We export the raw tag strings and map them directly to Monday.com Tags on the People item. Tags are self-describing in Monday.com, requiring no schema pre-configuration.

MetroLeads lead_fields are keyed by internal property IDs (e.g., customer_id_070) rather than human-readable names. We fetch the full property schema catalog during export, build an ID-to-name mapping, and create Monday.com columns with the human-readable property names before import. Property value types (text, number, date, multi-select) are mapped to equivalent Monday.com column types. Tenant-specific field definitions require manual review during scoping.

MetroLeads Advanced Data Modules are tenant-specific data structures extending the base schema with custom field definitions that vary per organization. We export the module schema alongside records and map fields to Monday.com custom columns on a dedicated board. The structure is preserved as closely as possible, but module-specific logic and calculated fields do not migrate; we deliver a written module inventory for the customer's admin to rebuild as Monday.com boards or formulas.