Migrate from Plezi to Salesforce Sales Cloud

Plezi Contacts with a lifecycle stage of prospect or unqualified map to Salesforce Lead. Contacts with a lifecycle stage of qualified, customer, or evangelist map to Salesforce Contact tied to a pre-created Account. We compute the split using Plezi's lifecycle stage and scoring profile properties, and preserve the original Plezi lifecycle stage and behavioral score in custom fields plezi_lifecycle_stage__c and plezi_behavioral_score__c on both Lead and Contact for audit and reporting continuity.

Plezi Company records map directly to Salesforce Account. The company domain becomes the Account Website field and serves as the dedupe key during import. We create Account records before any Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. Industry, employee count, and any custom company properties map to corresponding Salesforce Account fields or custom fields.

Plezi Campaigns representing individual marketing initiatives with associated costs, channels, start and end dates, and budget fields map to Salesforce Campaign. Campaign type, status, and budget migrate as standard Salesforce Campaign fields. We preserve the campaign hierarchy if Plezi uses parent-child campaign structures, mapping to Salesforce Campaign hierarchical self-lookup.

Plezi Landing Pages are standalone assets with their own URLs, page titles, and form associations. We export the page title, slug, URL, and form reference. Any embedded third-party widgets (webinar iframes, live chat scripts, custom JavaScript) cannot be extracted during export. We document each landing page's embedded components during the audit phase and flag which pages require manual recreation versus automated migration. The customer's marketing team rebuilds landing pages in Experience Cloud or their preferred CMS post-migration.

Plezi Forms capture leads and feed them into Smart Campaigns with pipeline stage assignments. We migrate form field names, required flags, and the target stage assignment. Custom field types map to the closest Salesforce equivalent (text, picklist, checkbox, date). We create a corresponding Web-to-Lead form in Salesforce as the replacement capture mechanism and map form submission data to the appropriate Salesforce Campaign or Lead object.

Smart Campaigns are Plezi's core automation engine combining triggers, conditions, and actions stored in a proprietary format. We cannot export runnable automation packages. Instead, we reconstruct each Smart Campaign's intent by exporting the campaign trigger events, conditional rules, and action sequence separately. We deliver a written inventory of every Smart Campaign with its trigger type, conditions, actions, and recommended Salesforce Flow equivalent. Dynamic personalization steps and complex branching logic are flagged as requiring manual rebuild by the customer's admin.

Plezi Workflows manage multi-step nurture sequences with step sequences and content block references. We export the step sequence and content block associations but note that dynamic content within workflow steps cannot be automatically reproduced. The workflow step inventory is delivered as a written document for the customer's Salesforce admin to rebuild in Process Builder or Flow. Content blocks used inside workflows are exported as HTML and text variants where available.

Emails and content blocks used inside Plezi Smart Campaigns and Workflows are exportable as HTML and text variants with subject lines. We extract the HTML body and carry it forward as a Salesforce Email Template or ContentDocument record. Inline images may require re-hosting at the destination because image URLs pointing to Plezi's asset CDN will not resolve in Salesforce. We document each image reference for manual re-attachment.

Plezi User accounts include name, email, and role. We export user records and map roles to Salesforce's permission model. Plezi-specific role names require manual review during scoping because role semantics differ between platforms. We resolve users by email match against the Salesforce destination org's User table. Any Plezi user without a matching Salesforce User is held in a reconciliation queue.

Plezi Contacts can be tagged for segmentation. We preserve all tag names and associations. In Salesforce, tags used for contact classification map to a multi-select picklist field on Contact or Lead. Tags used for content or campaign classification map to Salesforce Topics with TopicAssignment records. The customer chooses the tag strategy during scoping based on how they intend to use segmented data in Salesforce.

Plezi's behavioral scoring profiles are proprietary and not directly portable. We export the most recent score value and scoring history for each Contact and store it in a custom field plezi_behavioral_score__c on the Lead or Contact record. Scoring model rules (which behaviors contribute which point values) are documented separately as part of the Smart Campaign inventory and can be implemented as Salesforce assignment rules or Einstein Lead Scoring if the customer licenses that add-on.

If Plezi stores engagement activities (opens, clicks, form submissions as behavioral events), we map these to Salesforce Task records with custom event-type fields. Email engagement events (opens, clicks) map to Task records with a custom event type picklist. Meeting and call records from Plezi map to Salesforce Event and Task (TaskSubtype=Call) respectively. Activity timestamps are preserved as ActivityDate for timeline ordering.