Migrate from Ayna to Mailchimp

Ayna Contact records map to Mailchimp Subscribers within an Audience. The contact's email address is the primary identifier and dedupe key. First name, last name, phone, and company association map to the standard Mailchimp merge fields FNAME, LNAME, PHONE, and COMPANY. We validate email format and MX record existence during import preparation to avoid bounced imports.

Ayna Company records map to Mailchimp in one of two ways depending on plan tier. On Premium (which supports Company merging), we map to the COMPANY merge field on the Subscriber. On Essentials and Standard, we use Mailchimp Tags to preserve company association, creating one tag per unique Company name and applying it to all Subscribers belonging to that company. We recommend Premium for customers requiring structured company-to-contact relationships.

Ayna Channels represent communication and social platforms connected to the brand (social accounts, messaging platforms, website channels). Mailchimp does not have a native Channel equivalent. We map active channels to Mailchimp Groups within an Audience (if the customer uses groups for segmentation) or to Tags for lighter-weight classification. Archived channels are suppressed from migration and documented for reactivation review in Mailchimp.

Ayna Website Domain records tied to brand protection and website synchronization have no direct Mailchimp equivalent. We extract domain records during discovery and either create a domain-based Tag on each Subscriber ([email protected]) or document the domains for the customer to use in Mailchimp's domain authentication settings for SPF/DKIM. Domain ownership metadata does not transfer to Mailchimp as a data field.

Ayna custom fields on Contacts migrate to Mailchimp Merge Tags. Mailchimp caps at 25 merge tags on Essentials and Standard plans, 80 on Premium. We audit Ayna's custom field schema during discovery, identify fields exceeding the plan limit, and work with the customer to prioritize the most operationally critical fields. Fields beyond the limit are documented in a field inventory for the customer's admin to activate post-migration on Premium or to consolidate via tagging strategy on lower tiers.

Ayna User records (name, email, role) map to Mailchimp Audience Members or Admins depending on the user's access level. Contributors and Viewers in Ayna map to Mailchimp Audience Members with appropriate permission levels. We resolve by email match. Any Ayna User without a matching Mailchimp account goes to a provisioning queue for the customer's Mailchimp admin.

Ayna Social Account connections for brand monitoring cannot migrate as live integrations to Mailchimp because OAuth tokens and platform API keys are not exported. We document the current social account connections (Facebook Page, Instagram Business, Twitter/X, LinkedIn Company Page) during discovery and flag which require re-authentication in Mailchimp's Connected Apps or in a third-party social sharing integration. The customer re-links social accounts post-migration.

Attachments to Ayna brand protection records (screenshots, legal documents, brand assets) reference file URLs or stored files that do not have a native Mailchimp equivalent beyond email attachment within campaigns. We export attachment metadata and URLs, and we document the attachment inventory in a handoff file so the customer's admin can re-upload critical brand assets to Mailchimp's Content Studio or link them within email campaign content manually.