Migrate from Pipz to HighLevel

Pipz Contacts map 1:1 to GoHighLevel Contacts. Email address serves as the dedupe key during import. We preserve all standard contact fields (name, phone, address), custom field values, and tag associations. The Pipz contact record's linked Company association migrates as a GoHighLevel Contact-to-Company relationship that we resolve by matching the company name or domain at import time.

Pipz Company records map to GoHighLevel Company. Company name is the dedupe key. We preserve address, domain, and industry data. If a Pipz Company has no name (some Pipz records link contacts to anonymous organizations), we create a placeholder Company record and link all associated Contacts before proceeding to the Deal phase.

Pipz Deals map to GoHighLevel Opportunities. The Deal value, stage name, owner assignment, and associated contact links migrate. We flag Deal pipeline structure during scoping because Pipz organizes pipelines differently depending on which solution tier is active; GoHighLevel requires explicit pipeline and stage configuration before Deal import begins.

Pipz pipeline stages require explicit GoHighLevel pipeline configuration before Deal import. Each Pipz pipeline becomes a GoHighLevel Opportunity pipeline with stage names mapped directly. Stage order and probability percentages migrate where Pipz exposes them; custom stage colors and icons do not transfer and must be reconfigured in GoHighLevel's pipeline settings.

Pipz email campaign Activity records (opens, clicks, unsubscribes) migrate to GoHighLevel as Activity records on the associated Contact. Timestamps preserve the original engagement moment. GoHighLevel displays these as timeline entries on the Contact record. Note that GoHighLevel's native email reporting is campaign-scoped; individual open/click events appear in the contact timeline rather than a unified campaign analytics view.

Pipz native live chat and in-app messaging conversations migrate as Activity records with the chat content preserved as the activity body. We link each message thread to the associated Contact by email match. GoHighLevel does not have a native live chat widget; these activity records preserve the communication history but cannot be replayed as a live chat session.

Pipz automation-triggered events (workflow entry, tag applied, stage changed, goal reached) migrate as Activity records with the event type and trigger source preserved. We use the Pipz event type as the activity type selector in GoHighLevel. The automation logic that generated the event does not transfer; only the resulting contact state change is recorded.

Pipz Email Campaign metadata (name, subject, send date, status, recipient list size) migrates as a GoHighLevel Campaign record. Performance metrics (open rate, click rate, bounce rate) migrate as custom fields on the Campaign. The actual email content does not automatically transfer; we export HTML templates from Pipz and flag them for manual recreation in GoHighLevel's Email Template Builder or for use as reference content during Workflow rebuild.

Pipz tags applied across Contacts, Companies, and Deals migrate to GoHighLevel tags with the same tag name. We map tag associations per record type, preserving all cross-object tag usage. GoHighLevel supports tag filtering on contacts and companies in list views and Smart Lists.

Pipz custom fields on contacts, companies, and deals map 1:1 to GoHighLevel custom fields of equivalent type. Text fields map to text, number fields to number, date fields to date. Multi-select Pipz fields map to GoHighLevel multi-select. We extract the full custom field definition including type, options, and default value during scoping. Note that GoHighLevel distinguishes between Contact-level custom fields and Opportunity-level custom fields; Pipz does not make this distinction, so we clarify the intended scope with the customer during scoping.

Pipz Users assigned as owners to Contacts, Deals, and Automation flows map to GoHighLevel Users. Owner resolution uses email match. We extract all distinct owner references across Contact, Company, Deal, and Activity records and match against the GoHighLevel destination User table. Any Pipz owner without a matching GoHighLevel User is held in a reconciliation queue for the customer to provision before record import resumes.

The Pipz Customer Engagement Index is a proprietary behavioral score with no GoHighLevel native equivalent. We extract the raw CEI value and preserve it as a custom numeric field on the GoHighLevel Contact record. The underlying engagement event data (login activity, in-app actions, email engagement breakdown) does not have a structured mapping destination in GoHighLevel; we document the full event schema for the customer's admin to evaluate against GoHighLevel's available custom field structure.