Migrate from Pepper Cloud to Microsoft Dynamics 365 Sales

Pepper Cloud Contacts migrate to Microsoft Dynamics 365 Sales Contact. The Contact's email address serves as the dedupe key. Standard fields (name, email, phone, address, lifecycle stage) map to typed Dynamics 365 fields. Any custom fields on Pepper Cloud Contacts are audited for type compatibility; dropdown fields in Pepper Cloud map to Option Sets in Dynamics 365, checkbox fields to Two Option sets, and date fields to Date fields. We preserve the Pepper Cloud lifecycle stage value in a custom field pc_original_lifecycle__c on the Contact for reporting continuity.

Pepper Cloud Leads (distinct from Contacts, tied to web forms, WhatsApp, and social capture channels) migrate to Dynamics 365 Lead. Lead source attribution (web, WhatsApp, Facebook, Instagram, Telegram, Shopify) migrates to Dynamics 365 LeadSource. We preserve the original lead score from Pepper Cloud's AI-assisted scoring in a custom field pc_lead_score__c. If the customer uses Pepper Cloud's lead status taxonomy, we map it to a custom Option Set and recommend rebuilding lead scoring in Microsoft Dynamics 365 Sales Copilot or a Power Automate flow post-migration.

Pepper Cloud Account records (representing business organizations) map directly to Dynamics 365 Account. Company domain from Pepper Cloud maps to the Account Website field and is used as a dedupe indicator during import. Parent-child hierarchy for Account structures migrates via the ParentAccountId lookup. Custom fields on Accounts follow the same type-mapping audit as Contacts.

Pepper Cloud Opportunities migrate to Dynamics 365 Opportunity with AccountId (via Account mapping), OwnerId (via User mapping), EstimatedCloseDate, and Amount fields preserved. Pipeline stage names from Pepper Cloud's configurable stages must be explicitly mapped to Microsoft Dynamics 365 Sales Process stage values (Prospecting, Qualification, Proposal/Price Quote, Negotiation, Closed Won, Closed Lost). We configure a custom Sales Process in Dynamics 365 if the Pepper Cloud stage taxonomy does not map cleanly to the system default.

Pepper Cloud workspace pipelines (configurable per account) require explicit mapping to a Microsoft Dynamics 365 Sales Process. We create a custom Sales Process with Stage names, probabilities, and status values that mirror the Pepper Cloud pipeline. Stage probability percentages from Pepper Cloud migrate to StageProbability on the corresponding Dynamics 365 Stage. If the customer has multiple Pepper Cloud pipelines for different lines of business, we create multiple Sales Processes or Record Types in Dynamics 365.

Pepper Cloud Tasks linked to Contacts, Leads, or Opportunities migrate to Dynamics 365 Task. Due dates, assignees (via User mapping), status, and priority transfer directly. Recurring task frequency configuration from Pepper Cloud is preserved in custom fields (pc_recurrence_type__c, pc_recurrence_interval__c) with the note that recurring task logic requires manual rebuild in Dynamics 365.

Pepper Cloud custom fields across Contacts, Leads, Accounts, and Opportunities require type-compatible mapping to Dynamics 365 field types. Text fields map to Single Line of Text or Multiple Lines of Text by length. Dropdown fields map to Option Sets with the same label-value pairs. Date fields map to Date Only or Date Time depending on Pepper Cloud field precision. We audit the destination Dynamics 365 edition tier before migration because custom field count limits and field type availability differ between Professional and Enterprise.

Pepper Cloud tags applied to Contacts, Leads, and Opportunities migrate as flat string values. If the customer uses tags primarily for segment classification, we recommend migrating them to a multi-select Option Set field in Dynamics 365. If tags represent a taxonomy suitable for content association, we recommend migrating to Dynamics 365 Topics with TopicAssignment records. The customer chooses the strategy during scoping.

Pepper Cloud Users (owner references on Contacts, Leads, Accounts, and Opportunities) migrate by matching the owner's email address to a Dynamics 365 User. Any owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status from Pepper Cloud maps to the IsActive flag in Dynamics 365.