Migrate from RSoft CRM to Freshsales

RSoft Contact records map directly to Freshsales Contact. We map name, phone, email, address, lifecycle stage, and owner fields. If RSoft custom fields exceed the 5-field cap on the customer's current plan tier, we identify orphaned fields during discovery and surface them for the customer to review before import. Email deduplication runs during staging to prevent duplicate Contacts in Freshsales.

RSoft Lead records (captured via web forms, WhatsApp, or manual entry) map to Freshsales Lead with source, status, score, assigned owner, and associated activities. The Lead-to-Contact conversion record from RSoft is preserved as a custom field for audit. RSoft's Lead score migrates as a custom numeric field in Freshsales if the destination plan supports it.

RSoft Company records map to Freshsales Account. We map company name, industry, size, address, and owner. Company-to-Contact relationships are preserved during migration by sequencing Companies first in the load order so that AccountId is resolved at the moment of Contact insert, preventing orphaned Contact records without a parent Account.

RSoft Deals map to Freshsales Deals with pipeline stage, amount, probability, expected close date, and owner preserved. RSoft's custom stage names and reorderable stages per pipeline map explicitly to Freshsales pipeline stages. Closed-Lost and Closed-Won reasons from RSoft custom fields map to Freshsales Deal status fields.

RSoft custom stage names and reorderable stages per pipeline are extracted with their probability percentages and mapped to Freshsales pipeline stages during configuration. Stage-specific automation triggers from RSoft are documented in the automation inventory rather than migrated, since RSoft workflow definitions have no export path.

RSoft Activities (calls, emails, SMS, notes logged against Contacts, Leads, or Deals) map to Freshsales Activity records. Call logs from IVR and autodialer are stored in RSoft-specific modules that do not appear in the standard CSV export, and these are flagged as a data gap during scoping. We migrate standard Activity fields via CSV import with parent-record lookup resolution.

RSoft Ticket records (processing requests from email, online, phone, chat, and social media) map to Freshsales Ticket. We map ticket subject, status, priority, assignee, and conversation threads. Custom ticket fields are limited by plan tier on the RSoft side; we audit and surface any that exceed the customer's plan cap during discovery.

RSoft Tags on Contacts, Leads, and Deals export via CSV and map as tags in Freshsales. We deduplicate tags during the staging phase before import. Tags used for segmentation in RSoft map to Freshsales's tag and segmentation model without transformation.

RSoft user accounts map to Owner fields on Deals, Contacts, Leads, and Tickets. We extract the full RSoft user roster and match by email against Freshsales destination users. Any RSoft owner with no matching Freshsales user enters a reconciliation queue, and the customer's admin provisions the missing user before record import resumes.

RSoft custom fields above the customer's plan cap (5 on Standard and Advanced plans) are identified during discovery and reviewed with the customer before migration. We create equivalent custom fields in Freshsales Growth or above where the tier supports them. Fields that cannot map due to destination plan limits are flagged and documented for the customer to prioritize post-migration.