Migrate from ArkCase to Mailchimp

ArkCase Person records map directly to Mailchimp contacts. The Person's first name, last name, and email address become Mailchimp's FNAME, LNAME, and EMAIL merge fields. Mobile phone maps to PHONE if present. Organization affiliation is preserved as a tag or merge field rather than a linked object.

The primary email address on an ArkCase Person record becomes the Mailchimp contact's email address, which serves as the unique identifier for the audience member. Secondary emails on ArkCase persons are preserved as a custom merge field. During migration, the primary email serves as the unique key; duplicate email entries in ArkCase are flagged for review. Additional email addresses are stored as custom merge fields (e.g., EMAIL_2).

ArkCase stores first name and last name as separate Person properties. Both map directly to Mailchimp's standard FNAME and LNAME merge fields. Full-name concatenation is avoided; Mailchimp templates reference FNAME and LNAME separately. If a Person record contains only a single FULL_NAME field without split components, FlitStack AI attempts to parse the name into first and last parts, applying a fallback to the FULL_NAME merge field when parsing is ambiguous.

ArkCase Person phone number maps to Mailchimp's PHONE merge field. Phone numbers are normalized to E.164 format during migration where ArkCase stores country codes; otherwise, a custom merge field is created for extended phone data. If a Person has multiple phone numbers (mobile, work, home), the primary number populates PHONE while others are stored in additional custom merge fields such as PHONE_MOBILE or PHONE_WORK.

ArkCase Organizations are not Mailchimp native objects. We create a merge field (ORGANIZATION_NAME) on the Mailchimp contact and tag each contact with the organization name. If you maintain multiple organizations per Person (N:N in ArkCase), all affiliations are captured as comma-separated tags.

ArkCase Organization addresses map to Mailchimp's compound ADDRESS merge field (ADDR1, ADDR2, CITY, STATE, ZIP, COUNTRY). Primary organization address is used; secondary addresses are preserved as a custom merge field. When an Organization has multiple locations, each additional address is stored as a custom merge field (e.g., ADDRESS_2) with the same component breakdown, ensuring you can reference each physical office in your campaigns.

ArkCase Cases have no Mailchimp equivalent. We preserve the most recent case number, case status, and case type as merge fields (RECENT_CASE_NUMBER, CASE_STATUS) and apply a tag (HAS_OPEN_CASE) when a Person is associated with an open case. Historical case associations are not migrated to avoid audience bloat.

ArkCase Complaints are compliance records. We map complaint status (Open, Closed, Pending) as a tag on the associated Person contact and preserve the most recent complaint reference number in a COMPLAINT_REF merge field. Full complaint history is not migrated to Mailchimp's flat contact model.

ArkCase custom fields on Person records — such as Preferred Contact Method, Source Channel, or Custom Dropdown — are created as Mailchimp merge fields. Pick-list values in ArkCase are mapped value-by-value to Mailchimp merge-field dropdown options during the migration. If a custom field contains a list of permissible values, FlitStack AI replicates the same options in Mailchimp's dropdown configuration; any new values added after migration are added manually in Mailchimp.

ArkCase Tasks have no Mailchimp equivalent. We surface the Person's most recent task status (Open Tasks count) as a numeric merge field (OPEN_TASKS_COUNT) and tag contacts with task priority levels for segmentation. Full task history is not migrated. If a Person has no open tasks, the OPEN_TASKS_COUNT field is set to zero, and the contact receives a NO_OPEN_TASKS tag for straightforward filtering.

ArkCase documents and file attachments have no Mailchimp equivalent. These are not migrated. We provide a file inventory export so you can document which documents are associated with which Person records for compliance purposes. The file inventory CSV lists each document's ArkCase ID, associated Person ID, file name, and last modified date, allowing your compliance team to maintain a linkage even though the files themselves remain in ArkCase.

ArkCase BPMN 2.0 workflows have no Mailchimp automation equivalent. Mailchimp's automation builder uses a different trigger-action model. We export workflow definitions as a JSON reference for your team to rebuild in Mailchimp Customer Journeys. The JSON export captures each step’s name, condition, assignee, and timeout, providing a blueprint that your Mailchimp team can translate into Customer Journey blocks. This reference does not include execution history or variable data.