Migrate from Plezi to HighLevel

Plezi Contacts map to GoHighLevel Contacts with standard properties (first name, last name, email, phone) migrated directly. The Plezi behavioral scoring profile (lead score, lifecycle stage) migrates to custom numeric fields on the Contact record that we provision in GoHighLevel's Settings > Custom Fields before migration. Tags associated with each Contact migrate to the GoHighLevel Tags field.

Plezi Company records carry enrichment data including company name, domain, industry, and size. We map these to the company information section of the related GoHighLevel Contact record. Where the destination GoHighLevel account uses the separate Company object for multi-contact accounts, we map accordingly and resolve the Contact-to-Company lookup at migration time.

Plezi Campaigns represent marketing initiatives with cost, channel, and date metadata. We map campaign cost and budget fields to GoHighLevel Opportunity fields (amount, stage), and preserve the campaign start and end dates as custom date fields. The campaign type and channel map to Opportunity tags or custom picklist fields. If the Plezi Campaign is a closed-won deal reference, we treat it as a historical Opportunity.

Plezi Forms capture leads and feed them into Smart Campaigns. We migrate form field names, required flags, and target stage assignments. Custom field types (text, email, phone, dropdown) map to the closest GoHighLevel Form field equivalent. Form submission counts migrate as tags on the Contact record for reporting context.

Plezi Landing Pages are standalone assets with their own URLs and form associations. We export page title, slug, and form references during the audit phase. Any pages containing embedded third-party widgets (webinar iframes, live chat scripts, custom JavaScript) are flagged as non-exportable and documented for manual recreation in GoHighLevel's funnel builder. Pages without embedded content may be migrated as snapshots at customer request.

Plezi Smart Campaigns store trigger-action logic in a proprietary format that cannot be exported as runnable automation. We reconstruct each Smart Campaign's intent by exporting the trigger events, conditional rules, and action sequence separately. We deliver a written inventory of every Smart Campaign with its reconstructed trigger, conditions, and actions plus a GoHighLevel Workflow equivalent recommendation. The customer's admin rebuilds Workflows using the documented intent.

Plezi Workflows manage multi-step nurture sequences with step references to Contacts and Companies. We export the step sequence and associated content blocks. Dynamic personalization content that cannot be extracted is documented as a rebuild requirement. The step logic maps to GoHighLevel Workflow nodes, but the content itself requires admin verification.

Plezi emails and content blocks used inside Smart Campaigns and Workflows are exportable as HTML and text variants. We migrate the HTML body and subject line to GoHighLevel Email Templates. Inline images may require re-hosting at the destination; we flag any image URLs that point to Plezi-hosted assets as requiring manual replacement or re-upload to GoHighLevel's media library.

Plezi User accounts include name, email, and role. We export user records and map roles to GoHighLevel's permission model, where roles include Admin, Manager, Agent, and Scheduler. Plezi-specific role names require manual review during scoping to determine the correct GoHighLevel permission level for each user.

Plezi Tags on Contacts migrate to GoHighLevel Tags, which appear on the Contact record as a tag list. Tag names are preserved verbatim. In GoHighLevel, tags are used for segmentation, filtering, and Workflow triggers. The customer chooses whether to migrate all tags or a scoped subset during scoping.