Migrate from Clientify to Salesforce Sales Cloud

Clientify's Contact object is a unified record with lifecycle stage, source, and score properties. Salesforce separates unqualified prospects into Leads and qualified contacts into Contacts attached to Accounts. We define the split rule during scoping using Clientify's lifecycle stage values and create a custom field original_lifecycle_stage__c on both the Lead and Contact record for post-migration audit and reporting continuity.

Clientify maintains a distinct Lead object separate from Contact, with source, status, and score fields. We map these directly to Salesforce Lead fields including LeadSource, Status, and a custom lead_score__c field. The Salesforce Lead Status picklist values are pre-configured during schema design to match Clientify's status vocabulary.

Clientify Companies map to Salesforce Account. The company domain stored in Clientify becomes the Account Website field and serves as the dedupe key. We create Account records before Contact import so that AccountId Lookup is satisfied at the moment of Contact insert. Industry, size, and address fields migrate directly.

Clientify Deals map to Salesforce Opportunity with deal name, value, stage, owner, and expected close date preserved. We resolve the AccountId lookup at migration time using the Contact-to-Account relationship, and OwnerId by email matching against the Salesforce User table.

Clientify pipeline stages are label strings. We create a Salesforce Sales Process with StageName values that match the Clientify stage sequence and assign probability percentages rounded to Salesforce-allowed integers. Each HubSpot pipeline becomes a Salesforce Record Type with its own Sales Process whitelisting the relevant stage values.

Clientify's multiple pipelines map to Salesforce Opportunity Record Types, each with a corresponding Sales Process and Page Layout. Stage probability mappings are preserved per pipeline so that weighted pipeline values in Salesforce reports match what the team saw in Clientify.

Clientify activity records (calls, emails, meetings, task notes) migrate to Salesforce Task with TaskSubtype set to Call, Event with proper StartDateTime and EndDateTime, EmailMessage for email content, and Note for free-text notes. We resolve WhoId (Contact or Lead) and WhatId (Account or Opportunity) for each activity at migration time. ActivityDate is preserved from the Clientify timestamp to maintain timeline ordering.

Clientify tags stored as multi-checkbox properties on contacts and companies migrate to Salesforce multi-select picklist fields. The customer selects whether tags land on Contact, Account, or both during scoping. Tags used for segmentation are preserved as-is; dynamic segment definitions tied to Clientify filters must be rebuilt in Salesforce as filtered views or custom list views.

Clientify custom fields on contacts, companies, and deals map to Salesforce custom fields with type-mapped equivalents. Picklist fields require pre-creation of the picklist values in Salesforce before import begins; otherwise records will be rejected. We coordinate with the customer's Salesforce admin during schema design to prepare all picklist value sets and any required-field flags.

Clientify email templates with dynamic merge field placeholders export as text bodies. We preserve the template structure and body copy. Dynamic merge field names require remapping to Salesforce merge field syntax (e.g., {{first_name}} becomes {!Contact.FirstName}) as a post-migration admin task since field mapping conventions differ between platforms.

Document attachments linked to contacts, deals, or companies migrate as ContentVersion records attached via ContentDocumentLink to the parent record. Large files or attachments stored outside Clientify's native file system may not have exportable URLs; we flag any missing attachment URLs during the scoping export audit.

Clientify user records (name, email, role) are exported and matched by email against the Salesforce destination org User table. Any Clientify owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId is a required reference on most standard Salesforce objects.

WhatsApp message threads linked to Clientify contact records migrate as available. Full conversation history exportability depends on Clientify's API at migration time. We extract available metadata (timestamps, participant IDs, message count, available message body text) and flag any gaps in the scoping report. Media attachments, delivery receipts, and read receipts are preserved where exportable. Salesforce has no native WhatsApp channel, so the customer should plan a replacement WhatsApp integration (Twilio, Salesforce Messaging for WhatsApp, or a native WhatsApp Business API connector) post-migration.

Clientify workflow automation rules are stored internally with no portable export format. We do not migrate them automatically. We provide a structured workflow audit worksheet during scoping so the customer's admin documents every active rule (trigger, conditions, actions, delays), and a recommended Salesforce Flow equivalent is listed in the handoff document for manual rebuild post-migration.