Migrate from SoulCRM to Nutshell

SoulCRM Companies map directly to Nutshell Companies. The Company name becomes the Company name field, address and contact information map to standard Nutshell Company fields. We import Companies first in the migration sequence because Contacts and Deals reference them via lookup relationship. Any SoulCRM custom fields capturing India-specific data (regional segments, GST registration status) map to Nutshell custom fields on Company, which Nutshell documents as mappable during data imports.

SoulCRM Contacts map to Nutshell People. The Contact's name, email, phone, and address fields map to equivalent Nutshell Person fields. We import Contacts after Companies to satisfy the Company lookup reference. SoulCRM's integrated telephony and email capture data migrates as contact metadata on the Person record. Any custom contact fields (department, secondary phone) map to Nutshell Person custom fields.

SoulCRM Leads map to Nutshell People with the Lead status flag preserved as a custom field or tag. The Marketing Module's lead capture forms generate Lead records that migrate as People with lead classification maintained. Lead source and assignment fields from SoulCRM map to Nutshell Person custom fields to preserve marketing attribution data.

SoulCRM Deals map to Nutshell Opportunities. The deal amount, probability, and stage map to Nutshell Opportunity fields. SoulCRM pipeline stage names are mapped to Nutshell pipeline stage values during import. Deal owner assignments resolve to Nutshell User records by email match. We import Deals after Companies and Contacts so that the Opportunity-Company relationship is satisfied at insert time.

SoulCRM Activity records (email, call, task) map to Nutshell Activity records linked to the parent Person or Company. Call disposition, duration, and timestamp preserve from SoulCRM fields. Email content and task notes migrate as Activity description fields. Activity type classification maps to Nutshell Activity types. We resolve the parent record reference (Person or Company ID) using the SoulCRM record's related contact or company field before inserting.

SoulCRM Marketing Module campaigns (name, type, start/end dates, budget) map to Nutshell Campaigns. Campaign membership linking Contacts and Leads to campaigns requires separate association records during import. We export campaign membership as a separate mapping table and create Nutshell Campaign membership records after both the Campaign and People imports complete. Note that Nutshell's marketing automation features are scoped separately from core CRM migration.

SoulCRM custom fields for India-specific data (GST identifiers, regional segments, industry categories) require pre-creation in Nutshell before data import. We review each SoulCRM custom field for active usage, create equivalent Nutshell custom fields on the appropriate object (Company or Person), and map the field values during the CSV-to-Nutshell import. Deprecated custom fields with zero usage are excluded from migration scope.

File attachments linked to SoulCRM Contacts, Companies, or Deals migrate as binary blobs re-uploaded to the corresponding Nutshell record. We extract attachments during CSV export, re-upload using Nutshell's API, and link them to the migrated parent record. Folder hierarchy from SoulCRM may flatten in Nutshell; we document any structural loss for the customer's admin to address post-migration if necessary.

SoulCRM Owners referenced on Deals, Contacts, and Companies resolve to Nutshell User records by email match. We extract the distinct owner list from SoulCRM, match each by email against the Nutshell destination, and flag any owner without a corresponding Nutshell User for the customer's admin to provision before the migration runs. Owner assignment on Opportunities and Activities requires a valid User reference at insert time.