Migrate from Claritysoft to Salesforce Sales Cloud

Claritysoft Contact records map directly to Salesforce Contact. All standard fields (Name, Email, Phone, Address, Title, Company association via Account lookup) migrate via REST API extraction. We preserve the Claritysoft contact ID in a custom field claritysoft_id__c for audit traceability. Any Profile-Based Layout assignments referencing Contact fields map to the Salesforce Record Type selected for that account.

Claritysoft Account (called Company in Claritysoft) maps 1:1 to Salesforce Account. Account-to-Contact relationships are preserved by importing Account records first, resolving the AccountId on each Contact at migration time. Industry, AnnualRevenue, NumberOfEmployees, Website, and BillingAddress migrate as standard fields. BillingAddress from Claritysoft maps to the Account's BillingAddress; ShippingAddress maps to ShippingAddress.

Claritysoft Leads (distinct from Contacts, with lifecycle stages New, Contacted, Qualified) map to Salesforce Lead. Lifecycle stage values migrate to a custom picklist field claritysoft_lead_stage__c, and Lead Status maps to Salesforce LeadStatus with the closest equivalent state. We flag any Claritysoft Leads that represent existing Contacts in the destination and advise the customer on whether to treat them as duplicate Leads or merge them with existing Contact records post-migration.

Claritysoft Opportunities map to Salesforce Opportunity with Amount, StageName, Probability, CloseDate, and Description preserved. Pipeline Stage assignments from Claritysoft map to a Salesforce Sales Process or Record Type that we configure before migration. We compute the StageName mapping during discovery to ensure the closest equivalent stage exists in the destination. If Claritysoft's pipeline uses stages that have no Salesforce equivalent, we map to the nearest stage and flag the gap in the migration inventory.

Claritysoft Activities include Tasks, Calls, and Meetings with timestamps, owners, and linked records. Calls migrate as Salesforce Task with TaskSubtype=Call and CallDurationInSeconds in a custom field. Meetings migrate as Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee lists migrate via EventRelation records. All activity records use Bulk API 2.0 with WhoId (Contact or Lead lookup) and WhatId (Opportunity or Account lookup) resolved at migration time to prevent orphaned timeline entries.

Claritysoft Documents attached to multiple record types are extracted as binary files and re-associated in Salesforce as ContentVersion records linked via ContentDocumentLink to the parent Account, Contact, Lead, or Opportunity. We flag this as mapping work because Claritysoft's document storage conventions differ from Salesforce's library-based Content model. Customers using Claritysoft's document versioning should expect a flat version history import unless version tracking is explicitly requested.

Claritysoft Custom Fields (Advanced Custom Fields with calculated logic require Accelerator or Enterprise tier) map field-by-field to Salesforce custom fields on the equivalent standard object. We create the Salesforce field schema before import, matching field types: text to Text, number to Number, date to Date, picklist to Picklist. Calculated Custom Fields from Claritysoft do not replicate as calculated fields in Salesforce; we document the calculation logic for the customer to implement as a Salesforce formula field or Flow after migration.

Claritysoft Custom Modules (available on Accelerator and Enterprise tiers) migrate to Salesforce custom objects with __c suffix. We pre-create the destination custom object schema, including all custom fields, lookup relationships to standard objects (Account, Contact, Opportunity), and validation rules before any data import. If the source account is on Professional tier, Custom Modules are not accessible via API; we flag this during scoping and advise the customer to upgrade before migration or use manual export for custom module data.

Claritysoft Pipeline Stages define the sales process steps. We preserve stage names, order, and probability percentages by mapping each to Salesforce Opportunity StageName entries and StageProbability values. If Claritysoft uses multiple pipelines (Accelerator feature), we create Salesforce Record Types per pipeline and assign the corresponding Sales Process to each. Stage mapping is validated in Sandbox before production migration.

Claritysoft Users own records and drive access permissions. We extract all distinct User records and map them to Salesforce Users by email match. API keys inherit the generating user's permission scope, which is why we generate keys from admin-level accounts during migration to maximize coverage. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Claritysoft's Profile-Based Record Layouts assign different field visibility and layout configurations per user role. This has no direct Salesforce equivalent; the Salesforce analog is Record Types (per business process) combined with Page Layouts (per profile and record type) and Field-Level Security (per profile and field). We document each Claritysoft Profile-Based Layout and map it to a Salesforce configuration plan for the customer's admin to implement post-migration.

Claritysoft Workflows automate triggers and actions based on conditions. Date-based Workflow Triggers are an Enterprise-tier feature. We do not migrate Workflows as executable automation because Claritysoft workflow logic and Salesforce Flow use different semantics. We deliver a written inventory of every active Claritysoft Workflow with its trigger conditions, actions, and recommended Salesforce Flow equivalent, including Flow type (record-triggered, scheduled, screen) and action steps. The customer's admin rebuilds them post-migration.