Migrate from Pepper Cloud to Odoo CRM

Pepper Cloud Contact records map directly to Odoo CRM Contact. Standard fields (name, email, phone, street, city, state, country) migrate with direct field-to-field mapping. Custom fields on Contact require type compatibility audit: Pepper Cloud dropdown, date, and checkbox fields map to Odoo Selection, Date, and Boolean fields respectively; text fields map to Odoo Char or Text depending on length. Mobile and phone fields consolidate into Odoo's phone field with type preserved via a custom field if distinction matters.

Pepper Cloud Lead records map to Odoo CRM Lead (crm.lead). Lead source attribution (web form, WhatsApp, Facebook, Instagram, Telegram, Shopify) migrates to the Odoo Lead medium_id field. The Pepper Cloud lead status (new, contacted, qualified, lost) maps to the Odoo stage_id with explicit stage name mapping configured during scoping. Lead score from Pepper Cloud's AI-assisted scoring migrates to a custom integer field on the Odoo Lead for post-migration segmentation.

Pepper Cloud Account records map to Odoo Contact records with the is_company flag set to True, creating an Odoo Company record. The Account name becomes the Odoo Contact's company_name field. Pepper Cloud's parent-child Account hierarchy (if configured) maps to Odoo's child contacts linked under the parent Company contact. We pre-create the Company contact record before any child Contact import so the parent contact_id relationship is satisfied.

Pepper Cloud Opportunity records map to Odoo CRM Opportunity (crm.lead with type = opportunity). Pipeline stage names from Pepper Cloud migrate explicitly to Odoo stage names; stage probabilities migrate to the Odoo stage probability field. Deal amount, expected close date, and owner (sales rep) migrate directly. The Opportunity to Contact and Opportunity to Company links resolve via the Contact and Company mapping done in steps 1-3.

Pepper Cloud workspace-level pipelines with custom stage names and counts map to Odoo CRM Pipeline stages. We configure Odoo stages with names, sequence order, and probability percentages matching the Pepper Cloud pipeline before any Opportunity records are inserted. If multiple Pepper Cloud pipelines exist, we use Odoo's crm.team model to separate pipeline ownership per team while maintaining a single CRM stage set.

Pepper Cloud Tasks linked to Contacts, Leads, or Opportunities map to Odoo CRM Activities (mail.activity). Task title, body, due date, assignee, and status (open, completed) migrate to Odoo activity_type_id, summary, date_deadline, user_id, and state. Recurring task frequency from Pepper Cloud is documented for manual rebuild in Odoo because recurring activities require a different configuration model in Odoo CRM.

Pepper Cloud Owner records (sales reps) map to Odoo User records by email match. Active status and role (admin, sales rep) migrate as Odoo User active flag and access rights. Any Pepper Cloud Owner without a matching Odoo User goes to a reconciliation queue; the customer's Odoo admin provisions missing users before record import resumes because OwnerId references are required on Opportunities and Leads.

Pepper Cloud custom fields across Contacts, Leads, Accounts, and Opportunities require pre-creation in Odoo before data import. We audit the source workspace custom field inventory during scoping, verify type compatibility against Odoo's field model (Char, Text, Integer, Float, Boolean, Date, Datetime, Selection, Many2one, One2many), and create Odoo custom fields via XML data migration or Odoo Studio before ingestion. Tier-gating differences between Pepper Cloud plans are flagged if custom field types used in Enterprise cannot be represented in the customer's Odoo edition.

Document attachments associated with Pepper Cloud records migrate as Odoo ir.attachment records linked via res_model and res_id to the corresponding Odoo Contact, Lead, or Opportunity. Large files (>10MB) are chunked for download and upload. We verify file integrity via checksum comparison. File naming conventions from Pepper Cloud are preserved in the Odoo attachment display name for traceability.

Pepper Cloud tags on Contacts, Leads, and Opportunities migrate as flat crm.tag records with TagAssignment linking to the Odoo Lead or Opportunity. Odoo's tag system is per-pipeline by default; if the customer uses tags across multiple business lines, we configure tags at the crm.lead model level during schema setup. Tag names are preserved verbatim; no hierarchical restructuring is applied unless specified during scoping.

Pepper Cloud WhatsApp message content cannot be exported via the private app API. Only conversation metadata (contact reference, timestamp, channel label) is accessible. We flag this limitation during scoping and preserve what we can: the channel attribution on the Contact or Lead record, and any timestamps associated with WhatsApp-sourced lead capture events. We advise customers to export WhatsApp chat history separately via WhatsApp's own chat export feature before migration if message content is business-critical. We do not attempt a full message log transfer.

Pepper Cloud workflow automation rules (automated follow-ups, lead assignment logic, stage-change triggers) are not accessible via the private app API in a portable format. We document each automation rule observed in the source workspace during the discovery walk-through and deliver a configuration guide with the Odoo equivalent action (Odoo Server Actions, Automated Actions via Studio, or Python code) for the customer's admin to rebuild post-migration. This is a manual rebuild step outside standard migration scope.