Migrate from Sharp CRM to Salesforce Sales Cloud

Sharp CRM Contacts with no company association or with a prospect-level status map to Salesforce Lead. Sharp CRM Contacts attached to a Company record map to Salesforce Contact tied to the corresponding Salesforce Account. We preserve the original Sharp CRM contact record ID in a custom field sharp_crm_id__c on both Lead and Contact for audit and reconciliation. Email, phone, address, and standard name fields migrate directly; any industry-specific custom fields on Contact are enumerated and mapped by data type during scoping.

Sharp CRM Company records map directly to Salesforce Account. The Company record is the first object imported so that AccountId is available for Contact resolution during the contact import phase. Company name becomes Account Name; domain data becomes Website. Sharp CRM custom fields on Company (industry classification, annual revenue, employee count) migrate to equivalent Salesforce Account fields or custom Account fields pre-created during schema design.

Sharp CRM Deals map to Salesforce Opportunity. Deal name becomes Opportunity Name; deal value maps to Amount; expected close date maps to CloseDate. The Sharp CRM pipeline stage name maps to Salesforce StageName using the explicit stage-mapping table built during scoping, where each Sharp CRM stage is matched to a Salesforce stage and assigned the correct probability percentage. Deal owner resolves to Salesforce OwnerId via email lookup against the User mapping.

Sharp CRM pipeline stages are per-customer configurations that do not export with a standard schema. During scoping we ask the customer to provide their current stage names and order, then build an explicit stage-mapping table that assigns each Sharp CRM stage to a Salesforce StageName and StageProbability. This table is deployed to the Salesforce org before any Deal records are imported, ensuring that Opportunity Stage is valid on insert and no validation rules reject records.

Sharp CRM Tasks map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignee resolves to Salesforce OwnerId via email match against the User mapping. Completed tasks retain their Status; open tasks migrate as-is. Sharp CRM task description migrates to Task Description. Tasks without a resolvable assignee are assigned to the migration service user and flagged for admin reassignment post-migration.

Sharp CRM Activities by type map to Salesforce equivalents: call engagements map to Task with TaskSubtype=Call and CallDurationInSeconds preserved; email engagements map to EmailMessage records linked to a Task; meeting engagements map to Event with StartDateTime and EndDateTime preserved; note engagements map to Salesforce Note linked via ContentDocumentLink. Activity type and timestamp are preserved; body content migrates as plain text. All activities require WhoId (Contact or Lead) and optionally WhatId (Account or Opportunity) to be resolved at migration time, which requires the Contact/Lead import to complete first.

Sharp CRM User records (name, email, role) migrate to Salesforce User lookup entries. We match Users by email address against the destination Salesforce org's User table. Any Sharp CRM User without a matching Salesforce User is held in a reconciliation queue; the customer's Salesforce admin provisions missing Users before record import resumes. Active/inactive status is preserved; the customer's admin confirms the active User count for Salesforce seat licensing post-migration.

Sharp CRM tags on Contacts and Deals are exported as tag arrays and mapped to Salesforce multi-select picklist fields on the equivalent object. The customer chooses during scoping whether tags migrate as a single multi-select picklist field or as Salesforce Topics with TopicAssignment records. Tag preservation is informational rather than functional since Salesforce's tagging model differs from Sharp CRM's.

File attachments associated with Sharp CRM Contacts, Companies, or Deals are exported to a file store with their parent record ID reference. We link them in Salesforce via ContentDocument and ContentDocumentLink, associating each document with the migrated Contact, Account, or Opportunity record. Attachment filenames are preserved as ContentDocument titles. Large attachments (over 25 MB) may require Salesforce file size handling adjustments.

Sharp CRM custom fields on Contact are enumerated during scoping, classified by Salesforce data type (text, number, date, picklist, checkbox, phone, email), and mapped to pre-created Salesforce custom fields on the Contact or Lead object. Any custom fields without a clear Salesforce match are flagged for the customer to resolve before import. Industry-specific fields (patient ID, license number, property type) receive explicit mapping documentation.

Sharp CRM custom fields on Company are enumerated and mapped to pre-created Salesforce custom fields on Account. Industry-specific company fields (NAICS code, brokerage license, insurance carrier ID) are mapped explicitly with field-level transform notes. Custom field API names in Salesforce follow the __c suffix convention and must be pre-created before data import begins.

Sharp CRM custom fields on Deals are mapped to pre-created custom fields on Salesforce Opportunity. Any custom picklist values in Sharp CRM are matched to Salesforce picklist values; unmapped values are flagged as data exceptions for the customer to resolve before import. Deal-specific fields like referral source, closing agent, or property address are mapped individually with transform notes.

Sharp CRM automation rules (follow-up sequences, lead nurturing flows, campaign triggers) do not export as records and are not migrated to Salesforce Flow. We document every active automation observed during the discovery call, including trigger conditions, action sequence, delay rules, and CRM object affected. The customer receives a workflow reconstruction guide with prioritized rebuild recommendations for Salesforce Flow, which the customer's admin or a Salesforce partner implements post-migration.

Sharp CRM's email marketing module (bulk emailer) is flagged as loosely integrated with the CRM core per user reviews. Email subscription preferences and contact-level opt-out flags migrate to Salesforce HasOptedOutOfEmail and to CampaignMember Status if campaign history is being preserved. The customer decides whether to move email marketing to Salesforce Marketing Cloud Account Engagement (Pardot) or a third-party platform; we provide the data mapping for that decision separately.