Migrate from Daylite to Mailchimp

Daylite People records map to Mailchimp Audience members. The email address is the required dedupe key for Mailchimp import. Daylite allows multiple People records with the same email (e.g., family members sharing an inbox), which Mailchimp collapses to a single member with combined properties; we surface a dedup report so the customer decides whether to merge or keep separate records before import. First name, last name, phone, and address fields map to Mailchimp merge fields FNAME, LNAME, PHONE, and the address merge fields respectively.

Daylite custom fields on People (text, date, number, dropdown, checkbox types) map to Mailchimp merge tags created at the audience level before import. We extract the custom field definition table from the Daylite export, present the customer with a merge field creation worksheet, and pre-create merge tags in Mailchimp with the correct type (text, number, date, dropdown) before the member import runs. Dropdown fields from Daylite become dropdown merge tags in Mailchimp.

Daylite Groups containing People members map to Mailchimp Tags. Each Daylite Group becomes a tag of the same name applied to all members of that group. If the customer has Group hierarchies (parent and child groups), the parent group maps to a Mailchimp Tag and the child group maps to a tag with a parent-child naming convention (e.g., 'Region-West' and 'Region-East' under 'Region'). Segments with condition logic (e.g., 'People in Group A with custom field X = Y') are presented as Mailchimp pre-built Segments created during import.

Daylite's separate tag system (distinct from Groups) maps directly to Mailchimp Tags. Tags are additive labels that a single Person can hold multiple of. We extract the Daylite tag assignment table and apply each tag to the corresponding member during import. Tag names are normalized to remove characters Mailchimp does not support (angle brackets, non-UTF-8 characters).

Daylite Notes attached to People migrate as Mailchimp member notes. Note creation date becomes the Mailchimp note timestamp. Note body migrates as plain text (HTML note content is stripped). Mailchimp limits notes to 1,000 characters; notes exceeding this are truncated with a '(truncated)' suffix and the customer is notified of the affected records.

Daylite exports attachments in a flat folder with filenames referencing parent object type and ID. We cross-reference the attachment folder with the People CSV and flag any attachments to People records. Mailchimp does not host file attachments natively on member profiles; we provide a written reference document mapping each attachment to its Daylite-sourced file path so the customer's admin can manually attach or link files in their chosen storage system.

Daylite Company records do not have a direct Mailchimp equivalent because Mailchimp has no native Account or Company object. We map Company name, industry, and website to Mailchimp merge fields (COMPANY, INDUSTRY, COMPANY_WEBSITE) on the member profile. The customer's admin configures these merge fields during scoping if they are not already present in the destination audience. Company-People linkage (a Person belongs to one Company in Daylite) is preserved by ensuring the Company merge field is set for every migrated Person.

Daylite Opportunities (deal pipeline records with stage, value, probability, and close date) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not track deal stages, pipeline values, or sales probability. We flag the Opportunity table in the export as excluded and deliver a written record count so the customer knows the volume of deal data being left behind. If the customer needs deal data in a new system, a separate CRM migration engagement is required.