CRM migration
Field-level mapping, validation, and rollback between Soffront and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Soffront
Source
Nutshell
Destination
Compatibility
10 of 12
objects map 1:1 between Soffront and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Soffront to Nutshell is a simplification migration for teams that find Soffront's deep customization overhead outweighing its flexibility. Nutshell offers a cloud-only, per-user model with unlimited contacts at every tier, making it predictable for growing sales teams. Soffront's custom field names, picklist values, and on-premise versus cloud edition differences mean every migration requires a discovery field inventory before any record moves. We handle Soffront's 500-record API rowcount ceiling through cursor-based pagination, preserve Activity history across calls, emails, meetings, and tasks, and flag the absence of native Projects and Knowledge Base objects in Nutshell. Soffront Workflows, Knowledge Base articles, and Group-based permissions do not migrate; we deliver written inventories for admin rebuild.
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 Soffront 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.
Soffront
Contact
Nutshell
Person
1:1Soffront Contacts map to Nutshell People. Standard fields (name, email, phone, address) map directly. Soffront Group assignments and tags are preserved in Nutshell People as custom multi-select picklist fields if the Nutshell People custom field schema is extended during migration. Soffront lifecycle stage values map to Nutshell status values (Lead, Customer, etc.). The HubSpot-style contact-account relationship in Soffront maps to Nutshell People linked to Companies.
Soffront
Account
Nutshell
Company
1:1Soffront Accounts represent organizations linked to Contacts. They map to Nutshell Companies. The Account-Contact relationship becomes the Nutshell People-Company association. All standard fields including industry, size, and custom properties map to Nutshell Company custom fields.
Soffront
Deal
Nutshell
Opportunity
1:1Soffront Deals track opportunities through pipelines with custom stages, amounts, and owners. They map to Nutshell Opportunities. Stage names vary between Soffront instances so we perform a value-mapping exercise during discovery before import to align stage names and probabilities with Nutshell's pipeline stage values.
Soffront
Deal Stage
Nutshell
Opportunity Stage
lossySoffront pipeline stages map to Nutshell pipeline stages. Each Soffront pipeline becomes a Nutshell pipeline. Stage probability percentages from Soffront map to Nutshell stage probability values. If Soffront has custom stage names (e.g., 'Proposal Sent - Awaiting Review'), we create matching Nutshell stages during the pre-migration configuration phase.
Soffront
Activity: Call
Nutshell
Call
1:1Soffront call activities map to Nutshell Call records. Duration, disposition, and outcome from Soffront map to Nutshell Call duration and result fields. Activity timestamps are preserved. Calls are linked to the target Person (from migrated Soffront Contact) at migration time.
Soffront
Activity: Email
Nutshell
Soffront email activities map to Nutshell Email records linked to the target Person. Email subject, body, and timestamp migrate directly. Attachments migrate as separate file references. Nutshell's email threading model associates emails with the relevant Person record.
Soffront
Activity: Meeting
Nutshell
Meeting
1:1Soffront meeting activities map to Nutshell Meeting records. Start time, end time, location, and title migrate directly. Attendees are resolved to Nutshell Person records via the contact mapping. Meeting notes from Soffront migrate as the Nutshell meeting description.
Soffront
Activity: Task
Nutshell
Task
1:1Soffront tasks map to Nutshell Task records. Status, priority, due date, and description migrate directly. Task assignment in Soffront is resolved to the Nutshell user match via owner email lookup. Completed-at timestamp is preserved.
Soffront
Project
Nutshell
Custom Fields or External Tool
1:1Soffront Projects with milestones, resources, and due dates have no native Nutshell equivalent. Nutshell does not include project management. During scoping we assess whether the customer wants Projects reconstructed as Nutshell custom fields on Opportunities (for project-type deals) or migrated to a separate project management tool. Milestone names and due dates can be stored as a formatted text field or JSON blob on a custom Nutshell object if Enterprise API access is licensed.
Soffront
Ticket
Nutshell
Case
1:1Soffront support tickets with status, priority, assignee, and conversation history map to Nutshell Cases if the destination Nutshell account includes the customer service module. Ticket pipeline stages become Case status values. Conversation history migrates as Case comments or as linked Email records.
Soffront
Knowledge Base
Nutshell
External Documentation
1:1Soffront Knowledge Base articles storing solutions linked to ticket types have no Nutshell equivalent. Nutshell does not include a Knowledge Base. We export articles with their category assignments during discovery and deliver a written handoff document listing each article and its category for the customer's admin to recreate in a shared documentation tool (Confluence, Notion, or similar). This is not a code migration; it is a content inventory.
Soffront
Custom Object
Nutshell
Custom Fields on Standard Objects
lossySoffront custom objects beyond the standard data model (e.g., Vehicles, Properties, Subscriptions) require schema inspection at the start of each migration. We map them to Nutshell custom fields on People, Companies, or Opportunities depending on the object's nature. If the custom object has relationships to standard objects, we replicate the relationship as a lookup custom field in Nutshell.
| Soffront | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Deal Stage | Opportunity Stagelossy | Fully supported | |
| Activity: Call | Call1:1 | Fully supported | |
| Activity: Email | Email1:1 | Fully supported | |
| Activity: Meeting | Meeting1:1 | Fully supported | |
| Activity: Task | Task1:1 | Fully supported | |
| Project | Custom Fields or External Tool1:1 | Fully supported | |
| Ticket | Case1:1 | Fully supported | |
| Knowledge Base | External Documentation1:1 | Fully supported | |
| Custom Object | Custom Fields on Standard Objectslossy | 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.
Soffront gotchas
API rowcount defaults to 500 records per call
Workflow definitions tied to Main Objects require recreation
Knowledge Base articles must be mapped to destination KB categories
Custom field names vary between Soffront instances
On-premise and cloud editions have different import/export paths
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 edition determination
We audit the source Soffront instance across edition (Online or On-Premise), custom field inventory, pipeline count, workflow count, and record volumes per object. We also assess whether Projects and Knowledge Base content are in active use and require a reconstruction plan. The discovery output is a written migration scope, a custom field mapping document, and a Nutshell plan recommendation based on the customer's team size and feature needs.
Custom field schema pre-creation in Nutshell
We create all custom fields in Nutshell before any data import begins. Custom fields on People, Companies, and Opportunities are pre-provisioned via the Nutshell API or admin interface. Picklist values are mapped from Soffront picklists and created as matching Nutshell picklist values. The schema is validated against the field inventory before extraction begins.
Paginated extraction with rowcount handling
We extract all records from Soffront using cursor-based or offset pagination to handle the 500-record rowcount ceiling. Records are extracted in dependency order: Contacts and Accounts first (for Person-Company lookup resolution), then Deals, then Activities. Each extraction batch is validated for row count against the discovery-phase estimate. Extracted records are staged in a migration workspace before transform.
Transform, value mapping, and owner reconciliation
We transform Soffront record data to match Nutshell's field types and naming conventions. Picklist values from Soffront are mapped to Nutshell picklist values. Soffront Owners are resolved by email match against Nutshell users. Any Owner without a matching Nutshell user is flagged in a reconciliation queue for the customer's admin to provision. Activity timestamps are preserved in their original format.
Sandbox migration and validation
We run a full migration into a Nutshell test account or sandbox environment using representative data volume. The customer's admin spot-checks 25-50 random records for field accuracy, correct Person-Company associations, and activity timeline completeness. Any mapping corrections are applied before production migration begins.
Production migration and cutover
We run production migration in dependency order: Companies (from Soffront Accounts), People (from Soffront Contacts with Company lookup resolved), Opportunities (from Soffront Deals with OwnerId resolved), Activity history (Calls, Emails, Meetings, Tasks via Nutshell API). We freeze Soffront writes during the cutover window and run a final delta migration for records modified during the migration. We do not migrate Projects, Knowledge Base, or Workflows; these are delivered as written inventories for the admin to rebuild.
Workflow and content inventory handoff
We deliver a written inventory of every active Soffront Workflow with its trigger conditions, actions, and recommended Nutshell automation equivalent. We deliver a structured export of Knowledge Base articles with their categories and linked ticket types for recreation in a documentation tool. We deliver a Projects inventory with milestones and resource assignments for reconstruction as Nutshell custom fields or a separate PM tool. Post-migration support is limited to a one-week window for reconciliation issues.
Platform deep dives
Soffront
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 5 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 Soffront and Nutshell.
Object compatibility
5 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
Soffront: Not publicly documented; rowcount parameter caps results at 500 records per call by default.
Data volume sensitivity
Soffront exposes a bulk API — large-volume migrations stream efficiently.
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 Soffront to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Soffront 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 Soffront
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.