Migrate from Cronberry to Mailchimp

Cronberry Contact records with name, email, phone, and custom field values map directly to Mailchimp Audience members. We map Cronberry's field names to Mailchimp merge tags (EMAIL, FNAME, LNAME, PHONE, and up to 29 custom merge fields on Standard, 79 on Premium). We run deduplication against the pre-migration report before import, matching on email as the primary key and phone as secondary, and we import duplicates as suppressed records in Mailchimp rather than active audience members.

Cronberry's tag associations on Contacts map to Mailchimp Tags. Tags preserve segmentation context across both platforms. We extract the full tag list from Cronberry's export and create matching Tags in the destination Audience before contact import, then assign tags during the contact insert phase using Mailchimp's tag-add endpoint in batches to respect API rate limits.

Cronberry Smart Segments are defined by conditional rules against contact field values, but the rule logic does not export as reusable schema. We reverse-engineer segment membership by querying which contacts belong to each segment, documenting the conditions implied by the contact data (field values, tag presence, date ranges). Your team rebuilds these conditions in Mailchimp's Segment builder using AND/OR logic on merge field values and tag membership. We deliver a segment map as part of the migration package.

Cronberry Campaigns (Email channel only) map to Mailchimp Campaigns. We extract campaign name, subject line, sender info, send time, and audience assignment. Campaign content (HTML body, images) maps to Mailchimp's template content block. Cronberry campaigns using SMS, Push, or WhatsApp channels are flagged as non-migratable because Mailchimp does not support these channels natively. We deliver a channel-specific gap report identifying which campaigns cannot move and recommending alternatives.

Cronberry Email Templates with personalization variables map to Mailchimp Templates. We extract template HTML content, inline CSS, images, and variable placeholders, then reconstruct them in Mailchimp's template format. Rich formatting may require minor adjustment due to differences in CSS inlining between platforms. SMS and Push templates have no Mailchimp equivalent and are excluded from migration with a written note in the template inventory.

Cronberry User and Agent records map to Mailchimp Team Members. We extract user email addresses and role names (Admin, Manager, Agent). Mailchimp's permission model uses Audience access levels rather than Cronberry's role structure, so we assign migrated users as Audience Managers or Account Admins based on their original access level. Mailchimp's free plan supports 1 user; Standard and Premium support multiple team members.

Cronberry Form definitions including field structure, conditional logic, and submission targets are extractable as schema. We map Cronberry form fields to Mailchimp merge tags and document the form's structure so your team can recreate the form in Mailchimp's signup form builder. Visual layout, drag-and-drop positioning, and conditional field rules cannot be preserved and require manual rebuild in Mailchimp's Form builder.

Cronberry's behavioral event logs (opens, clicks, push interactions, custom event types) map partially to Mailchimp's activity history. Mailchimp automatically tracks opens and clicks on sent campaigns for email channels, but it does not store arbitrary custom event types that Cronberry may have captured (e.g., form submissions, cart events, push interactions). We migrate behavioral events that match Mailchimp's tracked types (Email Open, Email Click) and flag custom event types as non-migratable in the event inventory. We do not migrate push notification events because Mailchimp does not support push channels.

Cronberry Company records map to a company_name custom merge field on the Mailchimp Audience member rather than a separate object. Mailchimp does not have a native Companies/Accounts object at the email marketing tier. If your Cronberry implementation stores company-level data as a separate object with related Contacts, we flatten it by merging the primary company name and any key company fields into custom merge tags on the Contact record. We document the original company schema for reference.