Migrate from Rizer to Mailchimp

Rizer Contact records map to Mailchimp Audience members. Email address is the primary dedupe key. First name, last name, phone, and address fields migrate to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). We preserve the original Rizer lifecycle stage in a custom merge field rizer_lifecycle_stage__c for reference and segmentation. Opt-in status migrates to the Member Status field; unsubscribed and bounced contacts import as unsubscribed to protect deliverability.

Rizer Companies linked to Contacts migrate as structured data in Mailchimp merge fields on the member record (e.g., COMPANY_NAME, COMPANY_INDUSTRY). Mailchimp does not have a native Company object, so we store company association as a tagged group and populate merge fields with the linked company name and industry tags. If the customer requires a full company-account model, this is documented as a post-migration configuration recommendation.

Rizer Tags on Contacts migrate directly to Mailchimp Tags on the corresponding Audience member. Tags serve as the primary segmentation signal in Mailchimp. We handle multi-value tag lists from Rizer by splitting into discrete Mailchimp Tags. Tag normalization corrects case inconsistencies and removes duplicates during the transform phase.

Rizer custom fields on Contacts map to Mailchimp merge fields. Mailchimp requires merge fields to be created in the Audience before import; we create them during the setup phase using the field type closest to the inferred data type. Date fields stored as strings in Rizer are parsed and written to Mailchimp date-typed merge fields. Multi-select values stored as delimited text in Rizer migrate to Mailchimp text merge fields with the delimiter preserved.

Rizer's referral source and attribution window on Contact records migrate to Mailchimp custom merge fields (REFERRAL_SOURCE, REFERRAL_CAMPAIGN, ATTRIBUTION_WINDOW). These are stored as text fields because Mailchimp does not have a native referral tracking object. We document the full referral field list during scoping so the customer can set up matching merge fields in the destination Audience before migration.

Rizer Workflow sequences do not migrate to Mailchimp as code. We extract every active Workflow's trigger conditions, tag actions, delay rules, and email sequence order and deliver them as a written Workflow inventory document. The customer's team rebuilds the automations in Mailchimp's Customer Journey builder. Workflow names and trigger logic are preserved in the handoff document for reference during rebuild.

Rizer Team Members (user accounts) map to Mailchimp account users by email match. We generate a reconciliation report of all Rizer team members and their role assignments (admin, manager, member). The customer provisions corresponding Mailchimp users in their account settings before cutover. Team members without a Mailchimp account are flagged in the handoff document.

Rize time-tracking Clients (a separate product from Rizer Social) are out of scope for the standard CRM migration. If the customer requires Rize data moved alongside Rizer Social contacts, we scope a separate pass and map Clients to Mailchimp Groups or store them as structured merge fields depending on the use case. This requires a separate export from rize.io and is priced as an additional object scope.