Migrate from LeadSimple to Nutshell

LeadSimple leads with contact info (name, email, phone, address) map to Nutshell People records. Email is the de-duplication key. Owner resolves by email match against Nutshell users; unresolved owners become a migration-system fallback owner. We also preserve the original lead creation date in a custom field, and any associated tags are transferred as Nutshell tags on the Person record.

LeadSimple leads carry an optional company name field. When present, we create a Nutshell Company record first, then link the Person record to it. LeadSimple leads without a company name land as unlinked People in Nutshell. We also map the company's address if available, and attach any company-level tags to the Person record for reference.

Each LeadSimple pipeline maps to a Nutshell Deal pipeline. Each LeadSimple stage name maps value-by-value to a Nutshell deal stage. Stage probability and forecast category re-applied based on Nutshell's stage defaults or your specified mapping. If a stage name does not exist in Nutshell, we create it as a new stage before mapping, ensuring continuity of the pipeline structure.

LeadSimple stage status values (Active, Won, Lost, Dead) map directly to Nutshell Lead status pick-list values. Custom LeadSimple status values require a value-map entry added during planning. During the planning call we confirm the exact status strings, ensure any inactive or archived statuses are excluded, and document the mapping so your team can verify the status layout in Nutshell before import.

LeadSimple stores property type (Single Family, Multi-Family, Commercial) on lead records. Nutshell has no native property-type field. We create a Nutshell custom field (type: pick-list) on People, populated with the source values from LeadSimple. If LeadSimple uses additional property-type values beyond the standard set, we add them to the pick-list during the planning phase and map each one explicitly.

LeadSimple occupancy field (Occupied, Vacant) migrates as a custom pick-list field on Nutshell People. If your LeadSimple setup uses custom occupancy values, those require a value-map before migration. We verify the exact occupancy labels in your LeadSimple export, add any missing values to the Nutshell pick-list, and document the mapping so the correct status appears on each Person record after import.

LeadSimple's Number of Units field migrates as a custom integer field on Nutshell People. Zero or blank values preserved as null unless your migration plan specifies a default. If LeadSimple records contain non-numeric characters or text in this field, we clean them before import and flag any anomalies for your review.

LeadSimple stores comments on leads. We pull comments via LeadSimple API and load them as Nutshell Notes attached to the corresponding Person or Lead record, preserving the comment author and timestamp. If a comment references another record or contains a mention, we preserve the reference as a plain-text note and note the original thread context for your team's review.

LeadSimple's Next Task and due date map to a Nutshell Task on the Person or Lead record. Task kind (call, email, meeting) inferred from task name if present in the export. If the task name does not indicate a type, we default to a generic task and include the original LeadSimple task description in the task notes field for clarity.

Any custom fields on LeadSimple contacts (beyond the standard export fields) migrate as Nutshell custom fields on People. Field type (text, pick-list, date, number) matched to the closest Nutshell field type; complex conditional logic cannot be preserved. We also record the original LeadSimple field labels in a reference sheet so your team can verify the mapping and update field names in Nutshell after migration.

LeadSimple process-level custom fields that store data per contact (lease dates, renewal flags, etc.) migrate as People-level custom fields in Nutshell. Process automation logic does not migrate — values transfer, rules do not. We map each process field to a matching custom field on the Person record, preserving the original data type and any pick-list options, and note any fields that cannot be directly represented in Nutshell.

LeadSimple tags on leads map to Nutshell Tags on the Person record. Multi-value tags are split and applied individually. Tags with spaces are preserved with their exact casing. If a tag contains characters not supported by Nutshell, we sanitize the tag to a compatible format and log the original tag in a reference file for your review.