Migrate from Pipz to Freshsales

Pipz Contacts map directly to Freshsales Contacts. The critical difference is that Freshsales requires every Contact to have an Account (Company) lookup. We resolve this by importing Pipz Companies first as Freshsales Accounts, then mapping Pipz Contacts with their Company association to the corresponding Freshsales Account lookup. Pipz lifecycle stage values preserve in a custom field pipz_lifecycle_stage__c for audit and future segmentation.

Pipz Company records map to Freshsales Accounts. The Account name, domain, address fields, and custom fields migrate. The Pipz Company-Contact relationship graph preserves in Freshsales through the Account-Contact lookup. We deduplicate by company domain name during import to avoid creating duplicate Accounts when multiple Pipz Contacts share the same organization.

Pipz Deals map to Freshsales Deals. Deal value, owner, stage, and associated Contact and Company links transfer. We map Pipz pipeline stages to Freshsales pipeline stages, creating the stage values in Freshsales before migration begins. Closed-Lost and Closed-Won status from Pipz map to Freshsales stage values with the same names if they exist, or to the closest equivalent.

Pipz pipeline stages transfer as Freshsales deal stage values. We create the stage values in Freshsales first during the schema design phase, preserving the original stage names and ordering. Probability percentages for each stage migrate if Pipz stores them, otherwise we set defaults and flag for the customer to adjust.

Pipz Activities (email opens, link clicks, chat conversations, page views, automation-triggered events) map to Freshsales Tasks. The event type, timestamp, associated Contact, and metadata fields transfer. Freshsales does not have a native equivalent for every Pipz event type, so we map to a Task with the event type preserved in a custom field pipz_event_type__c. High-volume event types (page views, email opens) may be aggregated into summary records to stay within Freshsales storage and API limits.

Pipz Email Campaigns with metadata (name, subject, send date, status) map to Freshsales Campaigns. Campaign member associations (which contacts received which campaign) migrate as CampaignMember records linking the imported Pipz Contacts to their Freshsales Campaign counterparts.

Pipz Smart Segments built from demographic, tag-based, and behavioral rules do not transfer as active filters. We document each segment's definition (criteria, operators, values) as a written specification for the customer to recreate as Freshsales Saved Views or List Views. Tags associated with segment membership are transferred and can be used to rebuild segment logic post-migration.

Pipz Tags migrate to Freshsales Tags. Tags applied across Contacts, Companies, and Deals transfer with their associations intact. Freshsales Tags are a platform-level feature that can be applied to any record type, matching Pipz's cross-object tagging model. We map all tag names and preserve the record-level tag assignments.

Pipz custom fields on Contacts, Companies, and Deals require field-level mapping to Freshsales custom fields. We extract the full custom field definition (name, type, options) from Pipz during discovery and pre-create the corresponding Freshsales custom fields before migration. For auto-mapping during Freshsales native imports, custom field names must match exactly; we handle name normalization during the transform phase.

Pipz Users assigned as owners to Contacts, Deals, and automation flows map to Freshsales Users. We resolve owners by email match. Any Pipz User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import completes.