Migrate from RSoft CRM to Nutshell

RSoft Company records map directly to Nutshell Account (API name). We extract company name, industry, size, address, and owner fields from the RSoft CSV export and map them to Nutshell's standard Account fields. Account is imported first in the sequence so that the Account-People relationship is satisfied at the moment of People import. The company name serves as the dedupe key during insertion to prevent duplicate Account creation if multiple RSoft Contacts share the same company.

RSoft Contact maps to Nutshell People. We map name, email, phone, address, lifecycle stage, and owner fields. RSoft's lifecycle stage property migrates as a custom People field in Nutshell since Nutshell People do not have a native lifecycle stage property. If multiple RSoft Contacts share the same company, each Contact generates a separate People record linked to the same Account via Nutshell's map relationship.

RSoft Lead records map to Nutshell Lead. We map lead source, status, score, assigned owner, and associated activities. RSoft's lead-to-contact conversion record is preserved as a comment or note in Nutshell's Lead timeline since Nutshell Lead does not have an explicit Convert action equivalent. The customer's admin reviews converted leads post-migration to confirm the Contact creation in Nutshell People.

RSoft Deals map to Nutshell Opportunity. We map deal name, pipeline stage, amount, probability, expected close date, and owner. RSoft's drag-and-drop pipeline builder with custom stage names maps to Nutshell's pipeline stage configuration. The owner field resolves via email match against the Nutshell user roster during import. Deals without a valid Contact or Company reference in RSoft are flagged as orphaned and held for customer review before insertion.

RSoft's custom stage names and reorderable stages per pipeline are extracted and recreated as Nutshell pipeline stages. Each RSoft pipeline becomes a Nutshell pipeline with its stage labels preserved. Stage probabilities migrate to Nutshell's probability values. We configure the pipeline in Nutshell before Deal import so that stage values are valid at the moment of Opportunity insertion.

RSoft Activities (calls, emails, SMS, and notes logged against Contacts, Leads, or Deals) map to Nutshell Activities attached to the corresponding People, Lead, or Account record. Activity timestamps preserve to maintain the timeline order that sales reps rely on. Note: RSoft IVR call recordings stored in the IVR module do not appear in the standard CSV export and are flagged as a separate file-transfer requirement. Email logs migrate as Activity records with content preserved in the notes field.

RSoft Ticket records (from RSoft's Ticket Management module handling requests from email, online, phone, chat, and social) map to Nutshell Tasks linked to the relevant People or Account record. Ticket subject, status, priority, and assignee migrate. RSoft custom ticket fields beyond the plan tier limit require manual recreation in Nutshell as custom fields on the Task object. If RSoft ticket conversations include message threads, those migrate as Notes attached to the Task.

Tags on RSoft Contacts, Leads, and Deals migrate as Nutshell Tags. We deduplicate tags during import to avoid redundant tag creation. Tags serve as the primary segmentation mechanism in Nutshell for list-building and filtering, so we preserve the full tag set from RSoft to maintain existing filters and reports in the new system.

RSoft custom fields capped at 5 on Standard and Advanced plans migrate to Nutshell custom fields on the corresponding object (People, Account, Opportunity, Lead). We audit the customer's RSoft plan tier during discovery and extract all custom field names and types. Fields exceeding the destination plan limit are documented in the migration inventory for the customer to recreate as Nutshell custom fields post-migration. Type mapping: RSoft text maps to Nutshell text, RSoft dropdown maps to Nutshell dropdown, RSoft date maps to Nutshell date.

RSoft user accounts map to Nutshell Users referenced in the Owner field on Deals, Contacts, Leads, and Tickets. We extract the full RSoft user roster and match each by email against the Nutshell destination user list. Any RSoft Owner without a matching Nutshell User is held in a reconciliation queue for the customer to provision before record import resumes. Orphaned owner references are flagged in the migration report and must be resolved before Deals and Contacts can be inserted with valid owner assignments.