Migrate from Claritysoft to Freshsales

Claritysoft Contacts migrate directly to Freshsales Contacts. The mapping preserves first_name, last_name, email, phone, mobile_phone, job_title, and address fields. We resolve the Claritysoft account association to a Freshsales Account by domain or name match and set the AccountId on Contact during import. Owner assignment maps from Claritysoft user email to Freshsales User by email lookup. Any Claritysoft contact without a matching Account is imported with the account association flagged for manual resolution.

Claritysoft Accounts (called Companies in some CRM contexts) map to Freshsales Accounts with company_name, domain, industry, annual_revenue, phone, and address fields preserved. We use the Claritysoft Account name or domain as the dedupe key during import to prevent duplicate Accounts. If the Claritysoft account has multiple Contacts, all Contacts link to the single migrated Account record via AccountId resolution during the Contact import phase.

Claritysoft Leads migrate to Freshsales Lead records with the lifecycle stage values (New, Contacted, Qualified) mapped to Freshsales Lead Status picklist values. The original Claritysoft lifecycle stage is preserved in a custom field claritysoft_lead_status__c for audit. If the customer plans to convert Leads in Freshsales post-migration, the status mapping ensures the conversion workflow triggers correctly. We flag any Lead records that lack a last_name or email as incomplete and quarantine them for customer review before import.

Claritysoft Opportunities map to Freshsales Deals with amount, stage_name, probability, expected_close_date, and description preserved. The Claritysoft pipeline association maps to a Freshsales Deal pipeline that we configure before migration, including stage names and stage probabilities. Closed-Lost and Closed-Won status from Claritysoft map to Freshsales stage values with probability 0 and 100 respectively. Deal ownership resolves via email-to-User lookup in Freshsales.

Claritysoft Activities including Tasks, Calls, and Meetings migrate to Freshsales Tasks and Events with timestamps, owners, and linked record associations preserved. Call activities map to Freshsales Tasks with type=Call and the duration stored in a custom field. Meeting activities map to Freshsales Events with start_time, end_time, and location preserved. We link each migrated activity to the corresponding Contact, Account, or Deal via Freshsales's target_object_id and target_entity_type fields. Activity ordering is preserved using the original Claritysoft created_at timestamp.

Claritysoft Custom Fields (defined in Accelerator or Enterprise tiers) map to Freshsales custom fields by equivalent data type: text fields to Freshsales text, number fields to number, date fields to date, and picklist fields to multi-select picklist where appropriate. We run a schema profiling pass during discovery to capture every custom field definition including field type, required flag, and picklist values. Calculated Custom Fields from Claritysoft Accelerator are documented as formulas with their logic preserved in a written field reference; Freshsales does not support formula fields on the same object in the same way, so these require admin-level rebuild or replacement with Freshsales workflows.

Claritysoft Custom Modules (Accelerator and Enterprise only) map to Freshsales Custom Objects with all fields and relationships migrated as custom fields on the equivalent Freshsales object. Custom Module record associations to standard records (Contacts, Accounts, Deals) become Freshsales custom lookup fields pointing to Contact, Account, or Deal. We note that Freshsales Custom Objects are available from the Growth plan ($9/user) with API access, making them more accessible than Claritysoft's tier requirement. Professional-plan Claritysoft accounts do not expose Custom Modules via API, which requires a data-dump-and-import approach for those records.

Claritysoft Users map to Freshsales Users by email address match. Every record imported (Contact, Account, Deal, Activity) references an OwnerId that we resolve against the Freshsales User table at migration time. Users without a match in the destination org are queued for manual provisioning by the customer's Freshsales admin before the record import phase runs. We also preserve the Claritysoft Access Profile and User Group assignments as a written reference document to help the admin configure Freshsales roles and permissions post-migration.

Claritysoft Documents attached to records migrate to Freshsales file attachments. We extract the file content and re-associate it to the migrated Contact, Account, or Deal record using Freshsales's attachment upload API. Document metadata (filename, file type, upload date, attached record type) is preserved. Users should note that Freshsales handles attachments differently from Claritysoft in terms of storage limits per plan, so we flag any unusually large attachment sets for the customer to review before import.