Migrate your Pipz data

Contacts are Pipz's primary billing unit and the core of its data model. All features pivot on contact records. We map Contacts 1:1 to the destination schema, preserving email, name, phone, custom properties, and lifecycle stage. No data loss expected on standard field transfer.

Companies in Pipz associate multiple contacts under a single organizational record. We map company records alongside their linked contacts, preserving the relationship graph in the destination CRM where supported.

Deals in Pipz represent sales opportunities tied to pipeline stages. We map Deal records and their associated stage, owner, and value fields, but we flag the pipeline structure for review since Pipz pipelines vary by solution tier and may need stage re-mapping at the destination.

Pipelines and their stages are configurable per solution tier in Pipz. We transfer stage names and ordering, but custom stage properties and automation triggers attached to stages require field-level mapping review before migration.

Activities in Pipz capture email opens, link clicks, chat conversations, page views, and automation-triggered events. We map all activity records with timestamps, contact associations, and event types. This preserves the full lifecycle timeline in the destination.

Email campaigns in Pipz include metadata (name, subject, send date, status) and performance metrics. We map campaign records and their linked contact lists to the destination, preserving segmentation logic where field mapping allows.

Segments in Pipz are built from demographic, tag-based, and behavioral rules. We transfer segment definitions as saved filter criteria and flag the underlying logic for manual recreation if the destination does not support equivalent rule-based segmentation.

Tags in Pipz are applied across contacts, companies, deals, and campaigns as a flexible labeling mechanism. We map all tags and their associations to preserve categorization and filtering logic at the destination.

Custom fields on contacts, companies, and deals are fully supported but require field-level mapping to the destination schema. We extract the full custom field definition including type, options, and default values, then map them to matching or custom fields at the destination.

Users in Pipz are assigned as owners to contacts, deals, and automation flows. We map user records and their assignments, preserving owner relationships in the destination. Note that Pipz includes unlimited team members on paid plans, so user record counts may be high.