Migrate from Plezi to HubSpot

Plezi lead scoring rules cannot be exported as data — they must be rebuilt in HubSpot

Plezi's scoring engine computes a numeric score per contact based on rules defined within the platform. These rules are application logic, not data records, and the Plezi API does not expose the scoring rule definitions in a structured format. When migrating to HubSpot, the numeric score value migrates as a static property (Plezi_Score__c), but the rules that produced it — point values per behavior, decay settings, threshold tiers — have no migration path. FlitStack delivers a Plezi scoring audit document listing all active rules and point values so your HubSpot admin can rebuild them as HubSpot property-based workflows. This is a manual step that must be planned alongside the data migration.

Plezi smart campaigns and automation logic do not transfer to HubSpot workflows

Plezi smart campaigns define lead nurturing sequences, trigger conditions, and action branches that are stored as internal automation configuration. HubSpot workflows (Automation Hub) are a separate system with their own trigger model, condition syntax, and action set. There is no export format that preserves Plezi campaign logic for import into HubSpot. FlitStack migrates campaign names and email send history as reference data, but the automation logic — drip sequences, enrollment triggers, goal steps, and delay rules — must be rebuilt manually in HubSpot. We provide a campaign export summary listing every active Plezi campaign, its enrolled contacts, and its action sequence so your team has a complete blueprint for the HubSpot rebuild.

Plezi engagement history requires API-based migration — CSV imports cannot preserve association links

Plezi engagement events (email opens, clicks, form submissions, page visits) are tied to contacts via internal record IDs. Standard CSV import into HubSpot can load contact properties but cannot natively link timeline events to contacts using Plezi's ID structure. FlitStack uses the HubSpot Engagement API and Bulk API to create timeline entries that reference the correct HubSpot contact IDs after the ID mapping is resolved. This API-based approach ensures that when a user opens a HubSpot contact record, the full engagement history from Plezi appears on the timeline in chronological order. A flat CSV import without ID resolution would create orphaned engagement records.

Duplicate contact risk when Plezi contacts already exist in HubSpot

If your team has been using HubSpot in parallel with Plezi, some contacts may already exist in HubSpot with different record IDs. A naive import by email would create duplicate contact records. FlitStack resolves duplicates by email match before the migration runs: existing HubSpot contacts are updated with Plezi property values rather than creating new records. Contacts that have no HubSpot match are created fresh. The deduplication logic is applied to contacts, companies, and deals based on the identifier your team specifies (email for contacts, domain for companies, deal name plus close date for deals).

HubSpot lifecycle_stage pick-list values must match Plezi lifecycle vocabulary exactly

HubSpot's lifecycle_stage is a standard pick-list field with predefined values (subscriber, lead, MQL, SQL, opportunity, customer, evangelist). If Plezi uses custom lifecycle stage names that do not match HubSpot's pick-list, those values cannot be saved to the standard lifecycle_stage field. FlitStack detects this mismatch during the pre-migration audit: Plezi lifecycle values that match HubSpot's list migrate directly; non-matching values migrate to a custom property (e.g., Plezi_Lifecycle_Stage__c) that accepts free text. Your team decides whether to remap values to HubSpot's standard list post-migration or use the custom field.