Migrate from Saleshiker to Salesforce Sales Cloud

Saleshiker Leads map directly to Salesforce Lead with full CRUD field preservation. We map the Lead status, source, owner assignment, phone, email, and custom properties. Saleshiker's lead_stage property maps to Salesforce LeadStatus with a mapping table confirmed at scoping. If the customer uses Saleshiker's lead scoring model, we preserve the score in a custom field sh_lead_score__c on the Salesforce Lead.

Saleshiker Contacts map to Salesforce Contact with name, email, phone, lifecycle stage, and owner preserved. Lifecycle stage values (active, inactive, prospect, customer) from Saleshiker map to a custom picklist field sh_lifecycle_stage__c because Salesforce's native Contact model does not have an equivalent lifecycle property. The Contact's parent Organization resolves to the Salesforce Account via the AccountId lookup during import.

Saleshiker's Organizations (company records) map to Salesforce Account. The organization's domain or website becomes the Account's Website field and is used as the deduplication key during import. Account is imported before Contact so that AccountId is available at the moment of Contact insert. Any linked Deals carry the AccountId forward to Opportunity.

Saleshiker Deals map to Salesforce Opportunity. Deal pipeline stage maps to Salesforce StageName via a customer-confirmed mapping table. Deal value, expected close date, owner, and associated Organization all migrate. If the destination org has multiple Sales Processes, we assign the correct RecordTypeId and Sales Process at migration time based on the Saleshiker pipeline name.

Each Saleshiker pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the mapped stage values. Stage probability percentages migrate from Saleshiker's stage configuration to Salesforce StageProbability. The customer approves the stage mapping during scoping before any schema is deployed.

Saleshiker Quotes map to Salesforce Quote (a standard object available from Professional tier). Quote headers and line items migrate with status, totals, and validity dates preserved. Quote PDFs stored in Saleshiker's attachment layer migrate as ContentDocument records linked to the Salesforce Quote via ContentDocumentLink.

Saleshiker Invoice records (headers and line items) migrate with AR/AP status preserved. If the destination org includes Salesforce Billing or a third-party ERP integration, we map invoice status to the equivalent field. Otherwise, we map to a custom Invoice object (sh_invoice__c) with line items as a custom related list (sh_invoice_line__c) to preserve the full invoice structure without requiring the full Billing module.

Saleshiker Products map to Salesforce Product2 with name, SKU, price, and description preserved. Standard Price Book entries are created during migration so that Products are immediately available for Opportunity Line Items. Product SKU from Saleshiker's sku field maps to ProductCode on Product2.

Saleshiker Tasks migrate to Salesforce Task with title, due date, status, priority, and assignment preserved. We resolve the owner reference by matching the Saleshiker owner email to the Salesforce User ID established during the owner reconciliation phase. Tasks linked to Deals map to the migrated Opportunity via WhatId.

Saleshiker Events migrate to Salesforce Event with title, start and end datetime, type, and assignee preserved. Recurrence patterns from Saleshiker events map to Salesforce Event recurrence fields where supported, or are flagged for manual recreation if the pattern exceeds Salesforce's recurrence model complexity. Event attendees map to EventRelation records linked to the migrated Contact or Lead.

Saleshiker Email Campaign records (template name, send date, open/click stats) migrate to Salesforce Campaign with campaign type and status preserved. Basic engagement statistics (opens, clicks, sends) migrate to custom fields on Campaign. Campaign membership—contacts who were added to a campaign—migrates to CampaignMember records with Status preserved (Sent, Responded, Bounced). Detailed email engagement logs that require destination-specific handling are flagged for the customer's admin to review.

Saleshiker attachments stored per record (Lead, Contact, Organization, Deal) migrate to Salesforce ContentDocument and ContentVersion. File binary is downloaded from Saleshiker's storage during export, then uploaded to Salesforce's Content library. ContentDocumentLink associates each file to the parent record (Lead, Contact, Account, or Opportunity) with the correct ShareType and Visibility for the org's sharing model.

Saleshiker's Workflow engine stores trigger-action logic internally that is not portable to Salesforce or any other CRM. We do not migrate workflow definitions. We deliver a written inventory of every active Saleshiker Workflow and Scheduler with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce implementation partner rebuilds the automations post-migration.

WhatsApp broadcast records are governed by Meta's WhatsApp Business API and depend on Meta-approved templates, phone number associations, and conversation states that exist outside Saleshiker's data model. We do not migrate broadcast history or message logs. We preserve a written inventory of active broadcast campaigns with their template names, send dates, and recipient counts as custom fields on a sh_whatsapp_campaign__c placeholder record so the customer has a reference point for rebuilding campaigns in a WhatsApp-integrated Salesforce add-on or external tool.