Migrate from Plezi to Freshsales

Plezi Contacts map to Freshsales Lead for records at the top of the funnel (subscriber, early lead stages) and to Freshsales Contact for qualified buyers tied to an Account. We use the Plezi lifecycle stage property to determine the split and preserve the original lifecycle stage in a custom field plezi_lifecycle_stage__c on both Lead and Contact. Scoring profile values migrate as a custom numeric field plezi_score__c for segmentation and reporting in Freshsales.

Plezi Company records map directly to Freshsales Account. The company domain from Plezi becomes the Account Website field. We use the Plezi company unique identifier as the dedupe key during import. Freshsales Account is created before any Contact import so that the Account Lookup relationship is satisfied at Contact insert time.

Plezi Campaigns with metadata (name, type, start/end dates, budget) map to Freshsales Campaign. Campaign type maps to Freshsales Type picklist. We preserve the campaign cost and channel fields as custom Campaign fields if the destination Freshsales plan supports custom fields on Campaign. Active campaign membership associations (Contact-to-Campaign links) migrate as CampaignMember records.

Plezi Forms with field names, required flags, and target pipeline stage assignments map to Freshsales Webforms. We export the form field schema and the associated target stage mapping. Freshsales Webforms require manual recreation of the form builder layout; we provide the field-level configuration documentation so the admin can rebuild without reverse-engineering the original form.

Plezi Landing Pages export with page title, slug, and form reference. Freshsales landing page builder is available on Freshsales Suite plans only, not on the CRM-only Growth or Pro tiers. We audit the destination plan during scoping. Pages with embedded third-party widgets (webinar iframes, live chat scripts) are documented separately with a manual recreation checklist for the customer's admin.

Smart Campaigns are not migrated as runnable automation. We reconstruct each Smart Campaign's intent from the Plezi export, documenting the trigger events, conditional rules, and action sequences in a written workflow inventory. The customer uses this inventory to rebuild in Freshsales Workflows (Pro and above) or Freshsales Suite automation builder. Dynamic personalization steps that cannot be automatically reproduced are flagged explicitly.

Plezi Workflows managing multi-step nurture sequences are documented as step sequences with associated content block references. The step logic (delays, conditions, content assignments) migrates as a written workflow map, not as executable code. Freshsales workflows use a different trigger-action model; the inventory document maps each Plezi workflow to a recommended Freshsales equivalent.

Plezi emails and content blocks used inside Smart Campaigns and Workflows export as HTML and text variants. We export the HTML body and subject line. Inline images may require re-hosting. Freshsales Email Templates are rebuilt manually using the exported HTML as source material; we provide the HTML package with image host references flagged for re-upload to Freshsales Media Library.

Plezi User accounts (name, email, role) map to Freshsales User records. We resolve by email match. Plezi-specific role names (admin, marketer, sales) require manual review against Freshsales role permissions. Users without a matching Freshsales User are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Plezi Tags on Contacts migrate as Freshsales Labels on Contact records. We preserve all tag names and associations. In Freshsales CRM-only plans without label support, tags map to a multi-select picklist custom field plezi_tags__c. The customer chooses the target strategy during scoping.