Migrate from Voopty Inc. to Mailchimp

Voopty student records map to Mailchimp audience members. The student's email address becomes the subscriber hash for Mailchimp's MD5-based identity. First name, last name, and phone number map to Mailchimp FNAME, LNAME, and PHONE merge fields. We preserve the original student ID in a custom field STUDENT_ID to support reconciliation back to Voopty if the customer maintains the platform for back-office use.

Voopty client records (representing parents or adult learners) map directly to Mailchimp members. Client email maps to the subscriber identifier. We deduplicate against existing student members by email match since the same person may appear as both a student and a client in Voopty. Voopty's active client threshold (at least one lesson per month) maps to a CUSTOM_STATUS merge field rather than relying on Mailchimp's native subscription status alone.

Voopty course records (language programs, tutoring subjects, group classes) do not have a direct Mailchimp equivalent. We create Mailchimp tags from course names and apply them to members based on the student's enrolled_courses relationship in Voopty. Multiple courses per student result in multiple tags on the same Mailchimp member. We preserve the course identifier and course term (semester, academic year) as part of the tag name for segmentation.

Voopty subscription plans (individual lessons, group packages, monthly subscriptions) map to a combination of Mailchimp tags (plan type) and custom fields (plan status, next_billing_date, monthly_amount). We apply a SUBSCRIPTION_STATUS tag with values active, paused, or churned. Plan period and pricing amount migrate as merge fields but require truncation or splitting if the combined data exceeds Mailchimp's 255-character limit per text field.

Voopty staff records do not map to Mailchimp contacts because teachers and administrators are internal users, not marketing recipients. We create internal tags prefixed with INSTRUCTOR_ to mark members associated with a specific teacher for internal reporting. This allows the school to filter campaigns by assigned instructor without exposing teacher contact information in the Mailchimp audience.

Voopty scheduled sessions (static recurring class schedules, dynamic session bookings) have no equivalent in Mailchimp. Mailchimp is an email marketing platform and does not have a scheduling, calendar, or booking object. We extract the next three upcoming sessions per student as a custom field NEXT_SESSION for use in onboarding or welcome email personalization only. Full schedule history is excluded from migration.

Attendance tracking per session per student does not migrate to Mailchimp. Mailchimp has no attendance or session-level event object. We do not map attendance records. If the customer requires attendance tracking post-migration, we recommend a dedicated attendance tool (Google Sheets, Teamup, or a purpose-built education app) integrated via Mailchimp's webhook or Zapier connection.

Payment records tied to WayForPay, LiqPay, and Stripe integrations do not migrate to Mailchimp. Mailchimp does not store financial transaction data. We do not export payment amounts, transaction IDs, or billing history. Subscription status and plan amount migrate as described in the Subscription mapping; actual payment reconciliation remains in Voopty or moves to a dedicated accounting platform (QuickBooks, Xero, or Zoho Books).