Migrate from Plezi to Twenty CRM

Plezi Contacts map to Twenty Person records. The Plezi contact's behavioral scoring profile (lead score, lifecycle stage) migrates as custom fields on Person. We create twenty_lead_score__c and twenty_lifecycle_stage__c in the Twenty workspace before import. Standard Plezi fields (name, email, phone, company link) map to Person.name, Person.emails, Person.phoneNumbers, and the Person.company link. Note that Twenty's Person object ships with fewer built-in fields than mature CRMs; we configure industry, job title, department, website, and social profile fields as custom fields during schema preparation.

Plezi Companies map directly to Twenty Companies. The company name, domain, industry classification, and any custom properties migrate to Company.displayName, Company.domainName, and custom fields. The Company record is created before Contact import so that the Person.company link is satisfied at insert time. If Plezi stores company enrichment data from a third-party provider, we flag each enrichment field and advise whether to recreate the enrichment in Twenty or skip it.

Plezi Campaigns (individual marketing initiatives with associated costs, channels, and dates) map to a Twenty custom object named Campaign. We pre-create the Campaign custom object with fields for campaign type, start date, end date, budget, and channel. Campaign costs and budget fields migrate as currency fields in Twenty's custom object schema.

Plezi Landing Pages are standalone assets with their own URLs and form associations. We export the page title, URL slug, and associated form reference. Because Twenty has no native landing page builder, we create a LandingPage custom object with fields for title, url, and form_id, and we document any embedded third-party widgets (webinar iframes, live chat scripts, custom JavaScript) during the audit phase so the customer knows which pages require manual recreation. Pages with non-exportable embedded content are flagged explicitly.

Plezi Forms capture leads and feed them into Smart Campaigns. We migrate form field names, required flags, and the target pipeline stage assignment as a custom object with field-level configuration. Custom field types in Plezi are mapped to the closest equivalent Twenty custom field type (text, number, email, phone, select). The form-to-Smart Campaign routing is documented in the Smart Campaign intent handoff rather than reproduced as automation.

Smart Campaigns are Plezi's core automation engine combining triggers, conditions, and actions. The logic is stored in a proprietary format that cannot be exported as runnable code. We reconstruct each Smart Campaign's intent by exporting the campaign trigger events, conditional rules, and action sequence separately. The output is a written inventory document with trigger, conditions, action steps, and a recommended Twenty Workflow equivalent for each Smart Campaign. The customer's admin uses this document to rebuild in Twenty's workflow builder. We do not migrate Smart Campaign logic as automation code.

Plezi Workflows manage multi-step nurture sequences and reference Contacts or Companies at each step. We export the step sequence, associated content blocks, and the trigger conditions. Dynamic personalization steps are flagged as requiring manual recreation. The output is a written step-by-step workflow inventory that the customer's admin uses to rebuild sequences in Twenty's workflow builder or via an external sales engagement tool.

Emails and content blocks used inside Smart Campaigns and Workflows are exportable as HTML and text variants. We carry over the HTML body and subject line for each email asset. Inline images may require re-hosting at a CDN URL and link updating. Because Twenty has no native email marketing module, these assets are delivered as a content library document with HTML files for the customer to use in their chosen email delivery tool or import into a sales engagement platform.

Plezi User accounts (team members with name, email, and role) map to Twenty Members. We export user records and attempt to map Plezi role names to Twenty's workspace permission model. Plezi-specific role names require manual review during the scoping phase because permission structures differ significantly between the two platforms. Active users are invited to the Twenty workspace before migration begins; inactive users are preserved in the export for reconciliation.

Plezi Contact tags migrate to Twenty's Tag model. Each tag name and its associations with Person records are preserved in the import. Tags used for segmentation purposes map directly to Twenty Tags. If the customer used Tags for content classification or campaign targeting, we document the tag taxonomy in the migration inventory for the admin to re-apply in Twenty.