Migrate from Pipz to Salesforce Sales Cloud

Pipz Contacts map to Salesforce Lead or Contact depending on the Contact's lifecycle stage. We evaluate Pipz lifecycle stage values during scoping to determine which records qualify as leads versus contacts. Unqualified Pipz Contacts (early lifecycle stages) map to Salesforce Lead. Contacts with an associated Company and active deal activity map to Salesforce Contact linked to an Account. The original Pipz lifecycle stage is preserved in a custom field pipz_lifecycle_stage__c on both Lead and Contact for historical audit and reporting continuity.

Pipz Company records map directly to Salesforce Account. Company domain, industry, employee count, and annual revenue migrate to standard Account fields. Company is the parent record for Contact, so Account import completes before Contact import to satisfy the AccountId Lookup. Pipz Company-to-Contact relationships are reconstructed as Salesforce Account-to-Contact lookups during the Contact import phase.

Pipz Deals map to Salesforce Opportunity. The deal value, close date, owner, and associated pipeline stage migrate directly. We resolve the AccountId on Opportunity by matching the Pipz Deal's linked Company to the migrated Account record. Pipz custom deal fields migrate to Salesforce custom Opportunity fields. Deal stages from Pipz map to Salesforce StageName values within the target Sales Process.

Each Pipz pipeline becomes a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Pipz to Salesforce StageProbability. If Pipz pipeline stages include custom properties beyond name and probability (such as automation triggers), we flag those during scoping for manual Salesforce Flow reconstruction since stage-level triggers are not data-migrated.

Pipz Activity records (email opens, link clicks, page views, chat conversations, automation-triggered events) map to Salesforce Task and Event records. We set Task.Subject and Task.TaskSubtype based on the Pipz activity type, preserve the original Pipz timestamp as ActivityDate, and link each record to the migrated Contact or Lead via WhoId. For high-volume activity migrations, we use the Salesforce Bulk API 2.0 with chunking and exponential backoff to avoid governor limit timeouts.

Pipz Email Campaigns map to Salesforce Campaign records, with campaign metadata (name, subject line, send date, status, open rate, click rate) preserved in custom Campaign fields. The Pipz campaign contact list migrates as CampaignMember records with Status set based on the contact's engagement state at send time (Sent, Opened, Clicked, Bounced). Email campaign performance metrics are stored as custom fields on Campaign rather than in standard Salesforce Campaign reporting.

Pipz Smart Segments built from demographic rules, tag filters, and behavioral event conditions do not have a direct Salesforce equivalent. We extract segment definitions as saved filter criteria and document them in a written inventory. Static segments (contacts hard-assigned to a list) migrate as Salesforce Campaigns with CampaignMember records. Dynamic behavioral segments require manual rebuild in Salesforce Reports, List Views, or Marketing Cloud Account Engagement (Pardot) segmentation tools post-migration.

Pipz tags applied across Contacts, Companies, Deals, and Campaigns migrate to Salesforce as either custom multi-select picklist fields on the relevant object or as Topic records with TopicAssignment links. The migration strategy is chosen during scoping based on tag cardinality: low-cardinality tags (under 30 distinct values) map to multi-select picklists; high-cardinality tag sets are mapped to a custom text field for flexibility.

Pipz custom fields on Contacts, Companies, and Deals migrate to Salesforce custom fields with equivalent data types. We extract the full custom field definition including type, picklist options, required flag, and default value during scoping, then pre-create the Salesforce custom field schema in a Sandbox before production migration. Pipz custom fields linked to Pipz-specific automation triggers are flagged separately for Salesforce Flow reconstruction.

The Customer Engagement Index (CEI) is a Pipz-proprietary behavioral score with no direct Salesforce equivalent. We preserve the CEI value as a custom numeric field (pipz_cei_score__c) on Contact or Lead at migration time. We also extract the raw engagement event log as a serialized JSON field (pipz_engagement_events__c) so that a Salesforce admin or data analyst can reconstruct scoring logic in Salesforce Flow, Pardot Scoring, or a CRM Analytics data model post-migration.

Pipz Users assigned as owners to Contacts, Deals, Companies, and automation flows map to Salesforce User records by email address match. We resolve Pipz owner references during migration by matching the owner's email to the destination Salesforce User. Any Pipz User without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before record import resumes, since OwnerId is required on most Opportunity and Contact records.

Pipz native live chat and in-app message conversations map to Salesforce Task records with a custom chat metadata field (chat_transcript__c) preserving the message content. If the customer intends to use Salesforce Service Cloud alongside Sales Cloud, chat conversations can alternatively map to Case records for support workflow integration. We confirm the preferred mapping during scoping based on the customer's Salesforce product licensing.