Migrate from Pega Platform to Mailchimp

Pega contacts are embedded inside case instances — not standalone records

Pega Platform does not store contacts as top-level standalone records in the way a traditional CRM does. Contacts are embedded pages inside case instances (Work- class objects), and the same contact can appear in multiple cases. Extracting contacts requires parsing the case data structure, identifying the embedded Contact page, and de-duplicating by email address before writing to Mailchimp. If your Pega application uses custom class structures for contacts rather than the standard Data-Contact class, the extraction logic must be adjusted per your ruleset. FlitStack inspects your Pega application class hierarchy during the discovery phase to map the exact extraction path before migration begins.

Mailchimp merge fields are limited to 300 per Audience and 255 characters per text field

Mailchimp enforces a 300-merge-field limit per Audience and truncates text merge fields at 255 characters. Pega applications with more than 300 custom properties on a contact record require prioritization — we migrate the most commercially relevant fields first and flag the remainder. Long-text Pega properties (such as pyNote, pyDescription, or custom large-text fields) are truncated to 255 characters with a [TRUNCATED] suffix and a reference to the full content stored in the JSON audit export. This ensures you retain the complete data even though Mailchimp cannot display it natively.

Pega Organization hierarchies cannot be replicated in Mailchimp's flat model

Pega supports parent-child organization hierarchies (an Organization can have N child Organizations with arbitrary nesting depth). Mailchimp has no organizational hierarchy whatsoever — every subscriber belongs to one Audience with no parent-account or subsidiary relationship. When migrating from Pega, we flatten the hierarchy by writing the top-level parent organization name to the COMPANY merge field and appending child-organization references as a comma-separated list in PARENT_ORG. You cannot segment by organizational hierarchy in Mailchimp without rebuilding that logic using tags or multiple Audiences, which is a manual decision your team must make post-migration.

Pega workflows and case-management logic have no Mailchimp equivalent

Pega workflows, assignment routing rules, decision trees, and case-stage logic are core to how Pega operates and cannot be transferred to Mailchimp. Mailchimp's automation builder is triggered by subscriber actions (sign-up, purchase, date-based triggers) and has no concept of multi-stage case routing, escalation rules, or operator assignment. Any Pega workflow that represents a business process — such as an onboarding case that moves through Intake, Review, Approval, and Completion stages — cannot be replicated in Mailchimp. FlitStack exports workflow definition references (JSON export of Pega ruleset structure) so your Mailchimp team can use it as a rebuild reference, but the automation itself must be reconstructed from scratch in Mailchimp's Customer Journey builder.

Pega's case notes and pulse activity are not Mailchimp-native records

Pega case notes (comments, pulse posts, assignment history) are audit records tied to the case lifecycle. Mailchimp tracks subscriber activity as email opens, clicks, and purchases — it has no concept of internal case notes. We export Pega case notes as a JSON reference file linked to each subscriber by their email hash. This file is included in your migration deliverable and can be imported into a separate system (a CRM, a knowledge base, or an internal audit tool) if needed for compliance. You cannot view Pega case notes inside Mailchimp after migration.