Migrate from Claritysoft to Microsoft Dynamics 365 Sales

Claritysoft Contacts map 1:1 to Microsoft Microsoft Dynamics 365 Sales Contact. The standard fields (FullName, Email, BusinessPhone, Address) migrate directly. We resolve the parent Account reference at migration time by matching AccountName to a pre-created Account record. Any Claritysoft contact without a matching Account is flagged in the reconciliation report for the customer admin to resolve before final import.

Claritysoft Accounts (called Companies in some CRM exports) map directly to Microsoft Dynamics 365 Sales Account. AccountName becomes the Account Name field; Website, Industry, and Address fields map by name. Account is created before any Contact import so the AccountId Lookup relationship is satisfied at Contact insert time. We use AccountName as the dedupe key during ingestion.

Claritysoft Leads with lifecycle stages (New, Contacted, Qualified) map to Microsoft Dynamics 365 Sales Lead. The Claritysoft lifecycle stage property maps to a custom Lead field lcs_original_lifecycle__c for audit, and the Lead Status maps to Microsoft Dynamics 365 Sales Lead Status with the closest equivalent value. We preserve the original lifecycle stage value for reporting continuity.

Claritysoft Opportunities map to Microsoft Dynamics 365 Sales Opportunity with Amount, StageName, CloseDate, and Probability preserved. The parent AccountId is resolved by matching AccountName. Pipeline Stage names from Claritysoft map to configured Opportunity Stage values in Microsoft Dynamics 365 Sales . We pre-create the stage values in the destination Sales Process during schema setup so the import does not fail on invalid picklist values.

Claritysoft pipeline stages map to Microsoft Dynamics 365 Sales Opportunity Stage values within a configured Sales Process. We create the Sales Process during schema setup, add the Claritysoft stage names as Stage values with corresponding probability percentages, and whitelist the stages per Record Type if the customer uses multiple sales processes. Stage order is preserved from the source pipeline.

Claritysoft Activities (Tasks, Calls, Meetings) with timestamps and linked records migrate to Microsoft Dynamics 365 Sales as Task (for Tasks and Calls) and Event (for Meetings). Call duration and disposition migrate as custom Task fields. Meeting start and end times migrate to Event StartTime and EndTime. The linked record reference (Contact, Account, Opportunity) resolves to the WhoId or WhatId on the target Dynamics record using the pre-resolved ID mapping from the Contacts, Accounts, and Opportunities phases.

Claritysoft documents attached to multiple record types are extracted as files and re-associated in Microsoft Dynamics 365 Sales via SharePoint document libraries (the native integration) or as Note records with file attachments. We flag this as mapping work because Microsoft Dynamics 365 Sales requires SharePoint to be configured for document management before the integration is active, and the customer's admin sets up the SharePoint location during migration scoping.

Claritysoft Custom Fields map to custom fields on the corresponding Microsoft Dynamics 365 Sales entity in Dataverse. Field type mapping follows: text fields to Text, numeric fields to Number or Decimal, date fields to DateTime, and dropdown fields to Option Sets. We pre-create the custom field schema in the destination environment before any record import so that values are accepted on insert.

Claritysoft Custom Modules (Accelerator and Enterprise tier) map to Dataverse custom tables in Microsoft Dynamics 365 Sales . We create the custom table with the equivalent columns during schema setup, map the module data row-by-row, and configure any lookup relationships to standard entities (Account, Contact, Opportunity) using the pre-resolved ID mapping. Custom Modules built with Advanced Custom Fields or Calculated Custom Fields require manual schema review because calculated logic does not migrate.

Claritysoft Project Management (Accelerator and above) does not have a native Microsoft Dynamics 365 Sales equivalent. We migrate project structure (name, milestones, tasks, assignees) to a Dataverse custom table, or the customer integrates Project for the Web separately post-migration. Project-specific metadata and progress tracking flags are noted in the inventory for the admin to evaluate.

Claritysoft Helpdesk Management tickets (Accelerator and above) with status, priority, assignees, and conversation threads migrate to a Dataverse custom table or to a Case entity if the destination org includes Dynamics 365 Customer Service. Conversation threads migrate as Notes or as a custom activity log. Custom ticket fields and priority levels map to equivalent custom fields or Option Set values in the destination.

Claritysoft Users who own records (Contacts, Accounts, Opportunities, Activities) map to Microsoft Dynamics 365 Sales User records by email match. We generate an owner reconciliation report listing every distinct Claritysoft owner and the count of records they own. Owners without a matching Dynamics 365 User go to a provisioning queue for the customer admin before the Opportunity and Activity migration phases run, because OwnerId is a required reference on Opportunity.