Migrate from Digital Signup to Mailchimp

Digital Signup's primary registrant contact record maps directly to a Mailchimp subscriber. All standard contact fields (name, email, phone, address) migrate as native Mailchimp fields or merge fields. This is the base unit of the migration — every other object attaches to a contact record.

Digital Signup stores family members as a hierarchical group — a single family may have a parent, multiple guardians, and several children on one enrollment. Mailchimp has no family hierarchy concept. Each individual becomes a separate Mailchimp contact. A Family_ID__c custom field links members together, and tags by family name enable segmentation without rebuilding the group structure.

A Digital Signup program enrollment links a registrant to a program with start/end dates, instructor name, enrollment status, and waitlist position. Mailchimp has no enrollment object. We create an audience tag per program name for segment filtering, and map enrollment start date, instructor, and status as individual merge fields (e.g., Program_Start_Date__c, Instructor_Name__c, Enrollment_Status__c).

Digital Signup stores emergency contact name and phone on the registrant record. Mailchimp has no native emergency contact structure. We create two text merge fields — Emergency_Contact_Name__c and Emergency_Contact_Phone__c — to preserve this information. This is critical for childcare and school programs where emergency contact data is a regulatory or parental expectation.

Digital Signup records waiver name, acceptance timestamp, and waiver document reference for each registrant. The waiver document itself (containing PHI or signature data) is excluded for HIPAA and PCI-DSS compliance. We map Waiver_Name__c and Waiver_Accepted_Date__c as merge fields. Waiver_Accepted__c stores a yes/no value. Any waiver document URL or content is stripped before import.

Digital Signup records payment amount, method, transaction ID, and billing address for each registration. Mailchimp has no payment or transaction object. These records cannot migrate. FlitStack flags all payment-related fields during the planning phase so organizations can exclude them before import — storing PCI data in an email marketing platform creates compliance exposure.

Digital Signup's Facility module stores facility name, address, and room assignment for each program location. Mailchimp has no facility object. We create a facility tag per unique location (e.g., 'Facility: Community Center Main Hall') and map address and room as merge fields on the contact or as a separate Facility_Name__c and Room__c field. Tagging by facility enables targeted campaigns — e.g., send reminders only to families registered at a specific location.

Digital Signup stores instructor name, email, and credentials per class. Mailchimp stores instructors as tagged contacts if they are also in the audience, or as a separate instructor roster tag list that can be referenced in segments. Instructor tags (e.g., 'Instructor: Smith') allow segmenting contacts by instructor for class-specific announcements.

Digital Signup allows user-defined discount levels applied per registration — Veteran, Senior, Resident, or custom-defined. Mailchimp has no native discount concept. We create a Discount_Level__c pick-list merge field and map Digital Signup values one-to-one. This preserves pricing-tier context for programs that run differentiated fee structures.

Digital Signup tracks waitlist position and waitlist enrollment date for contacts who registered but did not get a confirmed class slot. Mailchimp has no native waitlist concept. We create Waitlist_Position__c (integer) and Waitlist_Date__c (date) merge fields. A 'On Waitlist' tag enables a segment for waitlist-specific outreach when a spot opens — e.g., a 'Waitlist Open' automation that triggers when enrollment drops below capacity.

Digital Signup records the exact timestamp of each registration. Mailchimp's native timestamps (MEMBER_SINCE, CREATE_TIME) reflect when the contact entered Mailchimp, not when they registered in Digital Signup. We preserve the original signup date as a custom datetime merge field so organizations can analyze enrollment timing patterns, identify legacy vs. new registrants, and build segments based on registration recency.

Digital Signup's E-Store module supports gift card purchases linked to a registrant's account. Mailchimp has no gift card or purchase ledger object. Gift card purchase records cannot migrate. If gift card recipients are added as new subscribers to the Mailchimp audience, they can be tagged as 'Gift Card Recipient' manually or via API.