Migrate from Launchpad CRM to Mailchimp

Launchpad CRM Client records map to Mailchimp Contacts within a designated Audience. The client's email address is the dedupe key. First name and last name map to Mailchimp FNAME and LNAME merge fields. Phone number maps to the Phone field if the destination Audience has the phone field enabled. We deduplicate at migration time based on the most recently updated email address because Launchpad CRM's redundant-entry pattern means the same client may appear across multiple module exports.

Launchpad CRM Program records (workforce development, SNAP, TANF, housing, VR) do not have a direct Mailchimp equivalent. We map program enrollment to Mailchimp Tags applied to each Contact record, using the program name as the tag value. Alternatively, if the customer prefers group-based segmentation, we create Groups per program and add enrolled Contacts as Group members. The customer chooses tag strategy during scoping. HUD program codes and eligibility flags cannot be stored as structured data in Mailchimp; we include them as a free-form tag or note field if needed.

Launchpad CRM Case records link a Client to a Program and track service delivery and compliance milestones. Mailchimp has no case object, so case relationships do not map directly. We extract the most recent case status as a tag on the Contact record (e.g., case_status:Active, case_status:Closed). Caseworker assignments become Tags on the Contact record if audit tracking is needed. Compliance and eligibility flags do not migrate because Mailchimp cannot store government-mandated reporting fields.

Individual service encounters logged against a Launchpad CRM Case (assessments, training sessions, job placements) are mapped to Tags on the Contact record in Mailchimp. Service type taxonomy is preserved as tag prefix values. If service records include free-text notes, we include these as Mailchimp Notes on the Contact record for reference, though Mailchimp Notes are not searchable or segmentable.

Caseworker notes and case commentary migrate as Mailchimp Contact Notes. Plain-text notes transfer directly. Structured notes with metadata are flattened to plain text for Mailchimp compatibility. Notes do not appear in Mailchimp segments or automations; they are reference-only for the Contact record.

Launchpad CRM Custom Fields on Client records (eligibility flags, compliance codes, funding sources, program-specific properties) migrate to Mailchimp Audience Merge Fields. We create merge fields of the appropriate type (text, number, date, checkbox) in the destination Audience before import. Fields with no Mailchimp equivalent (multi-select compliance codes, relational data) are stored as text merge fields or documented as excluded data in the migration inventory.

Launchpad CRM Documents attached to Clients or Cases cannot migrate to Mailchimp because Mailchimp does not have a document management or attachment feature. We flag document associations in the migration inventory so the customer's admin knows which documents need to be retained in an alternative storage system (SharePoint, Google Drive, Dropbox) with a reference note in the Contact record.

Launchpad CRM User accounts (caseworkers and staff) do not map to Mailchimp Contacts. If caseworkers need Mailchimp access post-migration, they are provisioned as Mailchimp Users with the appropriate role (Admin, Author, Campaign Manager, Viewer) during Mailchimp account setup, which is outside migration scope. Owner assignments on Contact records become Tags on the Contact in Mailchimp to preserve assignment visibility.