Migrate from MetroLeads to Nutshell

MetroLeads Leads with state values such as contacted, unqualified, or new map to Nutshell People. Leads with state indicating a prospect awaiting qualification map to Nutshell's Lead object. We extract all unique tenant-specific state values during the export scan, present them to the customer for mapping to Nutshell People status (new, in progress, won, lost, archived), and preserve the original MetroLeads state string in a custom field ml_original_state__c for audit and reporting after migration.

MetroLeads Company records map directly to Nutshell Company. The Company UUID is preserved as a legacy reference ID on the Nutshell Company record for audit traceability. MetroLeads /companies/{uuid}/leads establishes the parent-child hierarchy; we create the Nutshell Company first and then associate each migrated Lead to the correct Company via the People-Company link.

MetroLeads Events track engagement history tied to Leads. event_type (call, email, meeting, note) maps to Nutshell Activity records of the corresponding subtype. The event timestamp becomes the Activity date, and any event metadata (disposition, duration, outcome) maps to custom Activity fields. We preserve event-to-lead associations by resolving the People or Company reference at migration time.

MetroLeads embeds phones as an array within Lead records with type metadata (Work, Mobile, Fax, etc.). We flatten each phone entry into a standard contact-phone table, map type metadata to Nutshell's phone type labels, and insert the primary phone number into the standard People phone field during import.

MetroLeads embeds emails as an array within Lead records with type metadata. We extract each email entry and map the primary Work email to the Nutshell People email field. Personal and other email types migrate to a custom email field if present in the MetroLeads schema.

MetroLeads User records with id, name, and role assignments export with their role and territory metadata. We match Nutshell Users by email during import to preserve owner assignments on migrated People and Company records. Any MetroLeads User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

MetroLeads source_tags are string arrays on Lead records indicating lead disposition (e.g., disposition_answered). We export raw tag strings and map them to Nutshell People tags and/or the People source field depending on whether the tag represents a source or a disposition. The customer chooses tag strategy during scoping.

MetroLeads lead_group is a UUID reference grouping related Leads. There is no direct Nutshell equivalent. We export the UUID and group membership as a custom field ml_lead_group__c, then evaluate whether the customer wants lead_groups translated to Nutshell tags, shared lists, or campaign memberships based on the grouping use case.

MetroLeads Intellisearch is a platform-specific scoring and search layer. The scoring logic and saved search definitions do not map 1:1 to standard Nutshell fields. We export the raw Intellisearch configuration as a written document and map any computed lead scores to a custom People field ml_intellisearch_score__c. The customer's admin rebuilds the scoring model in Nutshell IQ or custom fields using this document.

Advanced Data Modules are tenant-specific data structures extending MetroLeads's base schema. Their field definitions vary per organization. We export the module schema alongside records, map fields to Nutshell custom fields on the People or Company object, and deliver a written schema map for the customer's admin to validate and extend post-migration.