Migrate from Plezi to Mailchimp

Plezi Contacts map directly to Mailchimp subscribers within a target Audience. We map standard fields: First Name, Last Name, Email Address, Phone, and any custom properties to Mailchimp Merge Fields. Behavioral scoring from Plezi (numeric score value and current score tier) migrates as custom merge fields the customer's admin uses to build segments post-migration. Lifecycle stage from Plezi migrates as a Tag on the subscriber so the team can filter by original lifecycle status.

Plezi Companies do not map to a native Mailchimp object because Mailchimp has no Companies or Accounts concept. Instead, company-level properties from Plezi (company name, domain, industry, size, address) migrate as Merge Fields on the linked Contact record. Where a single Plezi Company is linked to multiple Contacts, we write the same company merge field values to each subscriber. The customer should consider whether company-level reporting is needed in Mailchimp; if so, a workaround like Mailchimp's Groups for Companies or a CRM integration may be required post-migration.

Plezi Campaigns (marketing initiatives with budget, channel, and date metadata) map to Mailchimp Campaigns with the campaign name, type, and date range preserved in the campaign title or description. Note that Mailchimp Campaigns are email campaign records; campaign-level budget and cost data from Plezi does not map to a native Mailchimp field and is delivered as a supplementary CSV for the customer's records.

Plezi Landing Pages are standalone assets with their own URLs and form associations. We export the page title, slug, and a static HTML representation of the page content. Pages containing embedded third-party widgets (webinar registration iframes, live chat scripts, custom JavaScript, dynamic personalization) cannot be fully extracted and are flagged during the audit phase. The customer receives a written page inventory with each page marked as fully migratable, requiring manual recreation, or requiring third-party rebuild.

Plezi Forms capturing leads into Smart Campaigns map to Mailchimp Signup Forms. Form field names and required flags map to Mailchimp Merge Fields. The target pipeline stage assignment from Plezi does not have a native Mailchimp equivalent and is documented separately for the customer's admin to configure as a Tag-based automation trigger post-migration. Custom field types are mapped to the closest Mailchimp field type (text, number, dropdown, date, address).

Plezi Smart Campaigns store trigger-action logic in a proprietary format that cannot be exported as a runnable package. We reconstruct each Smart Campaign's intent from the Plezi export: trigger event type (form submission, page visit, score threshold, tag change), conditional rules, and action sequence (email send, stage change, tag apply, task create). This intent is delivered as a written automation inventory with a recommended Mailchimp Customer Journey equivalent. The customer's team or a Mailchimp specialist rebuilds the automations inside Mailchimp's automation builder. Smart Campaigns are the highest-effort rebuild item in any Plezi to Mailchimp migration.

Plezi Workflows (multi-step nurture sequences with content blocks) are documented separately from Smart Campaigns during migration. We export the step sequence, step type, and associated content blocks as HTML and plain text. Dynamic personalization steps that reference Plezi's variable substitution engine are flagged as requiring manual reconstruction in Mailchimp. The customer receives a step-by-step Workflow inventory document that their team uses to rebuild sequences in Mailchimp Automations.

Emails and content blocks used inside Plezi Smart Campaigns and Workflows are exportable as HTML and text variants. We carry over the HTML body and subject line. Inline images may require re-hosting because embedded image URLs from Plezi's CDN may not persist post-cancellation. We flag all image URLs requiring re-hosting and provide a list of images to upload to Mailchimp's built-in content storage.

Plezi Tags applied to Contacts migrate as Mailchimp Tags on the corresponding subscriber. Tags used for segmentation in Plezi Smart Campaigns are documented with their segmentation context so the customer can rebuild the segment logic in Mailchimp using the migrated Tags and Merge Field conditions.