Migrate from Pepper Cloud to Twenty CRM

Pepper Cloud Contact records map directly to Twenty Person records. Standard fields (name, email, phone, address, lifecycle stage) migrate as typed fields. Custom fields on Contacts require an explicit audit because Pepper Cloud's field type availability varies by pricing tier; Starter-tier workspaces may not have the same field types as Business or Enterprise, and any fields that do not have a type-equivalent in Twenty are flagged before migration. Email addresses serve as the dedupe key during import.

Pepper Cloud Leads are distinct from Contacts and tied to lead capture sources (web forms, WhatsApp, social channels). We migrate Leads to Twenty Person records with a leadType or tag field preserving the original source attribution. If the customer uses a Lead-to-Contact conversion workflow in Pepper Cloud, we map converted Leads to Twenty Person records in the customer lifecycle stage, and non-converted Leads to a separate prospecting lifecycle stage.

Pepper Cloud Account records map directly to Twenty Company records. Company-level fields (name, website, industry, address, employee count) migrate as typed fields. If Pepper Cloud has a parent-child account hierarchy, we preserve it using the Twenty Company field for parent company lookup. Custom fields on Accounts require the same tier-gated field type audit as Contacts.

Pepper Cloud Opportunity records map to Twenty Opportunity with stage, amount, close date, and owner preserved. Pipeline stage names in Pepper Cloud are workspace-specific and must be explicitly mapped to Twenty stage values rather than copied directly. The Opportunity-to-Company and Opportunity-to-Person lookups are resolved at migration time using the account name and primary contact email as matching keys.

Pepper Cloud pipeline configurations (stage names, stage order, stage probabilities) do not have a direct API export. We document the pipeline structure from the Pepper Cloud UI during scoping and configure the equivalent stage set in Twenty Settings before migration. Stage probability percentages are approximated to Twenty's nearest supported format. If the customer has multiple pipelines, we create multiple stage sets in Twenty and map Opportunities to the appropriate set based on the source pipeline assignment.

Pepper Cloud Tasks linked to Contacts, Leads, or Opportunities migrate to Twenty Task records. Due dates, assignees (resolved via owner email match), status, and priority migrate directly. Tasks that were marked complete in Pepper Cloud migrate with completed status and the original completion timestamp preserved as an activity date field. Recurring task configuration is documented as a settings handoff item because Twenty handles recurring tasks differently.

Pepper Cloud User records (name, email, role, active status) migrate to Twenty Workspace Users. We match by email as the primary key. Any Pepper Cloud Owner not found as an active Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission mapping is documented as a settings handoff item because Twenty's role model uses workspace-scoped permissions rather than Pepper Cloud's role hierarchy.

Pepper Cloud custom field schemas are audited per object before migration because field type availability differs by plan tier (Starter, Business, Enterprise). A field available as a dropdown in Enterprise may not be representable as a dropdown in Starter. We pre-create the equivalent Twenty custom fields with matching types in Settings before migration. Text, number, date, and checkbox fields map cleanly; dropdown fields require option value translation; multi-select fields map to Twenty multi-select fields where supported.

Document attachments associated with Pepper Cloud records are exported via file download and re-linked to the corresponding Twenty record by matching the parent record ID. Large file attachments may require chunked download and upload. We verify file integrity (MD5 checksum) during the export-to-import cycle. Attachments that are not accessible via the Pepper Cloud private API (such as files stored outside the standard attachment API) are flagged in the scoping report.

Tags applied to Pepper Cloud Contacts, Leads, and Opportunities migrate as flat label strings in Twenty's Tag system. If the customer has a large tag vocabulary (over 200 distinct tags), we deduplicate and normalize before import to avoid tag inflation in Twenty. Tags that represent segmentation categories rather than informal labels are documented for the customer's admin to restructure as a custom field or option set post-migration.