Migrate from LeadManaging to Nutshell

LeadManaging's person data maps directly to Nutshell's Person object. Name, email, phone, job title, and address fields transfer as-is. The person's primary company association resolves to a Nutshell Company record that must be created first to satisfy the foreign-key relationship.

When LeadManaging stores an organization name on a lead, FlitStack extracts it as a standalone Company record in Nutshell. If the company name is blank or ambiguous, a placeholder company record is created and flagged for your team to verify and rename.

LeadManaging deals and opportunities map to Nutshell Leads. The deal name, amount, close date, and stage all transfer. Nutshell Lead Confidence (0–100 rating) can receive a mapped value if your source has a comparable score; otherwise it defaults to 50 and can be updated manually after migration.

LeadManaging pipeline names map to Nutshell Pipeline objects. Each pipeline in the source becomes its own Nutshell Pipeline with named stages. Stage order and labels are preserved; stage probability is not carried over unless your source stores explicit probability values, since Nutshell stages do not have native probability fields.

LeadManaging lead status values (New, Contacted, Qualified, Lost, Won) map to Nutshell's Lead Status pick-list. We apply a value-by-value mapping — statuses that have no exact Nutshell equivalent receive the closest available option and are flagged in the mapping plan for your review before the migration runs.

LeadManaging custom fields — such as lease_type, unit_number, move_in_date, or referral_source — do not have a native equivalent in Nutshell. FlitStack creates matching custom fields on the appropriate Nutshell object (Person, Company, or Lead) before the migration, preserving the original data type and any pick-list values the field uses.

LeadManaging's tag model has no direct Nutshell equivalent. Tags migrate as a text custom field storing comma-separated values, or as a multi-select pick-list if the total tag set is small and well-defined. Teams that rely heavily on tagging for segmentation should review the resulting field in Nutshell and consider using Nutshell's built-in filters instead.

Activity records from LeadManaging map to Nutshell Activities. Calls become call activities, emails become email activities, meetings become meeting activities, and notes become note records — all linked to the correct Person, Company, or Lead. Original timestamps and owner attribution are preserved on each record.

File attachments stored against lead records in LeadManaging are downloaded and re-uploaded to Nutshell's file storage. Nutshell's file size limits apply; files exceeding the limit are flagged for manual re-upload by your team. Inline images in notes are extracted, re-hosted, and the note body is updated with the new image URLs.

LeadManaging owner assignments resolve by matching the owner's email address to a Nutshell user. If no matching Nutshell user exists, the record is assigned to a designated fallback owner and flagged in the migration report. You should ensure all active LeadManaging users have been invited to Nutshell before the migration date.

If LeadManaging stores a numeric confidence or priority score on leads that has no direct equivalent in Nutshell, we migrate it as a custom numeric field on the Lead object. Nutshell's native Lead Confidence (0–100 rating) coexists with this field; your team can choose which to use for pipeline sorting.

LeadManaging stores address components separately (street, city, state, zip, country). These merge into Nutshell's single-line address field. When multiple address records exist for one person, FlitStack selects the most recently modified address by default and surfaces any alternates as a note on the Person record.