Migrate from SoulCRM to Salesforce Sales Cloud

SoulCRM Company records map directly to Salesforce Account. SoulCRM's company_name becomes Account Name; phone and email fields map to standard Account fields. Regional segment data from SoulCRM custom fields (state, city, territory) become Salesforce custom fields on Account. Company is imported first because Contacts and Deals both reference it as a foreign key. SoulCRM does not distinguish between business Accounts and individual consumers, so no Person Account split is required unless the customer's data includes consumer records.

SoulCRM Contact records map to Salesforce Contact with AccountId resolved to the migrated Account. SoulCRM's contact status (Active/Inactive) maps to a custom Contact field rather than the deprecated isDeleted pattern. GST-related contact fields (business GSTIN if applicable) migrate to a custom field on Contact. We deduplicate by email during import to avoid creating duplicate Contact records for customers who appear in multiple SoulCRM modules.

SoulCRM Lead records map to Salesforce Lead. Lead status from SoulCRM (New, Contacted, Qualified, Converted) maps to Salesforce Lead Status with a custom field soulcrm_original_status__c preserving the source value. Source attribution fields (Lead Source, Campaign Reference) migrate to standard Salesforce LeadSource and a custom campaign reference field.

SoulCRM Deal records map to Salesforce Opportunity with AccountId and OwnerId resolved at migration time. Deal stage names map to Salesforce StageName values; stage probabilities are mapped explicitly per stage using a configuration table. Deal amount migrates to Amount; expected close date migrates to CloseDate. SoulCRM's custom deal fields (product line, deal type, regional segment) map to custom Opportunity fields.

Each SoulCRM pipeline stage becomes a Salesforce StageName entry in a new Sales Process. We configure StageProbability values to match SoulCRM's probability percentages rounded to integers. The Sales Process is assigned to the Opportunity Record Type during migration. Any custom stage fields (stage_changed_date, stage_notes) migrate to custom Opportunity fields.

SoulCRM email activities migrate to Salesforce EmailMessage records (body content) linked to an Activity Task record. The WhoId points to the migrated Lead or Contact; WhatId points to the related Account or Opportunity. Email direction (Sent/Received) is preserved in a custom field. Email body content may require HTML normalization depending on the original encoding in SoulCRM exports.

SoulCRM call logs migrate to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and outcome fields from SoulCRM map to custom Task fields. ActivityDate is set to the original SoulCRM call timestamp to preserve timeline ordering. Call recording URLs (if stored as external links in SoulCRM) migrate to a custom field on the Task record.

SoulCRM task activities map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving SoulCRM owner references to Salesforce OwnerId via the User email lookup. Completed tasks retain their completion timestamp as ActivityDate.

SoulCRM file attachments linked to Contacts, Companies, or Deals migrate as Salesforce ContentVersion blobs uploaded to the destination org. Each file gets a ContentDocumentLink junction record pointing to the migrated parent record (Contact, Account, or Opportunity). Folder hierarchy from SoulCRM is not preserved; all files land in the destination record's file list without nested folders.

SoulCRM custom fields capturing India-specific GST identifiers require pre-creation of custom fields in Salesforce before migration begins. GSTIN format (15-character alphanumeric with state code, PAN, entity number, and checksum) can be validated using a Salesforce custom validation rule with a REGEX pattern. We recommend creating soulcrm_gstin__c on Account as a Text(15) field with the validation rule active after migration.

SoulCRM regional segment fields (state, city, sales territory, zone) map to Salesforce custom fields on Account or Opportunity. We recommend a Picklist or Multi-Select Picklist for territory and zone fields to enable reporting by region. If SoulCRM uses a hierarchical regional structure, we flatten it to a text or picklist field in Salesforce based on the customer's reporting requirements.

SoulCRM Marketing Campaign records (name, type, start/end dates, budget) map to Salesforce Campaign. Campaign membership links (which Contacts or Leads were members of which campaigns) migrate as CampaignMember records. We resolve Contact and Lead references by email during the CampaignMember import phase. CampaignMember Status values (Sent, Responded, Converted) map from SoulCRM membership status fields.