Migrate from SalezShark to Salesforce Sales Cloud

SalezShark treats Leads as a distinct object from Contacts with auto-assignment rules and conversion scoring on Basic and above. We map SalezShark Leads to Salesforce Lead and SalezShark Contacts to Salesforce Contact, with the split rule defined during scoping based on the customer's assignment model. Source record IDs are preserved in a custom field sz_source_id__c on both Lead and Contact for reconciliation. Any conversion history in SalezShark (Lead-to-Contact conversion events) is captured as a note on the resulting Salesforce Contact.

SalezShark Account Management maps directly to Salesforce Account. Company name is the dedupe key. Account is imported before any Contact import so that the AccountId lookup is satisfied at Contact insert time. Multi-currency data from SalezShark's Professional tier migrates to Salesforce's CurrencyIsoCode field on Account and Opportunity.

SalezShark Opportunity Management maps to Salesforce Opportunity. Pipeline stage, deal value, close date, owner assignment, and probability percentages transfer directly. We resolve AccountId and OwnerId via the Account and User lookups before Opportunity import. Closed-Won and Closed-Lost outcomes and their associated reasons map to Salesforce standard fields.

SalezShark's multiple Sales Pipelines map to Salesforce Record Types on Opportunity, each with its own Page Layout and Sales Process. Stage names and ordering are extracted from the current pipeline configuration during scoping and re-created in Salesforce. Probability percentages per stage transfer to StageProbability on the corresponding Sales Process stage entry.

Custom Fields available on SalezShark Basic and above are extracted as a schema inventory from the account settings during scoping. We map each to a typed Salesforce custom field (Text, Number, Picklist, Date, etc.), pre-create the fields in the destination org before any record import, and flag any fields with no Salesforce equivalent as candidate fields to create manually. Picklist values migrate as active values on the Salesforce field.

SalezShark Activity and Task Management maps to Salesforce Task. Status, Priority, DueDate, Owner, and association to Contact, Account, or Opportunity transfer directly. We resolve the WhoId (Contact or Lead) and WhatId (Account, Opportunity, or other) references via lookup tables built during the Account and Contact import phases. Activity timestamps are preserved to maintain timeline ordering.

SalezShark Document Management files are exported as metadata (file name, type, size, upload date, associated record ID) and re-associated to the corresponding Salesforce Contact, Account, or Opportunity via ContentDocumentLink records. The actual file content is re-uploaded as Salesforce Files using ContentVersion. File association to the parent record is resolved using the source system's record link captured during extraction.

SalezShark Campaigns and Mass Email configurations are available on Basic and above. We map campaign membership records (Contacts and Leads enrolled) to Salesforce Campaign and CampaignMember. Email content and templates do not migrate; we deliver a written list of campaign assets requiring rebuild as Salesforce email templates or Marketing Cloud content. Campaign type and status fields map directly.

SalezShark User records map to the OwnerId and AssignedTo fields on migrated records. User licenses themselves are not migratable — we flag the owner reassignment step to avoid orphaned records. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import continues.

SalezShark Reports (standard and custom) and dashboards are exportable as configuration metadata describing filters, field selections, and layout. We preserve the configuration but cannot migrate the underlying query results or historical data generated by those reports — these are regenerated automatically in Salesforce when the reports are rebuilt. We deliver a report mapping document specifying the equivalent Salesforce report type and fields for each source report.

Workflow Automations are gated to SalezShark Professional tier. We export the automation configuration as a written specification: trigger object, trigger conditions, filter logic, and downstream action sequences. This specification is delivered alongside the migrated records so the customer's admin can rebuild each automation in Salesforce Flow. We do not execute or translate workflow logic directly; the rebuild is performed by the customer's admin or a Salesforce partner post-migration.

Custom Event Triggers are only available on SalezShark Professional tier. We export each trigger's criteria and downstream action sequence as a written specification describing the event object, condition tree, and action list. The destination team uses this specification to design equivalent Salesforce Flow triggers or Apex triggers. No event trigger logic migrates as executable code.