Migrate from Pepper Cloud to HubSpot

Pepper Cloud Leads map directly to HubSpot Contacts. In HubSpot, lifecycle_stage defaults to 'subscriber' for new contacts; we set the initial value based on the lead status recorded in Pepper Cloud before migration. Owner assignment resolves via email match against HubSpot users.

Pepper Cloud Accounts are mapped to HubSpot Companies. We transfer the standard company fields—name, domain, industry, phone number, address, city, country, employee count, and annual revenue—directly where they exist. HubSpot's company record can associate multiple contacts; we preserve the primary contact linkage from Pepper Cloud, and any missing required fields are flagged for manual completion before the migration finalizes.

Pepper Cloud Contacts map to HubSpot Contacts when the source record is typed as a Contact rather than a Lead. All standard contact fields (name, email, phone, job title) transfer directly. HubSpot's association model links contacts to companies via the companyId property.

Pepper Cloud Opportunities become HubSpot Deals. The deal name, amount, close date, and owner map directly. Stage names require value mapping against HubSpot's pipeline stage pick-list. Multiple Opportunities from Pepper Cloud land in a single HubSpot pipeline unless you specify parallel pipeline splitting.

Pepper Cloud Tasks are migrated as HubSpot Tasks, preserving subject, due date, status, priority, and owner assignment. The task type field (call, email, meeting, or follow‑up) is mapped to HubSpot's task type taxonomy. Completed task notes and any descriptive text are transferred into the HubSpot task body so the full context is retained on the record.

Pepper Cloud custom fields on Leads that have no direct HubSpot equivalent become HubSpot custom properties on the Contact object. We create the custom property in HubSpot (with the appropriate type: text, number, date, select) before migration, then populate it during the data transfer. The original field label is preserved as the property name.

Pepper Cloud custom fields on Accounts that lack a native HubSpot Company field are migrated as HubSpot Company custom properties. Multi-select pick-list values from Pepper Cloud require HubSpot's multi-select property type. We validate type compatibility before creating the property in HubSpot.

Pepper Cloud Opportunity custom fields migrate as HubSpot Deal custom properties. Currency fields map to HubSpot's number property type; we preserve the numeric value. Date fields use HubSpot's date property type. Any custom field exceeding HubSpot's property name character limit is truncated and flagged for admin review.

WhatsApp conversation threads from Pepper Cloud do not have a native HubSpot equivalent. HubSpot's engagement model supports calls, emails, meetings, and notes. We attach WhatsApp conversation transcripts as a note on the associated contact record, preserving the full thread text and timestamp.

Pepper Cloud's single-pipeline model maps to a single HubSpot deal pipeline. If your Pepper Cloud account uses multiple stage configurations, we create corresponding HubSpot pipelines with distinct stage sets. Pipeline-level probability weights map to HubSpot's forecast category settings per stage.

Pepper Cloud lead status values (New, In Progress, Qualified, Converted) map to HubSpot lifecycle_stage values. The mapping is value-by-value: we document the exact translation in the migration plan. 'Converted' maps to 'customer', 'Qualified' maps to 'SQL' or 'MQL' depending on your Pepper Cloud definition.

Pepper Cloud call logs, email activities, and meeting records migrate as HubSpot engagements. Call recordings are not transferred (not stored in Pepper Cloud's standard export). Email subject, body, and timestamp map directly. Meeting details include title, start time, and duration.

File attachments on Pepper Cloud records (contacts, accounts, opportunities) are downloaded and re-uploaded to HubSpot's file storage. Files attach to the corresponding HubSpot record via the file associations API. File size limits apply per HubSpot's upload constraints (25MB per file by default).