Migrate from Sierra Interactive to Nutshell

Sierra Interactive Lead maps directly to Nutshell Person for contacts that represent existing clients or qualified prospects. The name, email, phone, address, and job title fields transfer as-is. Nutshell Person requires a primary CompanyId — leads without a company association attach to a default 'Unassigned' company record.

Sierra Interactive leads that have not yet been qualified route to Nutshell's Lead object. Nutshell Lead stores name, email, phone, and source. Once a lead converts, Nutshell's built-in lead-to-person conversion updates the Person record and closes the Lead at conversion.

Sierra Interactive company records (brokerages, real estate firms, property management companies) map to Nutshell Company with name, address, website, phone, and industry preserved. Parent-company hierarchies in Sierra map to Nutshell's Parent CompanyId field when present. Including ownership structure details and primary contact information.

Sierra Interactive deal records (transactions, listings, buyer/seller representation) map to Nutshell Deal with deal name, value, stage, expected close date, and owner preserved. Nutshell Deal requires a linked Person and Company — we resolve these lookups before inserting. And ensure accurate pipeline reporting.

Sierra Interactive Action Plans sequence automated emails, texts, voicemails, and phone tasks per lead. Nutshell has no equivalent automation-sequencing construct. We export each action plan's steps as a JSON audit log saved in a Nutshell custom field (Action_Plan_Audit__c) on the Person record for manual rebuild reference.

Sierra Interactive tracks saved properties per lead as property IDs with search criteria. Nutshell has no native saved-listings concept. We create a custom field (Saved_Listings__c) on Nutshell Person and serialize the property ID array as a JSON string for reference. Teams rebuild the search-context in Nutshell manually.

Sierra Interactive Lead Tags categorize prospects (e.g., 'First-Time Buyer', 'Investor', 'Expired Listing'). Nutshell stores tags as comma-separated strings in a custom field (Lead_Tags__c) on both Person and Lead objects. Tags are not linked entities in Nutshell — search and filtering rely on text matching.

Sierra Interactive Lead Source records where each contact originated (IDX website, referral, Zillow, etc.). Nutshell Lead has a standard 'source' field but it accepts only a single value. When Sierra records have multiple sources, we store the primary as Lead.Source and additional sources in Lead_Secondary_Sources__c.

Sierra Interactive notes and tasks attached to leads, companies, and deals migrate as Nutshell Notes and Tasks. Original timestamps, owners (resolved by email match to Nutshell users), and parent-record links are preserved. Nutshell Tasks support due date, priority, and status fields.

Sierra Interactive Lead Ponds organize leads into team queues (e.g., 'Hot Leads', 'Follow-Up Pool'). Nutshell does not have a native Pond equivalent. We map Pond membership to a custom pick-list field (Lead_Pond__c) on the Nutshell Lead record. Teams assign this field manually or via Nutshell automation after migration.

Sierra Interactive file attachments on leads, companies, and deals are downloaded and re-uploaded to Nutshell as file attachments on the corresponding Person, Company, or Deal record. Nutshell file size limits (25MB per file) apply. Inline images in rich-text notes are extracted and re-hosted as file attachments.

Sierra Interactive owner assignments resolve to Nutshell users by email match. Unmatched owners are flagged before migration — teams either invite them to Nutshell or reassign their records to a fallback owner. Nutshell's per-user pricing model means owner resolution also informs seat-count planning.