Migrate from Wyvern Magic to Mailchimp

Wyvern Magic Contacts map directly to Mailchimp Members within a single Audience. Email address is the dedupe key; we deduplicate at extraction so one Member record is created per unique email. Standard fields (first_name, last_name, email, phone) map to their Mailchimp equivalents. Contact owner assignments from Wyvern Magic do not map to Mailchimp user roles but can be stored in a custom merge field for segmentation.

Wyvern Magic Company records do not have a direct Mailchimp equivalent; Mailchimp Members do not support nested Company objects. We extract company_name, industry, employee_count, and domain from Wyvern Magic Company and map them to Mailchimp merge fields (COMPANY, INDUSTRY, EMPLOYEES) attached to the Member. The company-contact association is preserved as a Tag on the Member using the company name for post-migration segmentation.

Mailchimp has no native pipeline or deal record. We capture each Wyvern Magic Deal's stage, amount, close_date, and probability as merge fields (DEAL_STAGE, DEAL_AMOUNT, DEAL_CLOSE, DEAL_PROB) on the associated Member record, or apply a Tag per deal stage (e.g., Prospect, Qualified, Proposal Sent, Closed Won) at migration time. The customer decides during scoping whether to store deal data as merge fields or Tags.

Wyvern Magic Leads map to Mailchimp Members using the same email dedupe logic as Contacts. Lead status (New, Contacted, Qualified, Unqualified) and lead source migrate as merge fields (LEAD_STATUS, LEAD_SOURCE). Lead score values migrate as a merge field (LEAD_SCORE) if present in Wyvern Magic.

Wyvern Magic custom fields on Contacts, Leads, and Companies map to Mailchimp merge fields. Mailchimp limits merge fields to 255 characters per field and 40 merge fields per Audience. For fields exceeding 255 characters, we truncate and flag the record for manual review. For custom properties exceeding the 40-field limit, we prioritize the 40 most business-critical fields and store the remainder in a JSON-formatted MEMO merge field.

Wyvern Magic tags applied to Contacts, Leads, and Companies migrate to Mailchimp Tags attached to the Member. Multi-value tag arrays from Wyvern Magic flatten into individual Mailchimp Tags. We preserve tag names exactly as they appear in Wyvern Magic so segmentation logic that relies on tag names remains functional after cutover.

Wyvern Magic email engagement history (sent, opened, clicked, bounced) does not migrate to Mailchimp as a historical record because Mailchimp campaign activity is generated by Mailchimp campaigns. We export a written engagement summary from Wyvern Magic (total emails sent, open rate average, click rate average) and store it in a MEMO merge field on each Member for reference.

Wyvern Magic call, meeting, and task activity records have no Mailchimp equivalent. We export a written activity summary per Contact (call count, meeting count, open task count) and store it in a MEMO merge field on the Member. The customer uses this data to prioritize follow-up after cutover.

Wyvern Magic Owner records do not map to Mailchimp Users. We extract the list of unique Owner emails referenced on migrated records and provide a written list for the customer's admin to provision Mailchimp Admin or Manager roles manually. Mailchimp role provisioning requires admin action in the account settings and is not automatable via API.