Migrate from LeadMaster to Nutshell

LeadMaster Accounts map 1:1 to Nutshell Companies. We preserve the primary contact link, all standard address fields (street, city, state, postal code, country), and any custom properties mapped to Nutshell custom fields that we pre-create before Company import. The Company is the first object we migrate so that the People import can satisfy the 'works for Company' relationship at insert time.

LeadMaster Leads map to Nutshell People for records that represent individual contacts with a known company affiliation. We map owner assignment, status, source, and lifecycle fields to their Nutshell equivalents. LeadMaster custom properties that have no direct Nutshell equivalent are stored in custom fields created during schema setup. The lead status workflow from LeadMaster (new, contacted, follow-up) maps to Nutshell's People status values.

LeadMaster Opportunities map to Nutshell Deals. Stage, amount, close date, owner, and associated Account link migrate directly. Custom pipeline stages in LeadMaster are mapped against Nutshell's customizable deal stage list during configuration. The Deal-Company link is resolved at migration time by finding the matching Nutshell Company by name or domain.

LeadMaster Cases (the help desk module) map to Nutshell Cases. We preserve case number, status, priority, description, and the associated Company or Person link. Conversation threads are mapped to the Case's activity timeline. Cases are migrated after Companies and People so that the parent record references are satisfied at insert time.

LeadMaster Users and Owners map to Nutshell Users by email match. We extract every distinct owner referenced on Leads, Opportunities, and Cases during discovery and match by email against the Nutshell destination account's user list. Any LeadMaster owner without a matching Nutshell User is flagged for the customer's admin to provision before the migration run begins.

LeadMaster custom form field definitions and their submitted response data are mapped to Nutshell custom fields on People or Company depending on the form's target object. We extract both the form schema and the responses during discovery. Where a LeadMaster form field has no equivalent in the Nutshell standard schema, we create a typed custom field (text, number, date, or picklist) before migration and map the form response into it. The form layout itself must be replicated in Nutshell's form builder post-migration.

LeadMaster marketing campaigns and associated email send history are migrated as Nutshell Campaign records with contact associations. The campaign name, type, status, and start/end dates transfer. Email content and templates are exported from LeadMaster and re-imported to Nutshell's campaign email feature. Marketing automation sequences attached to campaigns do not migrate as executable logic and are documented for rebuild in Nutshell's email sequencing tool (Engagement Suite) or the customer's preferred platform.

LeadMaster notes and logged activity (calls, emails, meetings, tasks) are mapped to Nutshell Activities associated with the relevant People, Company, or Deal record. Activity type, date, owner, and content all transfer. The activity schema is normalized at migration time so that LeadMaster's varied activity types (call log, email log, meeting note) map to the correct Nutshell Activity type.