Migrate from Clarify CRM to Salesforce Sales Cloud

Clarify has no separate Lead object; all prospects live as Contact records with an internal lifecycle or stage indicator. We design a split rule during scoping: Contacts that never reached active deal stage in Clarify map to Salesforce Lead; Contacts with deal history or advanced lifecycle progression map to Salesforce Contact attached to a parent Account. We preserve any Clarify lifecycle stage value in a custom field clarify_lifecycle_stage__c on both the Lead and Contact for audit and reporting continuity.

Clarify Company records map directly to Salesforce Account. The company domain or name becomes the Account Name and Website field, used as the dedupe key during import. Clarify's AI-populated company details (revenue estimates, employee counts, industry) migrate to standard Account fields or custom fields if no direct Salesforce equivalent exists. We flag any AI-introduced field values with a clarify_ai_enriched__c checkbox for customer review before finalizing the load.

Clarify Deal records map to Salesforce Opportunity. The Clarify deal stage name maps to a Salesforce StageName value, and Clarify's pipeline configuration maps to a Salesforce Record Type or Sales Process that we configure before migration. Deal value, close date, and owner all migrate directly. We resolve the parent AccountId and OwnerId at migration time before Opportunity insert.

Clarify's named pipeline stages map to Salesforce Opportunity Stage values. Each Clarify stage gets a corresponding Salesforce StageProbability value, rounded to the nearest integer allowed by Salesforce. If the customer uses multiple named pipelines in Clarify, each pipeline becomes a Salesforce Record Type with its own Sales Process containing only the relevant stage values.

Clarify call records map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any recording URL transfer to custom Task fields. ActivityDateTime preserves the original Clarify timestamp for timeline ordering. Parent-record resolution links the Task to the migrated Lead, Contact, Account, or Opportunity using the clarify_contact_id or clarify_company_id as a cross-reference during migration.

Clarify email engagement records migrate to Salesforce EmailMessage (the message content) linked to an Activity Task record (the timeline entry). The WhoId on the Task points to the migrated Lead or Contact; the WhatId points to the related Account or Opportunity. Email body and headers migrate as standard fields. We resolve parent-record IDs using the cross-reference table built during the Contact and Account migration phase.

Clarify meeting records map to Salesforce Event. StartDateTime, EndDateTime, and Location migrate directly. Attendee mapping creates EventRelation records linking the Event to the migrated Contacts, Leads, and Users. Clarify meeting attendees without a matching Salesforce User are logged as External Attendees on the Event.

Clarify Notes migrate to Salesforce Note records attached via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Rich text formatting and embedded image URLs migrate as-is. Note body preserves the original creation timestamp for historical accuracy.

Clarify auto-generates meeting summaries from conversation context stored as enriched note content. These are not first-class structured objects in Clarify; they exist as note text with an AI generation flag. We export them as Salesforce Note records with a custom field clarify_ai_summary__c = true so the customer can distinguish AI-generated from manually authored notes. The destination does not interpret these as native AI summaries; they land as text content for human review.

Clarify supports custom fields on Contacts, Companies, and Deals. We export all custom field definitions and values, map field types (text, number, date, currency, multi-select) to equivalent Salesforce field types, and pre-create the custom fields in the destination Salesforce org before migration. Field-level security, page layout assignment, and field-level help text are configured during the schema design phase in the Sandbox org first.

Clarify's tag-based labeling migrates to Salesforce multi-select picklist fields on the relevant object. For tags used for content classification rather than CRM record categorization, we map to Salesforce Topics with TopicAssignment records. The customer chooses the tag strategy during scoping: multi-select picklist preserves tag filtering in Salesforce list views; Topics enable the Topic page and chatter integration.

Clarify Owner records map to Salesforce User by email match. We extract every distinct Owner referenced on Contact, Company, Deal, and Activity record and match against the Salesforce destination org's User table. Any Clarify Owner without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision the corresponding User before record import resumes. Owner resolution must complete before Contact and Opportunity import because OwnerId is a required reference on both.