Migrate from Lofty to Nutshell

Lofty Lead maps directly to Nutshell Lead — this is the primary person record in both systems. All standard fields (name, email, phone, address) transfer 1:1. Owner assignment is resolved by email match against Nutshell users before the full migration runs.

Lofty's multi-value tag field has no direct Nutshell equivalent. We concatenate tag values into a comma-separated string stored in a custom text field on the Nutshell Lead. Filtering by tag values requires a manual rebuild using Nutshell's filter capabilities post-migration.

Lofty source values (website, referral, zillow, etc.) map to Nutshell Lead Source pick-list. If a source value does not exist in Nutshell's options, we add it to the pick-list during pre-flight schema setup so no data is dropped. This ensures complete source attribution visibility in Nutshell's reporting and analytics views.

Lofty tracks lead quality scores as a numeric property. Nutshell has no native score field. We create a custom Number field (Lead_Score__c) on the Nutshell Lead object and migrate values directly, preserving the relative ranking of leads from Lofty. The numeric scale remains intact, allowing your team to filter and sort by score in Nutshell reports.

Lofty deal pipeline stages (New, Contacted, Showing Scheduled, Offer Made, Closed Won/Lost) map to Nutshell Deal status values. We create Nutshell Deal statuses matching Lofty's pipeline stage names during schema setup, then map values row by row during migration. Probability percentages associated with each stage are also transferred from Lofty's pipeline configuration.

Lofty Deal maps to Nutshell Deal — the monetary opportunity record tied to a lead and optionally a company. Fields including name, estimated value (amount), close date, and owner all transfer 1:1. Probability is mapped per stage from Lofty's pipeline configuration.

Lofty Company maps to Nutshell Company (the business-account record). Name, domain/website, industry, employee count, and annual revenue transfer 1:1. Lofty's parent-company hierarchy maps to Nutshell's Parent Company lookup — the parent company must migrate first or we flag circular references.

Lofty engagement records (calls, emails, meetings, notes) all become Nutshell Activity records with the type field set to 'Call', 'Email', 'Meeting', or 'Note' respectively. Original timestamps, subject lines, and owner assignments are preserved. Notes map to Nutshell Notes on the parent record.

Lofty custom fields (text, number, date, anniversary-date, single-select, multi-select, percentage, currency) map to Nutshell custom fields on the corresponding entity (Lead, Company, or Deal). Data-type-aware transformation is applied: anniversary dates become date fields, percentages become number fields, currency values are stored as decimal numbers.

Lofty Segments are dynamic lead groupings based on filter rules — a business-logic construct with no Nutshell equivalent. Segment definitions are exported as a reference document for your team to rebuild using Nutshell's saved-filter and reporting capabilities post-migration. The segment membership at migration time is not preserved as dynamic data.

Lofty owner IDs resolve to Nutshell users by email address match. If a Lofty owner email has no corresponding Nutshell user account, the record is flagged before migration for your team to assign to an active user or fallback owner. No record lands in Nutshell without a valid owner.