Migrate from Plumb5 to Mailchimp

Plumb5 Customer Profiles map to Mailchimp Subscribers within a designated Audience. We map standard fields (email, first name, last name, phone) to Mailchimp's merge field equivalents (EMAIL, FNAME, LNAME, PHONE). Custom properties from Plumb5 map to Mailchimp merge fields, which we create as Text, Number, or Date types during schema setup. Any Plumb5 profile without a valid email address is excluded and logged for the customer's review because Mailchimp requires an email address for every subscriber.

Plumb5's numeric scoring model (conversion propensity scores) cannot migrate as executable logic because Mailchimp has no native scoring engine. We write the last-known Plumb5 score value as a read-only custom merge field on the Mailchimp subscriber record. During discovery we capture the Plumb5 score definition (what behaviors contribute, what thresholds exist) and document it in a scoring rebuild guide so the customer's Mailchimp admin can implement a equivalent segmentation logic using Mailchimp automations or an add-on scoring tool.

Plumb5 marketing campaigns map to Mailchimp Campaigns with the associated Plumb5 contact memberships preserved as Groups or Tags on the Mailchimp Audience. If a contact was part of multiple Plumb5 campaigns, they receive multiple corresponding tags in Mailchimp. Campaign performance metrics (open rate, click rate from Plumb5) migrate as custom merge fields on the contact record rather than as Mailchimp campaign statistics since historical campaign stats are Mailchimp-native.

Plumb5 tags each customer interaction with a source channel (organic search, paid, social, email, direct, referral). We preserve this as Mailchimp Tags on the subscriber record. Tags include channel attribution values (e.g., source:organic_search, source:paid_google) and are created during the profile import phase so the customer can build Mailchimp segments filtering by original channel.

Plumb5 defines a proprietary lifecycle progression from anonymous visitor to brand advocate with six to eight named stages. Mailchimp has no native lifecycle field. We map each Plumb5 lifecycle stage value to a Mailchimp Tag (e.g., lifecycle:subscriber, lifecycle:mql, lifecycle:customer, lifecycle:advocate) and write these during profile import. The customer's admin can use these tags to rebuild Plumb5-style lifecycle segments in Mailchimp Automations.

Plumb5 auto-segmentation rules generate dynamic segment memberships based on behavioral criteria. Mailchimp handles dynamic segmentation through its Segment builder, not through migrated rule logic. We migrate segment membership as static Tags on each subscriber so the customer has the original audience lists available. We deliver a written segmentation map that lists each Plumb5 segment name, its definition criteria, and the equivalent Mailchimp segment builder configuration for the admin to implement.

Plumb5 stores Recency, Frequency, and Monetary (RFM) value as aggregated engagement KPIs per customer. Mailchimp does not natively store RFM data. We migrate these as read-only custom merge fields (P5_RFM_Recency__c, P5_RFM_Frequency__c, P5_RFM_Monetary__c) on the Mailchimp subscriber record. The customer can use these fields to build RFM-based segments in Mailchimp or export them to an external analytics tool for advanced segmentation.

Unsubscribed, bounced, andcomplained contacts from Plumb5 must be imported into Mailchimp as suppressed records before any campaign sends. Mailchimp requires explicit opt-in, so contacts with uncertain consent status from Plumb5 are imported to the suppression list and reconfirm via a re-permission campaign. This step is critical for deliverability and is executed before the main subscriber migration begins.