Migrate from SoulCRM to Microsoft Dynamics 365 Sales

SoulCRM Company records map directly to Microsoft Dynamics 365 Sales Account. The SoulCRM company_name field maps to Account Name; phone maps to Telephone1; website maps to Website URL. We extract Companies first in every migration because Contacts and Deals carry foreign-key references to the parent Company. Any GSTIN or regional_segment custom fields on the Company map to custom attributes on Account (text fields created during schema setup). India-specific address components (state, city, PIN code) map to Address composite fields using the Dataverse address structure.

SoulCRM Contact records map to Microsoft Dynamics 365 Sales Contact. Each Contact's parent_company reference resolves to an Account record via the AccountName dedupe key (or by Company ID if included in the CSV). Email, phone, mobile, and address fields map directly. SoulCRM interaction history (call logs, email captures) attaches to Contact via the Activity timeline migration. We validate email format and phone number normalization during the transform phase to satisfy Dynamics 365 field validation rules.

SoulCRM Leads map to Microsoft Dynamics 365 Sales Lead if the customer maintains a separate pre-qualification stage. Lead fields (firstname, lastname, email, company, phone, source) map to the corresponding Dynamics 365 Lead attributes. We map SoulCRM's lead_status and lead_score custom fields to leadscore and leadsource on Dynamics 365. If the customer uses SoulCRM's Marketing Module for lead capture without a separate Lead object, we migrate the source Leads as Leads in Microsoft Dynamics 365 Sales rather than converting them automatically.

SoulCRM Deals map to Microsoft Dynamics 365 Sales Opportunity. The SoulCRM deal_name maps to Opportunity Name; amount maps to EstimatedRevenue; closed_date maps to CloseDate; owner maps to OwnerId via email match against the Dynamics 365 User table. SoulCRM pipeline stages (e.g., Prospect, Qualified, Proposal, Negotiation, Won, Lost) map to configured Microsoft Dynamics 365 Sales Process stage values. We create a Sales Process in Dynamics 365 for each SoulCRM pipeline before migration so that stage names and probabilities are continuous from day one.

Each SoulCRM Deal pipeline stage maps to a Microsoft Dynamics 365 Sales Process stage entry. Stage probability percentages from SoulCRM migrate to StageProbability on the corresponding OpportunityStage record. Loss reasons and win reasons from SoulCRM custom properties become the LossReason field and a custom Win_Reason__c field on Opportunity. If SoulCRM uses multiple Deal pipelines for different business lines, we configure multiple Record Types and Sales Processes in Dynamics 365, one per pipeline.

SoulCRM activity logs (calls, emails, tasks) map to Microsoft Dynamics 365 Sales Task and Event records. Call activities map to Task with TaskSubtype=Call and CallDurationInSeconds preserved in a custom attribute. Email activity content maps to EmailMessage records linked to the corresponding Contact or Lead. We resolve the regarding_object reference (Contact or Account) at migration time using email or name matching against the already-migrated Contact and Account records. ActivityDate and CreatedOn timestamps are preserved to maintain timeline ordering.

SoulCRM Marketing Module campaigns (name, type, start/end dates, budget) map to Microsoft Dynamics 365 Sales Campaign. Campaign members linking Contacts or Leads to the campaign migrate as CampaignMember records with Status values (Sent, Responded, etc.). SoulCRM campaign member interactions (opens, clicks) do not have a direct Microsoft Dynamics 365 Sales equivalent; we map them as Campaign Activity records with the interaction type as Activity Type. If the customer plans to use Dynamics 365 Marketing separately, we document the campaign object separately for that implementation team.

SoulCRM custom fields (common examples: GSTIN, regional_segment, vertical, channel_partner_type, KYC_status) map to custom attributes (fields) on the corresponding Dynamics 365 entity. We create the custom attribute schema in Dynamics 365 before any data load, matching the field type (text, picklist, integer) to the closest Dataverse attribute type. India-specific fields like GSTIN require a text field with format validation; regional segments typically become Option Set (picklist) fields. Active custom fields (those with data) migrate; zero-value custom fields are documented and optionally excluded.

SoulCRM file attachments linked to Contacts, Companies, or Deals migrate as Microsoft Dynamics 365 Sales Annotation records (notes with file attachments). We extract attachments from the CSV export's file references, convert them to Base64-encoded documentbody values, and insert as Annotation records with the correct objectid and objecttypecode referencing the parent Account, Contact, or Opportunity. Folder hierarchy from SoulCRM flattens into flat attachment lists on each record in Dynamics 365.