Migrate from Flavor CRM to Mailchimp

Flavor CRM Students are the primary contact equivalent and map 1:1 to Mailchimp Contacts. We export all Student fields including name, email, phone, enrollment status, and any custom properties. Student-specific properties like enrollment_date and enrollment_status are preserved as Mailchimp merge fields (e.g., ENROLLDATE, ENROLLSTAT). The Lead-to-Student conversion link from Flavor CRM is extracted as a custom merge field (e.g., ORIGLEAD_ID) so that historical enrollment funnel reporting can be reconstructed by the customer's admin using a lookup spreadsheet.

Flavor CRM Leads map 1:1 to Mailchimp Contacts. We export all Lead fields including source, status, and custom properties. Lead records that share an email address with an existing Student record are flagged in the deduplication pass for the customer's review before final load. The original Lead status is preserved as a merge field (e.g., ORIGLEADST) so that marketing-sourced versus enrollment-sourced contacts can be segmented post-migration.

Flavor CRM Parent records are exported separately and merged into the unified Contact list by email deduplication. A Parent record that shares an email with a Student or Lead is reconciled using the preference rule established during scoping (typically: prefer the Student record and append Parent-specific properties). The original object type is preserved as a merge field (e.g., ORIGOBJTYPE: 'Parent') so that parent-specific segments can be built in Mailchimp. If a Parent email appears on multiple Student records (siblings), each student contact retains the shared Parent contact's merge field values.

Flavor CRM Company records have no direct Mailchimp equivalent. We export Company data as a structured CSV (company name, domain, industry, size) and optionally map the company name to a Mailchimp Group or Tag on each Contact record if segmentation by organization is required. If the institution does not require organization-level segmentation, Company data is delivered as a standalone CSV archive with a reference key linking back to the Contact email.

Flavor CRM Deals and pipeline stages have no Mailchimp equivalent. We export the full Deal record including stage, amount, owner, create date, and close date as a structured CSV file. Deal values and pipeline stages are documented with field names so that the customer can import the CSV into a separate reporting tool or spreadsheet if pipeline history is required. The Deal-to-Contact linkage is preserved via the contact email key in the CSV for cross-referencing.

Flavor CRM Invoice records store billing documents that behave like financial records, not CRM notes. Mailchimp has no invoice, payment, or financial object. We export invoice line items and payment history as a structured CSV with invoice_id, student_email, amount, status, and payment_date fields. If the customer has PDF copies of invoices in Flavor CRM, we attach them to the corresponding Contact record as an archive; otherwise, the CSV serves as the financial reference file. The customer routes this archive to a separate accounting system or spreadsheet for financial reporting.

Flavor CRM Class records (name, schedule, instructor, capacity, enrollment count) have no Mailchimp equivalent. We export Class data as Mailchimp Groups (e.g., 'Math 101', 'Science 202') and apply them to Contact records based on the enrollment relationship in Flavor CRM. Class schedules, instructor assignments, and capacity data are exported as a separate CSV archive since Mailchimp does not support scheduling objects. The student-to-class relationship is preserved via the contact email key in the Class CSV.

Flavor CRM engagement records (calls, emails, meetings, tasks) have no Mailchimp equivalent. Mailchimp tracks campaign-level engagement (opens, clicks, bounces, unsubscribes) natively but does not store individual call logs, meeting records, or task histories. We export the full engagement history as a structured CSV with contact_email, activity_type, activity_date, and activity_notes fields, and deliver it alongside the migration. The customer can import this CSV into a separate activity tracking tool if historical engagement records are required for compliance or reporting.

Flavor CRM Staff records store employee data separately from student records. Mailchimp does not have a Staff or User management module. We export Staff as a standalone CSV file (name, email, role, permissions) and deliver it as a reference archive. If any Staff member appears on the Contact list (e.g., staff who are also parents), we cross-reference by email and merge the Staff record's role information into the Contact's merge fields rather than creating duplicate entries.

Flavor CRM does not expose a documented bulk export endpoint for binary attachments and media files. Contract documents, student photos, and uploaded files require individual downloads and are not included in the automated migration scope. We flag this gap during scoping and deliver a written list of attachment locations in Flavor CRM so that the customer's admin can manually download critical files. Binary attachments are not imported into Mailchimp as Mailchimp does not support document attachments on contact records.