Migrate from Referrizer to Mailchimp

Referrizer Contacts map directly to Mailchimp Members within a target Audience. The contact's first name, last name, email address, and phone number transfer to the corresponding Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE). We validate email syntax before import because Mailchimp rejects malformed addresses and removes them from the import batch without partial recovery. Duplicate detection uses email address as the primary key; if a Member with the same email already exists in the Mailchimp audience, we update rather than create.

Referrizer custom fields (key-value properties on contact records) map to Mailchimp merge fields. Mailchimp enforces a 255-character limit on all text merge field values; any Referrizer field containing content longer than 255 characters is truncated at insertion with a flag raised in the reconciliation report. Number fields from Referrizer map to Mailchimp number merge fields without truncation. Date fields map to Mailchimp date merge fields. We enumerate the full custom field schema during discovery by calling GET /contacts and inspecting property names and types before designing the merge field map.

Referrizer stores loyalty point balances as numeric custom properties on contact records rather than as a distinct loyalty object. We separate these fields during transformation and create a custom number merge field in Mailchimp (e.g., LOYALTY_PTS) to carry the point balance. Because Mailchimp has no native loyalty program logic, the point value is informational data only. The customer should configure Mailchimp Customer Journeys to trigger based on this merge field if they want programmatic loyalty email behavior, but the logic itself does not migrate.

Referrizer contact labels (e.g., 'VIP', 'gym-member', 'laser-follow-up') transfer to Mailchimp Tags on each Member. Tags are flat string labels in Mailchimp; there is no label hierarchy or category structure as there is in Referrizer. If the customer used nested label groups in Referrizer, we flatten them into combined tags (e.g., 'location-downtown' and 'tier-gold' become two separate tags on the same Member) and document the flattening rule in the handoff report.

Referrizer Regular and Automated Campaign records (type, status, configured triggers) transfer as metadata to a campaign inventory document rather than as executable code. Mailchimp's Customer Journey builder is a different automation model with trigger types, conditions, and delay actions that do not have a direct mapping from Referrizer campaign logic. We document each Referrizer campaign's trigger, audience, and scheduled sends so the customer's admin can recreate equivalent Customer Journeys in Mailchimp.

Referrizer Offers (promotional codes, reward structures, referral link associations) are not a Mailchimp-native object. We extract offer codes, reward amounts, and referral link URLs as text custom merge fields on the relevant Contact records. The customer recreates offer logic in Mailchimp by building Customer Journeys that reference these stored values. We do not migrate referral relationship graphs (who referred whom) as a distinct structure; we store the referring contact's email as a merge field on the referred contact if that relationship exists in Referrizer's data model.

Referrizer's review request history (which contacts received requests, when, and to which platform) is stored as activity on the contact object. We extract the last review request date, the platform requested (Google, Yelp, Facebook), and the request status as custom merge fields in Mailchimp. This preserves a record of review outreach but does not replicate the automated review request workflow; the customer rebuilds that automation in Mailchimp using Customer Journeys if needed.

Referrizer's Smart Inbox stores conversational threads between contacts and the business, but no documented public API endpoint exposes this data. Only campaign-level sent/delivered metrics are accessible via the Reports API. We explicitly confirm with the customer during scoping whether inbox conversational history is critical. If it is, we recommend manual export of any required message threads from the Referrizer UI before the migration date. We cannot migrate Smart Inbox data programmatically and flag this as a data loss item in the discovery report.

Referrizer's Pipeline and lead management features have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a CRM with deal tracking. Pipeline stages, deal values, and lead status do not map to Mailchimp objects. We do not migrate pipeline data. If the customer needs pipeline tracking, they should evaluate a CRM alongside Mailchimp post-migration. We document the pipeline stage distribution from Referrizer in the handoff report so the customer can assess whether a separate CRM is needed.

Referrizer's multi-location model associates contacts with specific business locations. We scope extraction by location account ID during the extract phase to prevent cross-contamination. In Mailchimp, location can be preserved either as separate Audiences (one per location) or as a single Audience with a location-identifier merge field on each Member. We confirm the preferred strategy with the customer during scoping. If separate Audiences are chosen, we create a Mailchimp Audience per location and map contacts accordingly; if a single Audience is chosen, we add a LOCATION merge field to each contact during import.