Migrate from Plezi to Zoho CRM

Plezi Contacts with lifecycle stage set to prospect or unqualified map to Zoho CRM Lead. Plezi Contacts with lifecycle stage set to qualified, customer, or evangelist map to Zoho CRM Contact attached to an Account. We compute the split using Plezi's scoring profile lifecycle_stage property at migration time and preserve the original stage name in custom fields lead_original_stage__c and contact_original_stage__c for audit and reporting. Any Plezi Contact without a lifecycle stage assignment defaults to Zoho CRM Lead.

Plezi Company records map to Zoho CRM Account. The company domain from Plezi's enrichment data populates the Account Website field. We use company name as the dedupe key during import. Account is created before any Contact import so that the Account Name lookup is satisfied at the moment of Contact insert. Plezi's industry and employee_count custom properties map to Zoho CRM's standard Industry and Account Site fields.

Plezi's behavioral scoring model stores individual contact scores across multiple dimensions (engagement score, fit score, intent score). We decompose each scoring dimension into Zoho CRM custom number fields (e.g., plezi_engagement_score__c, plezi_intent_score__c) and create a multi-select picklist plezi_scoring_tier__c with values derived from Plezi's tier thresholds. The original scoring model is preserved in the custom field schema for the customer's admin to calibrate against Zoho CRM's native scoring tools post-migration.

Plezi Campaign records (type, channel, start date, end date, budget) map to Zoho CRM Campaign. The campaign type maps to Zoho CRM Campaign Type (Advertisement, Email, Seminar, Trade Show, Webinar, Other). Budget amount from Plezi migrates to the Zoho CRM Budget custom field. We link migrated Contacts to the Campaign via Campaign Member records during import.

Plezi Landing Pages export as metadata records (title, slug, URL). We migrate the page title and URL as a Zoho CRM Note linked to the associated Campaign. Embedded third-party widgets (webinar iframes, live chat scripts, custom JavaScript) cannot be extracted during export; we document each affected landing page in the audit phase with a flag indicating manual recreation required. Full HTML page export is not within standard migration scope.

Plezi Forms with field names, required flags, and target pipeline stage assignments migrate as Zoho CRM Notes referencing the form schema. Where Plezi's forms feed directly into Smart Campaigns with stage-gating logic, we capture the stage assignment as a custom field plezi_form_target_stage__c on the Contact record. Customers needing full form recreation use Zoho CRM's native form builder or Zoho Forms separately.

Smart Campaign trigger events, conditional rules, and action sequences are exported as a structured JSON manifest. We do not copy Smart Campaign logic as runnable code because the format is proprietary and non-portable. Instead, we deliver a written Smart Campaign inventory document listing each campaign's trigger type (form submission, page visit, contact update, date-based), conditions, and action chain, with a recommended Zoho CRM Blueprint or Workflow Rules equivalent. The customer's admin rebuilds the automation in Zoho.

Plezi multi-step nurture sequences (Workflows) export as step sequences with content block references. Dynamic content personalization steps cannot be automatically reproduced. We deliver a Workflow inventory document listing each sequence's step order, content block names, and delay configuration, with a recommended Zoho CRM Workflow Rules equivalent. The customer rebuilds in Zoho or engages a Zoho implementation partner.

Emails and content blocks used inside Plezi Smart Campaigns and Workflows export as HTML and text variants. We migrate the HTML body and subject line as Zoho CRM Email Templates linked to the relevant Campaign. Inline images may require re-hosting at a new CDN URL; we flag each affected template during audit. Customers running email campaigns post-migration should verify image URLs and update tracking parameters.

Plezi User accounts (name, email, role) map to Zoho CRM User records. We match Plezi users by email against the destination Zoho CRM org's User table. Role names are preserved in a custom field plezi_original_role__c for manual mapping to Zoho CRM's role hierarchy. Any Plezi user without a matching Zoho CRM User is added to a reconciliation queue for the admin to provision before record import resumes.

Plezi Contact tags migrate to Zoho CRM multi-select picklist fields on the Contact or Lead module. The customer chooses at scoping whether to consolidate all tags into a single plezi_tags__c field or distribute them across topic-specific picklists. Tags used for segmentation mapping to Plezi Smart Campaign triggers are flagged in the Smart Campaign inventory document so the rebuild plan accounts for the tag dependency.