Migrate from Pepper Cloud to Salesforce Sales Cloud

Pepper Cloud Contact records with no associated Opportunity or unqualified lifecycle status map to Salesforce Lead. Contacts with active Opportunities or explicit qualification status map to Salesforce Contact tied to a parent Account. We determine the split using Pepper Cloud's lead_capture_status and contact_stage properties if present, preserving the original stage attribution in a custom field pc_original_stage__c on both Lead and Contact. The Account lookup is resolved before Contact import so that no Contact is orphaned.

Pepper Cloud Lead records (distinct from Contacts with lead capture source) migrate directly to Salesforce Lead. Lead source attribution from channels (WhatsApp, Facebook, Instagram, web form, Shopify) preserves as the Salesforce LeadSource field. Any lead score or qualification data in Pepper Cloud custom fields migrates to a custom field pc_lead_score__c on the Salesforce Lead record.

Pepper Cloud Account records (internally labeled Company) map directly to Salesforce Account. Company domain from Pepper Cloud becomes the Account Website field and is used as the dedupe key during import. Parent-child hierarchy on Accounts migrates via the ParentId field with circular reference validation before insert. Account is created before any Contact import so that AccountId is available as a required or optional field on Contact.

Pepper Cloud Opportunity records map to Salesforce Opportunity with Amount, CloseDate, Description, and OwnerId preserved. Stage mapping is the most critical step: Pepper Cloud stage names are workspace-specific, so we build an explicit mapping table from Pepper Cloud stage values to Salesforce StageName values in the destination Sales Process before migration. Probability percentages transfer to StageProbability. Closed-Lost and Closed-Won statuses are handled with LossReason and custom fields for win context.

Each Pepper Cloud pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the mapped stage values. We configure Record Types, Sales Processes, and Page Layouts in the destination org's Sandbox before migration so that stage constraints are active from the first Opportunity insert. If the customer has a single pipeline in Pepper Cloud, we default to the Opportunity standard Record Type without additional configuration.

Pepper Cloud Tasks linked to Contacts, Leads, or Opportunities migrate to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Recurring task frequency configuration migrates to Salesforce recurring task fields if the destination org has the recurring task feature enabled. Owner assignment resolves via email match to Salesforce User records. Tasks without a resolvable Owner are assigned to the migration service account pending admin reassignment.

Pepper Cloud User records (name, email, role, active status) migrate as Salesforce User records with Active flag set to false initially. We match by email against the destination org's User table. Owners without a matching Salesforce User are held in a reconciliation queue, and the customer's admin provisions missing Users before record import resumes. Active status is set to true only for users confirmed as current team members.

Custom fields on Accounts, Contacts, Leads, Opportunities, and Tasks require pre-migration type mapping because Pepper Cloud custom field availability and type options differ by plan tier. We audit the source workspace's custom field inventory during scoping and pre-create destination fields in the Salesforce org with compatible types: text fields map to Text(255) or Long Text Area, dropdowns map to Picklist with values preserved, date fields map to Date, checkboxes map to Checkbox, and number fields map to Number with appropriate precision. Custom field schemas from Pepper Cloud Business or Enterprise tiers that cannot be represented in the selected Salesforce edition are flagged during scoping with a recommendation to upgrade the Salesforce tier.

Document attachments associated with records migrate via file export from Pepper Cloud and re-upload to Salesforce as ContentVersion records linked to the parent record via ContentDocumentLink. Large file attachments (over 25 MB per Salesforce's single-file limit) require chunked download and upload with SHA-256 integrity verification. We validate file counts and total volume during scoping to confirm the migration environment has sufficient storage and bandwidth.

Tags applied to Contacts, Leads, and Opportunities in Pepper Cloud migrate as flat label strings. We present two options during scoping: flat string migration to a Salesforce Text field, or hierarchical migration to Salesforce Topics with TopicAssignment records linked to the relevant object. The customer selects the tagging strategy based on how they use tags for segmentation and reporting in the destination org.

WhatsApp message content cannot be exported via the Pepper Cloud API; only conversation metadata (contact reference, timestamp, channel attribution) is accessible. We migrate what we can: a Task record with Subject indicating WhatsApp channel, ActivityDate set to the conversation timestamp, and WhoId pointing to the related Contact or Lead. We flag this limitation explicitly during scoping and advise customers to export WhatsApp chat history separately through the WhatsApp Business app before migration if message content is business-critical.

Pepper Cloud workflow automation rules (follow-up triggers, lead assignment logic, stage-change conditions, reminder setups) are configured within the platform and are not accessible via API in portable format. We do not migrate them as code. We document each automation rule observed in the source workspace with its trigger, conditions, and actions, and provide a written guide for rebuilding equivalent logic in Salesforce Flow. This document is delivered as part of the migration handoff package and is a manual step the customer's admin must budget for post-migration.