Migrate from Plezi to Pipedrive

Plezi Contacts map directly to Pipedrive People records. Standard fields (first_name, last_name, email, phone, job_title) transfer 1:1. Plezi's behavioral scoring profile and lifecycle stage properties are preserved as custom fields on the Pipedrive Person record (scoring_profile__c and lifecycle_stage__c) since Pipedrive does not have a native scoring engine. We resolve the organization lookup by matching Plezi's Company domain or name against Pipedrive Organization records, creating the link at import time.

Plezi Companies map to Pipedrive Organizations. Fields including company name, domain, industry, address, and any custom enrichment properties transfer 1:1. Pipedrive Organization is the parent record for Person lookups, so we create all Organizations before Person import to satisfy the relationship. Custom Plezi company properties map to custom Organization fields pre-created in the Pipedrive account before migration.

Plezi does not have a native Deal or Opportunity object, but engaged contacts with high lifecycle stages or conversion events can be represented as Pipedrive Deals. We work with the customer during scoping to define which Plezi contact behaviors (form submission, campaign conversion, high score threshold) map to Deal creation. Pipedrive pipeline stages and a default pipeline are configured before migration. Deals are created with linked Person and Organization records resolved at import time.

If the customer uses Plezi's campaign cost and pipeline tracking for revenue attribution, we configure Pipedrive Pipelines and Stages to match the business process. Pipedrive supports multiple pipelines from the Advanced tier ($24.90/user/month) onward; we configure one default pipeline for Essential tier migrations. Each stage receives a probability percentage and is labeled to match the Plezi campaign funnel stage the customer defines during scoping.

Plezi user accounts (name, email, role) map to Pipedrive User records. We match by email address. Plezi role names (admin, marketer, sales) require manual mapping to Pipedrive's permission model (admin, manager, regular user). Any Plezi user without a matching Pipedrive User is held in a reconciliation queue until the customer's Pipedrive admin provisions the account before record import resumes.

Plezi Tags applied to Contacts for segmentation map to Pipedrive Labels on Person records. Pipedrive Labels are a native feature for tagging people and organizations without requiring custom fields. We preserve all tag names and apply them during Person import. Labels that contain multiple words are preserved as-is since Pipedrive supports label strings without a character limit.

Plezi call engagement records map to Pipedrive Activity with type set to Call. We preserve call duration, disposition, and the associated Person link. Pipedrive Activity does not support a native recording URL field; recording links are stored in a custom text field on the Activity record. Activity date is set to the original Plezi engagement timestamp to preserve timeline ordering.

Plezi email engagement records map to Pipedrive Activity with type set to Email. The email subject and body transfer as Activity subject and notes. Plezi email open and click events are stored as separate engagement records; we consolidate these into a single Activity entry with open/click metadata in custom fields rather than creating multiple activity records per email.

Plezi meeting engagement records map to Pipedrive Activity entries. Meeting title, date, and location transfer. Attendee information is stored in Activity notes since Pipedrive Activity does not have a native attendee list. The associated Person and Organization are linked via the Activity's Person and Organization fields.

Plezi Notes attached to Contacts or Companies map to Pipedrive Note records linked to the corresponding Person or Organization. Note content (HTML from Plezi) is stored as plain text in Pipedrive Note content. We preserve the original Plezi timestamp as the Note creation date. Notes attached to multiple records in Plezi are duplicated as separate Note records in Pipedrive since Pipedrive Note does not support multi-record attachment natively.

Plezi task engagement records map to Pipedrive Activity with type set to Task. Task subject, due date, status, and assignee transfer. Assignee resolution uses the email match against Pipedrive User records. Pipedrive Activity supports a busy flag and public/private visibility that we set based on the Plezi task visibility setting when present.

Plezi Smart Campaigns store trigger-action logic in a proprietary format that cannot be exported as runnable automation code. We extract each Smart Campaign's trigger events, conditional rules, and action sequences from the Plezi export and document them in a written inventory. The document lists the campaign name, trigger type (form submission, page visit, score change, etc.), conditions, and a recommended Pipedrive Automation equivalent. The customer's admin rebuilds the automation in Pipedrive Automation or a connected tool (Zapier, Make) post-migration. This documentation step is included in the migration scope.

Plezi Landing Pages include page title, URL slug, and form associations that we export as a structured reference document. Some landing pages contain embedded third-party widgets (webinar registration iframes, live chat scripts, custom JavaScript) that cannot be extracted during export. We audit each landing page during the discovery phase, flag embedded components, and document the page structure so the customer's admin can recreate it in a landing page tool or Pipedrive Web Forms. Pages without third-party embeds may be reconstructable via the exported HTML if Plezi's export includes full page markup.