Migrate from Flowlu to Mailchimp

Flowlu Contact records map directly to Mailchimp subscribers within a target Audience. Email address serves as the primary dedupe key. We flag contacts missing a required email field before import because Mailchimp silently skips subscribers without email during CSV upload. First name, last name, phone number, and address fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). Any Flowlu custom fields on Contact with text, number, date, or dropdown types map to Mailchimp merge fields with equivalent types; multi-select or checkbox fields map to Mailchimp tags instead.

Flowlu Companies store organization-level data (name, industry, website, address) that Mailchimp does not represent as a separate record. We resolve the Company linked to each Contact via Flowlu's company association, then store the company name as a MERGE6 or similar merge field on the Contact's subscriber record. Industry maps to a text merge field. This approach preserves the organizational context without creating orphaned Company records in Mailchimp, which has no equivalent object.

Flowlu's Contact Category (a dropdown or multi-select property indicating segment assignment such as Client, Partner, Lead, Vendor) maps to Mailchimp Tags. Each distinct category value becomes a Tag in the destination Audience, and contacts carrying that category receive the corresponding tag. Multi-category contacts receive multiple tags. We extract the full distinct category value set during scoping and confirm the tag names with the customer before migration runs.

Flowlu contacts with an unsubscribed or bounced status must not be re-imported into an active Mailchimp audience because doing so damages sender reputation and deliverability. We extract the full suppression list (contacts with opt-out, unsubscribe, or bounce flags) from Flowlu and import them as a suppression list in Mailchimp before the active subscriber import begins. This step follows Mailchimp's recommended pre-migration workflow for responsible list transfer.

Flowlu Custom Fields on Contacts with type text, number, or date map to Mailchimp merge fields of the corresponding type (text, number, date). Custom fields of type dropdown or list map to Mailchimp tags using the selected value. Checkbox fields map to binary tags (field name as tag name, value as tag value). We extract the full custom field schema per object during scoping and flag any fields with types that Mailchimp cannot represent natively, such as nested structures or multi-reference lookups.

Flowlu contacts may carry lifecycle stage, status, or assigned owner fields that indicate segmentation intent. We map these to Mailchimp tags (for categorical values) or text merge fields (for descriptive values) depending on the field cardinality. Owner assignment from Flowlu maps to an OWNER or ASSIGNED_TO merge field on the Mailchimp subscriber record if the customer wants sales-rep attribution visible within Mailchimp.

Flowlu's workflow automation builder can trigger on contact creation or update events. These automations have no direct equivalent in Mailchimp's customer journey model and do not migrate as code. We document every active contact-triggered Flowlu workflow during scoping and deliver a written mapping to Mailchimp Customer Journey triggers and conditions, so the customer's marketing team can rebuild the logic post-migration.

Mailchimp does not have data model equivalents for Flowlu Pipelines, Stages, Opportunities, Projects, Tasks, Invoices, or Knowledge Base articles. These records are out of scope for this migration. We deliver a written record count by object type during scoping so the customer understands what will not transfer and can plan for manual export or archival if needed.