Migrate from Virtual Case Management to Mailchimp

VCM's client record maps directly to a Mailchimp audience member. Every client with a valid email address becomes a Mailchimp subscriber. Clients without email addresses are flagged for manual review — your team decides whether to include them or hold them in a separate VCM export.

The primary email address on a VCM client record maps directly to Mailchimp's EMAIL field, which is the unique identifier for each audience member. Mailchimp enforces email format validation; invalid addresses are flagged and excluded from the import. During the pre-migration data audit, we identify malformed email addresses and provide a report so your team can correct or remove them before the import process begins.

VCM first name and last name fields map to Mailchimp's standard FNAME and LNAME merge fields, which are automatically available in every Mailchimp audience. These power personalization tokens like 'Dear *|FNAME|*' in email templates, allowing you to address recipients by name in your campaigns. If VCM stores names in a single field rather than separate first and last name fields, we split them during the transformation process before loading into Mailchimp.

VCM program enrollment checkboxes or pick-lists (e.g., 'Housing Program', 'Food Bank', 'Youth Services') map to Mailchimp tags applied per enrollment. This preserves the multi-program client scenario — a client enrolled in three programs receives three tags in Mailchimp, enabling segment-based campaigns.

VCM referral source pick-list values (e.g., 'Hospital', 'School', 'Self-Referral', 'Court') map to Mailchimp tags or a custom merge field (REFERRAL_SOURCE). Value-by-value mapping ensures each referral category is represented in Mailchimp's segmentation UI. During planning, your team chooses whether referral sources should be tags (for flexible segment building) or a structured merge field (for reporting dashboards). We document all pick-list values from VCM to ensure no referral category is lost in translation.

VCM phone number fields map to Mailchimp's PHONE merge field, which is available by default. Note that Mailchimp does not use phone numbers for SMS campaigns unless your Mailchimp plan includes mobile optimization and you separately configure SMS opt-in. If you anticipate using SMS outreach in the future, we can flag phone numbers for mobile marketing compliance during the migration, ensuring you're prepared to activate SMS features when your plan allows.

VCM address fields map to Mailchimp's structured ADDRESS merge field, which stores street, city, state, and zip as sub-fields. This enables Mailchimp's postal merge feature for physical mail campaigns if your nonprofit uses that channel. For organizations that send printed newsletters, event invitations, or donation acknowledgments via postal mail, the ADDRESS merge field allows personalized letter generation directly from Mailchimp without manual label creation.

VCM's assigned caseworker field has no native Mailchimp equivalent. We create a CASEWORKER merge field on the Mailchimp audience and populate it with the staff member's name or email. This lets you segment by assigned caseworker if needed for internal coordination emails.

VCM case notes, service entries, and interaction history are narrative records with no Mailchimp equivalent. Mailchimp is not a case management tool. We export these as a separate CSV and document their location; your team manages them in VCM or an alternative system if you maintain both platforms temporarily.

VCM's client intake date maps to a custom INTAKE_DATE merge field in Mailchimp (date type). This preserves enrollment recency for segmentation — useful for welcome series triggers based on how long a client has been in the system. You can create segments for 'clients enrolled in the last 30 days' or 'clients active for over a year,' enabling time-based automation that delivers tailored outreach to different client cohorts based on their tenure with your organization.

VCM stores consent forms, referral letters, and case documents as file attachments. Mailchimp does not have a document repository. We flag attachments for separate export and storage; if documents need to be referenced in emails, they must be hosted externally and linked.

VCM custom fields created for program-specific data (e.g., 'Housing Voucher Status', 'Income Bracket', 'Household Size') map to Mailchimp custom merge fields. Each field requires creation in Mailchimp before import; we deliver a merge field setup plan as part of the migration package.