Migrate from MetroLeads to Twenty CRM

MetroLeads Lead records map to Twenty CRM Person records. The MetroLeads lead_id becomes the Person's id (preserved as external_id for cross-reference). The lead's name, state, source_tags, lead_creation_time, and assigned_to user reference migrate to Person's standard fields. The lead-centric state value (e.g. 'contacted', 'qualified') is mapped to a Twenty custom field metro_state__c because Twenty does not have a native lead-state concept. We resolve the assigned_to user reference to a Twenty User record by email match during import.

MetroLeads Company records map directly to Twenty CRM Company. The Company serves as the parent container for Leads and is accessed via the /companies/{company_uuid}/leads endpoint hierarchy during export. We export Company records first, then associate each migrated Lead (now Person) to its parent Company via the CompanyId lookup. Domain, address, and custom company fields migrate to Twenty's Company standard and custom fields.

MetroLeads embeds phones as an array within Lead records with type metadata (Work, Mobile, etc.). We flatten these into a standard phone table keyed by record and migrate to Twenty's phone number fields on Person (primary contact phone) and Company (main office phone). Type metadata is preserved in a custom field phone_type__c on Twenty.

MetroLeads embeds emails as an array within Lead records with type metadata (Work, Personal). We extract these into a standard email table and migrate the primary email address to Twenty Person's email field. Additional email addresses migrate to Twenty's emailAddresses relation with type metadata preserved.

MetroLeads Events track engagement history tied to Leads. The event_type field determines the target: call-type events map to Twenty Task with TaskSubtype=Call; meeting-type events map to Twenty Event; general engagement events map to Task. We preserve event timestamps for activity timeline ordering and link each migrated record to the corresponding Twenty Person and Company via the Activity's relations.

MetroLeads User records (id, name, role) export and map to Twenty CRM User. We resolve users by email match. Any MetroLeads User without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before record import resumes. assigned_to references on Lead and Event records are updated to point to the resolved Twenty User IDs.

MetroLeads lead_fields are keyed by internal property IDs (e.g. customer_id_070) rather than human-readable names. The property name catalog is a separate API call. We fetch the full MetroLeads property schema first, build an ID-to-name mapping, then apply that mapping during field mapping so destination custom fields are named correctly in Twenty. Custom fields are created in Twenty's data model editor before migration using the resolved property names.

MetroLeads Lead state accepts tenant-configured string values, meaning 'contacted' in one MetroLeads instance may not exist in another. We extract all unique state values during the export scan, present them to the customer for lifecycle-stage mapping, and create a custom picklist field metro_state__c on the Twenty Person object with the sourced values. Any unmapped state values are flagged before import so no records are orphaned.

MetroLeads 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 a custom multi-select picklist field source_tags__c on the Twenty Person object. The customer chooses between multi-select (inline display on Person record) or a Topic-based tagging strategy during scoping.

MetroLeads Advanced Data Modules are tenant-specific data structures extending the base schema with per-organisation field definitions. We export the module schema alongside records, pre-create equivalent Custom Objects in Twenty's data model editor, and map fields by type (text to text, number to number, date to date). Module-to-Lead relationships are preserved as lookups from the custom object to Person.

MetroLeads Intellisearch is a scoring and saved-search layer built on lead data. The scoring logic and saved searches do not map 1:1 to Twenty CRM standard objects. We export the raw Intellisearch configuration as a structured JSON file and deliver a written inventory describing how to recreate equivalent scoring rules in Twenty's Workflow builder or as a custom field formula. This is a handoff artefact, not a live data migration.

MetroLeads lead_group is a UUID reference grouping related leads. This concept does not map to standard Twenty CRM objects. We export the UUID and the grouped-lead membership, then present options: a custom multi-select field on Person (listing all group UUIDs), a tagging approach, or a custom Group object in Twenty. The customer selects the grouping strategy during scoping.