Migrate from Profi to Mailchimp

Every Profi client record maps to a Mailchimp subscriber. Email address is the required unique identifier for the subscriber. If the Profi client has no email address, the record cannot become a Mailchimp subscriber and is flagged as an exception.

Profi course enrollments transform into tags applied to the corresponding Mailchimp subscriber record. For example, a client enrolled in 'Advanced Coaching Program' receives the tag 'enrolled_advanced_coaching_program'. When clients participate in multiple courses, each enrollment generates a separate tag on the same subscriber, creating a complete enrollment history within Mailchimp.

Session booking data in Profi contains granular appointment details that do not fit Mailchimp's contact model. We extract booking type information and create descriptive tags such as 'booking_60min', 'booking_group_session', or 'booking_initial_consultation' rather than preserving individual appointment timestamps. This approach provides useful segmentation data without attempting to recreate time-series scheduling information that Mailchimp cannot store natively.

Profi custom fields per client map to Mailchimp merge fields in the target audience. Text fields become TEXT merge fields. Number fields become NUMBER merge fields. Date fields become DATE merge fields. Mailchimp limits text merge fields to 255 characters — longer Profi text fields are truncated with a flag.

Profi's email opt-in flag maps to Mailchimp's subscriber status through a direct value translation: opted-in clients become 'subscribed', explicitly unsubscribed clients become 'unsubscribed', and bounced or invalid email addresses become 'cleaned'. Clients with no explicit subscription status default to 'subscribed' unless your specific migration plan requires a re-confirmation opt-in workflow to be implemented before importing.

Mailchimp subscriber profiles do not expose a native field for tracking when the contact was originally created in the source system. To preserve acquisition cohort data, we store the original Profi client creation timestamp in a dedicated merge field (CLIENT_CREATE_DATE) so you can filter and report by when subscribers originally joined Profi.

Profi client notes transfer directly as Mailchimp subscriber notes. Both platforms treat notes as free-text annotations attached to the individual contact record. Notes are preserved in their entirety during migration and are not lost or truncated. However, neither platform makes notes searchable within segment criteria — notes serve as reference information visible on the contact record but cannot drive automated segmentation logic.

Admin-applied tags in Profi transfer directly as Mailchimp tags on the corresponding subscriber record. This includes manually created tags intended for segmentation purposes, such as source attribution tags or client classification labels. Tags do not get deleted when future enrollments occur — they accumulate on the subscriber record, building a historical tag profile over time.

Profi course content, video URLs, and drip delivery schedules have no Mailchimp equivalent. This data does not migrate. We provide an export of the course structure so your team can rebuild email sequences in Mailchimp Customer Journeys that mirror the original delivery logic.

Profi payment records and invoice history do not map to Mailchimp. We preserve transaction data in a CSV export linked by subscriber email so you can cross-reference payments if needed for segmentation, but Mailchimp does not store financial records natively.