Migrate from Plezi to Microsoft Dynamics 365 Sales

Plezi Contacts with a lifecycle stage of early-stage prospect (subscriber, marketing qualified) map to Salesforce Lead for follow-up by sales. Plezi Contacts with a sales-qualified or customer lifecycle stage map to Salesforce Contact attached to an Account. We run the split transform during migration using Plezi's lifecycle stage property and preserve the original value in a custom field plezi_lifecycle_stage__c on both Lead and Contact for reporting continuity.

Plezi Company records map directly to Microsoft Dynamics 365 Sales Account. The company domain becomes the Account Website field and serves as the deduplication key during import. Account records must be created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert.

Plezi Campaigns (individual marketing initiatives with associated costs, channels, and dates) map to Dynamics 365 Campaign. Campaign type, start and end dates, and budget fields migrate directly. Campaign Member associations from Plezi Contacts map to Campaign Members in Dynamics with Status mapped to a customer-defined response code.

Plezi Smart Campaigns store trigger-action logic in a platform-specific format that cannot be exported as executable automation. We reconstruct each Smart Campaign's intent from the source export by documenting trigger events, conditional rules, action sequences, and delay steps. The customer receives a written workflow inventory with recommended Dynamics Sales automation or Power Automate equivalents and rebuilds them post-migration.

Plezi multi-step nurture sequences export as step sequences and content block references but not as runnable packages. We preserve the step order and associated content block HTML/text for the customer's admin to reference when rebuilding in Power Automate. Dynamic content personalization steps that cannot be auto-reproduced are flagged in the handoff inventory.

Plezi Forms with field names, required flags, and target pipeline stage assignments migrate as a field inventory. Form field names and types map to equivalent Dynamics fields. The form itself (hosting, styling, logic) does not migrate; we recommend Dynamics Web-to-Lead or a Power Pages form as the replacement and document the field mapping to speed up reconstruction.

Plezi Landing Pages export as page title, URL slug, and form reference associations. Pages with 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, flag which pages require manual recreation versus automated rebuild, and deliver a full URL mapping so the customer's web team can plan redirects.

Plezi engagement records (email, call, meeting, task) migrate to the corresponding Microsoft Dynamics 365 Sales activity objects. Emails land as EmailMessage records with body and subject preserved, linked to a Task for the activity timeline. Calls land as Task with TaskSubtype=Call and duration preserved. Meetings land as Event with start and end times preserved. Activity ordering is maintained by setting ActivityDate to the original Plezi timestamp.

Plezi email and content block HTML/text exports as raw content. We carry over the HTML body and subject line. Inline images may require re-hosting at the destination if the URLs are not publicly accessible. Content blocks used inside Smart Campaigns are documented with their associated workflows for the customer's admin to reassemble in Power Automate or Dynamics email templates.

Plezi User accounts (name, email, role) export for mapping to Dynamics 365 User records. Plezi-specific role names require manual review against the Dynamics security model. We resolve users by email match and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before record import resumes.

Plezi Contact tags migrate as a custom field on Lead and Contact. Tags used for segmentation map to either a multi-select picklist field or Dynamics Topics with TopicAssignment records depending on the customer's preferred taxonomy. The strategy is chosen during scoping.