CRM migration
Field-level mapping, validation, and rollback between Sentia and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Sentia
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Sentia and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Sentia to Nutshell is a data-model consolidation migration. Sentia maintains separate Lead and Contact objects, while Nutshell merges unqualified prospects into a single People object with a Person Type property distinguishing between leads and customers. We handle that merge during import, preserving lead source and lead status as custom People fields. Sentia's customizable Deal pipelines map to Nutshell's pipeline and stage configuration, with stage probability percentages carried forward. Custom fields on Sentia Basic and Starter tiers migrate as Nutshell custom fields on the equivalent object; we validate API access during discovery since Starter provides fewer field types than Ultimate. Voice workflow configurations are not portable; we export a JSON representation for manual rebuild in Nutshell. Automation rules, sequences, and workflow logic do not migrate as code.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Sentia object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Sentia
Contact
Nutshell
Person (People)
1:1Sentia Contacts map directly to Nutshell People records. We preserve all standard Contact fields (name, email, phone, address) and any custom Contact-level properties as Nutshell custom fields on the Person object. The migration uses email as the dedupe key to prevent duplicate People records if the customer has existing Nutshell data from a trial period.
Sentia
Company
Nutshell
Account
1:1Sentia Company records map to Nutshell Accounts. Company names are matched case-insensitively against existing Nutshell Accounts to flag duplicates before import. The Contact-to-Company association is preserved by setting the Nutshell Person's Account link after the Account record is created. We handle the case where a single Sentia Company has multiple Contacts by creating one Account and linking all related People records.
Sentia
Lead
Nutshell
Person (People) with Person Type = Lead
many:1Sentia Leads do not have a direct Nutshell equivalent since Nutshell uses a unified People object with a Person Type field. We migrate Sentia Leads as Nutshell People with Person Type set to Lead and preserve the original lead source and lead status as custom fields on the People record. The customer confirms during scoping which Sentia lead statuses map to Nutshell's Person Type values.
Sentia
Deal
Nutshell
Person (People) linked Deals
1:1Sentia Deals map to Nutshell Deals linked to the associated People record and Account. The pipeline stage from Sentia becomes the Nutshell Deal stage. If Sentia has multiple pipelines, we consolidate to the Nutshell pipeline count available on the customer's target tier (Growth 1 pipeline, Pro 5 pipelines, Enterprise unlimited). The customer chooses the target tier during scoping.
Sentia
Pipeline Stage
Nutshell
Deal Stage
lossySentia pipeline stages map to Nutshell Deal stages by name proximity with customer confirmation required. Stage probability percentages migrate as a custom field on the Nutshell Deal if the destination tier supports custom Deal fields. We validate whether the target Nutshell tier exposes stage probability fields or if probability tracking is handled manually.
Sentia
Custom Fields
Nutshell
Custom Fields on Person, Account, or Deal
1:1Custom fields on Sentia migrate to Nutshell custom fields on the equivalent object. We discover the full field schema via the Sentia metadata API during discovery and validate API access on the customer's active tier. The Ultimate tier exposes more field types (date, number, currency, multi-select) than Basic or Starter, which may limit which field types are available for export. We flag any fields that cannot be exported before migration begins.
Sentia
Activity (calls, emails, meetings, notes)
Nutshell
Activity on Person or Account
1:1Sentia Activities attached to Contacts or Deals migrate to Nutshell Activity records on the linked People or Account. We preserve timestamps, content, and owner attribution. The Activity-to-Contact association is maintained by resolving the Person record created in the Contact migration phase. Activity records with no linked Contact are imported as standalone activities with a note in the record flagging the missing association.
Sentia
User
Nutshell
User
1:1Sentia Users who own records map to Nutshell Users resolved by email match. We build a user-mapping table during scoping because Sentia User IDs are not transferable to Nutshell. Any Sentia User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import. Inactive Sentia users may be mapped to inactive Nutshell users or assigned to a migration admin placeholder.
| Sentia | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person (People)1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Lead | Person (People) with Person Type = Leadmany:1 | Fully supported | |
| Deal | Person (People) linked Deals1:1 | Fully supported | |
| Pipeline Stage | Deal Stagelossy | Fully supported | |
| Custom Fields | Custom Fields on Person, Account, or Deal1:1 | Mapping required | |
| Activity (calls, emails, meetings, notes) | Activity on Person or Account1:1 | Fully supported | |
| User | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Sentia gotchas
Multiple unrelated entities share the Sentia brand
Tier-gated API surface affects migration completeness
Voice workflow configurations are not portable
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and tier selection
We audit the source Sentia account for active tier (Basic/Starter/Ultimate), record counts across Contacts, Companies, Leads, Deals, and Activities, custom field definitions, pipeline and stage configurations, and active user count. We pair this with a Nutshell tier review: Foundation ($13/user) covers standalone CRM with no API; Pro ($42/user) covers up to 5 pipelines and workflow management; Enterprise ($79/user) is required for API access, unlimited pipelines, and custom field limits. The discovery output is a written migration scope and a Nutshell tier recommendation.
Lead-to-People merge rule and field mapping
We define the merge rule for Sentia Leads into Nutshell People during scoping. Every Sentia lead status value maps to a Nutshell Person Type. Lead source and original lead status are preserved as custom fields on the Nutshell Person record. We map Sentia Contact fields to Nutshell Person fields and Sentia Company fields to Nutshell Account fields. Pipeline stages are mapped by name with customer confirmation. Custom field types from Sentia are mapped to Nutshell field types, with type-conversion logic applied where the target field type does not support the source format.
User reconciliation and owner assignment
We extract every distinct Sentia User referenced on Contacts, Companies, Deals, and Activities and match by email against the Nutshell destination's User table. Users without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision. We confirm whether inactive Sentia users should be mapped to inactive Nutshell users or archived. Owner assignment on imported records uses the resolved User mapping; any unresolved owners are assigned to a migration admin placeholder and flagged for manual reassignment.
Sandbox migration and reconciliation
We run a full migration into a test Nutshell account using production-like data volume. The customer reviews record counts, spot-checks 25-50 random records against the Sentia source, and confirms the Lead merge, pipeline mapping, and custom field values. Any mapping corrections are made before production migration begins. This step validates that the Lead-to-People merge produces the expected Person Type distribution and that no duplicate People records are created from email collisions.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Sentia Companies), People (with Lead merge applied, Account link resolved), Deals (with People and Account links resolved, stage mapping applied), Activities (linked to the resolved People and Account records). Each phase emits a row-count reconciliation report before the next phase begins. We flag any Sentia Activities with no linked Contact for manual review before finalizing.
Cutover, validation, and automation rebuild handoff
We freeze Sentia writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a JSON export of Sentia voice workflow definitions and automation rules for manual rebuild in Nutshell. Workflows and automations do not migrate as code; the customer rebuilds these using Nutshell's workflow builder (available on Pro and above). We support a one-week hypercare window for reconciliation issues raised by the customer's team.
Platform deep dives
Sentia
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Sentia and Nutshell.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Sentia: Not publicly documented — confirmed during scoping. Effective limits are bounded by the underlying CRM's published rate quotas since Sentia reads/writes through that platform's API..
Data volume sensitivity
Sentia doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Sentia to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Sentia to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Sentia
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
