Migrate from Striven to Mailchimp

Striven Customer records map to Mailchimp Audience Members by email address as the dedupe key. Each Striven Customer with a populated email address becomes one Mailchimp contact record. Customers without an email address cannot migrate and are flagged in the reconciliation report. Primary contact fields (first name, last name, email, phone) map directly to Mailchimp merge fields FNAME, LNAME, EMAIL, and PHONE.

Striven global-level and type-level custom fields on Customers map to Mailchimp merge fields within the target audience. We audit the full custom field schema during discovery to identify each field's scope (global versus type-level) and map it to the appropriate Mailchimp audience merge field. Type-level fields scoped to specific customer subtypes are mapped only for records of that subtype. Merge field type (text, number, date, phone, address) is chosen to match the Striven field data type.

Striven stores email opt-in status on Customer records (via the email address field and any marketing consent field if configured). We extract this and map it to Mailchimp's subscriber status: subscribed contacts import as subscribed, contacts with explicit unsubscribes import as unsubscribed, and contacts with hard bounces are excluded from import and added to a suppression list. Pending double opt-in states are noted for manual follow-up post-migration.

If the customer has used Striven's tagging or segmentation features to label customer records (for example, customer tier, industry, or account type), we map these as Mailchimp tags. Tags transfer as flat string labels rather than as structured taxonomy; the customer's marketing team reorganizes them into Mailchimp's tag groups or customer segments post-import if needed.

Striven Customer billing and shipping addresses map to Mailchimp's ADDRESS merge field group. If both billing and shipping addresses exist on a Customer, the primary billing address is used as the default; shipping address is noted in a custom merge field for operations teams to use in Mailchimp integrations or abandoned cart automations.

Striven Customer Portal association (whether a customer has portal access) has no direct Mailchimp equivalent. We map this to a Mailchimp tag (has_portal_access) or a binary merge field so the marketing team can segment portal users separately if needed. The portal itself does not migrate.

Striven Customer-level notes migrate as Mailchimp Customer Notes attached to the contact record. Notes with timestamps preserve the original creation date. Long-form notes exceeding Mailchimp's note field length are truncated with a reference to the original record in the migration audit log.

Striven Vendor records have no Mailchimp equivalent. Vendor contacts used for supplier communications are outside Mailchimp's contact model. We exclude Vendors from the migration scope and note them in the audit report.

Striven financial records (Invoices, Bills, Sales Orders, Purchase Orders, Chart of Accounts, Items) have no Mailchimp equivalent. Mailchimp is a marketing platform and does not store transactional or financial data. These records are explicitly excluded from migration scope and noted in the scope document for the customer's financial records team.

Striven Projects, Tasks, and Employee records are internal operational data with no Mailchimp equivalent. Employee records (required for Striven accounting migration prerequisites) are excluded from Mailchimp migration scope. Projects and Tasks do not map to Mailchimp's campaign or audience model.