Migrate from Flexie to Mailchimp

Flexie Workers map to Mailchimp Contacts within a destination Audience. First name, last name, and email address are the core fields. We resolve the email field from Flexie's worker contact details and use it as the subscriber key. Workers without a valid email address are held in a reconciliation queue for manual review before import because Mailchimp requires a valid email for contact creation.

Each Flexie custom property on a Worker record translates to a Mailchimp merge field in the destination Audience. We pre-create the merge field schema before contact import, mapping Flexie field types (text, number, date, picklist) to Mailchimp merge field types (text, number, date, dropdown). Picklist values from Flexie custom properties must be reviewed for character limits; Mailchimp merge field options support up to 255 characters per value.

Flexie Venues do not have a direct Mailchimp equivalent because Mailchimp is organized by Audience rather than by location. We offer two strategies: (1) Venue becomes a tag applied to every Worker assigned to that venue, preserving the worker-to-venue relationship; (2) Venue becomes a Segment definition within the Mailchimp Audience based on a merge field value. The customer chooses the strategy during scoping. Multi-location operations with over 20 venues may prefer tags for simplicity; operations requiring location-based reporting may prefer segments.

Shift Assignment records link Workers to Shifts with status (accepted, pending, declined) and timestamp. If the customer wants to preserve shift participation history in Mailchimp, we apply tags like 'shift-accepted-q3-2025' or 'shift-pending' to the Worker's contact record. This is an optional scope item; Mailchimp cannot represent shift times or schedules as structured data. Tags are applied in batch after the core contact migration completes.

Flexie workflows are automation sequences with triggers, conditions, and actions that do not export as code to any external system. We document every active Flexie workflow during discovery, capturing the trigger type (entity form submission, shift status change, date-based), the conditional logic, and the sequence of actions. This document is delivered to the customer for manual rebuild in Mailchimp Customer Journeys. Workflow documentation includes a recommended Mailchimp trigger, condition, and action equivalent for each Flexie workflow.

Flexie Entity Forms serve as data entry points and workflow triggers within the workforce management context. Mailchimp Signup Forms serve a different purpose (audience capture for marketing). These do not map to each other structurally. We document the Flexie Entity Form field definitions and submission records as part of the schema discovery, but form rebuild is outside migration scope. The customer recreates signup forms in Mailchimp based on the contact fields they wish to capture.

Flexie Documents are files attached to Workers, Shifts, or Venues (such as certifications, onboarding paperwork, or shift schedules). Mailchimp has no document attachment capability on contacts. We extract document metadata (filename, URL, upload date, attached record type) and deliver it as a file inventory. Actual file hosting must be moved separately to a document management system or cloud storage, and links can be preserved as URL merge fields on the contact record if needed.

Flexie Shifts represent time blocks with start time, end time, venue assignment, and capacity. Mailchimp has no scheduling or time-block model. Shift records cannot be represented in Mailchimp's audience structure. We extract shift metadata (shift date, venue, status) as a summary report during discovery and flag it as non-migratable. If the customer needs shift-related communications (reminders, confirmations), we document the Flexie shift trigger logic for rebuild as Mailchimp automations using date-based triggers.