Migrate from Plezi to Nutshell

Plezi Contacts map to Nutshell People. Standard fields (name, email, phone, address) migrate directly. Plezi's behavioral scoring profile properties (scoring rules, score values, lifecycle stage) migrate as Nutshell custom fields of the appropriate type: numeric fields for score values, picklist fields for lifecycle stage. We preserve the original Plezi lifecycle stage label in a custom field plezi_original_lifecycle__c for audit and segmentation continuity. Person is created before any associated Company so that the Company lookup is satisfied at insert time.

Plezi Companies map directly to Nutshell Companies. The company name, domain, industry, and any custom properties migrate directly. We use the Plezi company domain as the dedupe key during Nutshell import to avoid duplicate Company records where the same company appears across multiple Plezi Contacts. Company is imported before Person so that the Company lookup relationship resolves correctly for each Person record.

Plezi Campaigns (marketing initiatives with associated costs, channels, and dates) map to Nutshell Campaigns. Campaign type, start/end dates, budget fields, and status migrate as standard Nutshell Campaign fields. Custom Plezi campaign properties migrate as Nutshell Campaign custom fields if the customer requires the metadata for reporting.

Plezi Landing Pages export as page title, slug, and form reference. Pages with embedded third-party widgets (webinar registration iframes, live chat scripts, custom JavaScript) are flagged during the audit phase because the embedded content cannot be extracted. We document each landing page's embedded components and classify pages as fully migratable, manually recreatable, or requiring redesign in Nutshell's Marketing landing page builder.

Plezi Forms migrate as Nutshell Forms. We carry over form field names, required flags, and any pipeline stage assignment logic. Custom field types (date pickers, dropdowns, checkboxes) map to the closest Nutshell Form field equivalent. Where a Plezi form feeds into a Smart Campaign trigger, we document the trigger condition separately so that the customer can recreate the automation logic in Nutshell's Workflows after migration.

Plezi Smart Campaigns cannot migrate as executable automation code. We extract each Smart Campaign's trigger events, conditional rules, and action sequences from the source export, reconstruct the logic as a written document (trigger type, conditions, delay steps, action sequence), and deliver it to the customer for rebuild in Nutshell Workflows. Dynamic personalization steps that cannot be automatically reproduced are flagged explicitly. We do not build Nutshell Workflows as part of migration scope.

Plezi Workflows (multi-step nurture sequences with step references to Contacts or Companies) export as step sequences and content block references. We carry over the step order and content associations. HTML and text variants of emails used inside workflows migrate as content blocks. Dynamic content personalization steps are flagged as non-migratable. The customer rebuilds nurture sequences in Nutshell Workflows using the step inventory we deliver.

Plezi User accounts (name, email, role) export and map to Nutshell Users by email match. Plezi-specific role names (admin roles, campaign manager roles) require manual review against Nutshell's permission model because role naming conventions differ between platforms. We flag any Plezi role that has no direct Nutshell equivalent and advise the customer on the closest Nutshell permission set.

Plezi Tags on Contacts migrate to Nutshell Tags. We preserve tag names and associations so that segmentation built on tags in Plezi carries over to Nutshell for use in filtering, reporting, and workflow triggers. Tag strings longer than Nutshell's character limit for tag names are truncated with a note to the customer.