Migrate from Sentian Solutions to Nutshell

Sentian contact records map directly to Nutshell Person records. The Person object holds name, email, phone, title, address, and owner assignment. Custom properties on Sentian contacts migrate as Nutshell custom fields on the Person object. Multi-email addresses in Sentian collapse to the primary email field with additional addresses stored in a custom field.

Sentian company records map 1:1 to Nutshell Company records. Company name, domain, industry, employee count, and revenue fields map to their Nutshell equivalents. Parent-company relationships in Sentian map to Nutshell's parent Company lookup field. Custom properties on companies create Nutshell custom fields on the Company object.

Sentian leads that are not yet converted map directly to Nutshell Lead records. Lead status, source, and rating fields translate to Nutshell's Lead status, source, and rating fields. Custom lead properties in Sentian create Nutshell custom fields on the Lead object. Leads with a closed-won status in Sentian route to a Nutshell Person or Deal as appropriate.

Sentian deal records map to Nutshell Deal records. Deal name, amount, close date, stage, and owner map directly. Sentian deal stage names map to Nutshell's default stage labels; custom stage labels require a value-mapping step before migration. Deals without a primary company link are attached to the most-recently-associated Nutshell Company.

Sentian tasks and notes map to Nutshell Tasks and Notes. Call logs, meetings, and general tasks map to Nutshell Task records with the task type preserved in a custom field. Timestamps, owners, and linked record associations are preserved. Nutshell does not natively support meeting records with start/end times — these store as Tasks with a custom datetime field for the scheduled time.

Sentian custom objects map to Nutshell custom fields on the appropriate entity (Person, Company, or Lead). Nutshell does not have a standalone custom object concept — custom data that does not fit the standard Person/Company/Lead/Deal model is flattened into custom fields on existing objects. Complex custom objects with multiple sub-entities may require a custom mapping review.

Sentian user records are resolved by email match against Nutshell users. If a Sentian user email matches an existing Nutshell user, records are assigned to that user. Unmatched owners are flagged before migration and assigned to a fallback Nutshell user or team queue. This prevents orphaned records landing without an owner.

File attachments linked to Sentian records are downloaded and re-uploaded to the corresponding Nutshell record. Nutshell stores files attached to People, Companies, Leads, and Deals. File size limits of 25MB per file apply. Files without a valid parent record link are attached to the associated Person or Company.

Sentian workflow rules and automation logic do not transfer to Nutshell. Workflow definitions are exported as a JSON specification file that FlitStack delivers alongside the migrated data. Nutshell administrators use this file as a rebuild reference for Nutshell's drip sequences and automation tools. This is disclosed upfront — no automation carries over automatically.

Sentian reports and dashboards do not transfer. The underlying data that feeds reports migrates to Nutshell, but report definitions and dashboard layouts are destination-side configurations. Teams should plan for a reporting rebuild phase in Nutshell using exported Sentian report definitions as reference layouts.