Migrate from Pepper Cloud to Freshsales

Pepper Cloud Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, address, lifecycle stage) migrate without transformation. Freshsales Contact inherits any custom fields that were configured on the Contact object in Pepper Cloud, provided the target Freshsales plan tier supports the corresponding field type. We run a field-type compatibility check during scoping to flag any custom fields that cannot be represented in the destination tier.

Pepper Cloud Lead records map to Freshsales Lead. Lead source attribution (web form, WhatsApp, Facebook, Instagram, Shopify, Telegram) migrates as the original_sourcetype__c custom field in Freshsales to preserve attribution for reporting. Freshsales uses Lead Status values (New, Contacted, Qualified, Unqualified) rather than Pepper Cloud's status taxonomy, so we map the source status to the closest Freshsales equivalent during transformation. After migration, the customer's admin configures the Lead conversion field mapping in Freshsales Admin Settings so that custom lead fields populate Contact, Account, and Deal fields during qualification.

Pepper Cloud Account records map directly to Freshsales Account. Company-level fields including website, industry, employee count, and annual revenue migrate as standard Account fields. Parent-child hierarchy (if configured in Pepper Cloud) migrates as the Freshsales Parent Account lookup, which the customer's admin verifies after migration because the parent reference requires an existing Account ID at insert time.

Pepper Cloud Opportunity records map to Freshsales Deal. The opportunity amount, close date, owner, and related Contact and Account links migrate directly. Pipeline stage names from Pepper Cloud are the most complex part of this mapping because each Pepper Cloud workspace can have custom stage names and counts. We map each Pepper Cloud stage to a Freshsales Deal stage during scoping, creating new stages in Freshsales if no matching stage exists. Stage probability percentages migrate from Pepper Cloud to Freshsales probability values.

Pepper Cloud pipeline configurations map to Freshsales Pipeline setup. Each pipeline in Pepper Cloud becomes a named Pipeline in Freshsales with its stage sequence preserved. Stage count and ordering carry over, but stage names require explicit mapping because Pepper Cloud workspaces commonly use non-standard stage names (for example, pipeline-specific stages like Demo Done or Proposal Sent). We document the stage map in the migration spec before any Deal records are imported.

Pepper Cloud Tasks linked to Contacts, Leads, Accounts, or Opportunities migrate to Freshsales Task records with due dates, assignees, status, and priority preserved. Task ownership resolves by matching the Pepper Cloud owner email to a Freshsales User email. Recurring tasks carry their frequency configuration as a note in the task description for manual recreation in Freshsales because recurrence patterns are not transferable via API.

Custom fields on Contacts, Leads, Accounts, Opportunities, and Tasks migrate only if the target Freshsales plan tier supports the equivalent field type. Pepper Cloud's Starter and Business tiers limit custom field availability differently from Freshsales Blossom and Garden. We audit the source custom field inventory (field name, field type, and target plan) before migration and flag any fields that will be truncated, converted to text, or omitted. The customer creates equivalent custom fields in Freshsales before we begin the data import phase.

Document attachments associated with Pepper Cloud records migrate as Freshsales Files with the file linked to the corresponding Contact, Account, Lead, or Deal record via ContentDocumentLink. Large files are downloaded in chunks and re-uploaded with integrity verification (MD5 hash comparison) to ensure no silent data corruption during transfer. Files are linked after the parent record exists in Freshsales, so attachments import after the primary object migration phase completes.

Pepper Cloud Users (name, email, role, active status) migrate to Freshsales Users. We resolve ownership by matching the Pepper Cloud owner email to a Freshsales User email during migration. Any Pepper Cloud user without a corresponding Freshsales User record goes to a reconciliation queue for the customer's admin to provision. Inactive Pepper Cloud users migrate as inactive Freshsales users to preserve historical ownership on closed records.