Migrate from Notifi to Mailchimp

Notifi contact records map 1:1 to Mailchimp audience members. Each contact becomes one subscriber entry in the target audience. Email address is the unique identifier — contacts without a valid email are flagged as non-importable before migration. This ensures a clean, email-verified audience from day one.

Notifi standard fields — first name, last name, phone number, email address — map to Mailchimp's built-in merge fields (FNAME, LNAME, PHONE, EMAIL). These are created automatically when the Mailchimp audience is provisioned. They require no manual setup and are ready for immediate data mapping.

Notifi custom properties migrate as Mailchimp custom merge tags. We create each merge tag in Mailchimp under Settings > Audience fields and *|MERGE|* tags with the matching data type (text, number, date, dropdown). Tag names are normalized to uppercase Mailchimp format.

Notifi company names migrate as a custom merge tag (COMPANY) in Mailchimp, preserving the business name for personalization. If multiple contacts share a company, the COMPANY tag repeats per contact — no separate company object exists in Mailchimp. This approach keeps all contact data within a single audience record.

Notifi tags and labels attached to contacts (e.g., 'High-Value', 'Referral', 'Job-Complete') migrate as Mailchimp tags. Tags are applied per-contact and can drive segmentation after migration. Duplicate tag names are de-duplicated in Mailchimp. This allows targeted campaigns based on customer attributes without duplicating tag logic across the audience.

Notifi's active/inactive contact flag maps to Mailchimp's member status: 'subscribed', 'unsubscribed', or 'cleaned'. Contacts flagged as inactive in Notifi are set to 'unsubscribed' in Mailchimp to honor suppression rules. This ensures that suppressed contacts do not receive future email campaigns, protecting deliverability and sender reputation.

Notifi logs every VoIP call, SMS message, and email as an activity record. Mailchimp has no activity log per subscriber beyond email engagement metrics (opens, clicks). Communication history is preserved in a FlitStack audit export CSV — it cannot be loaded into Mailchimp's data model.

Notifi's job records, scheduling data, technician assignments, and job statuses have no Mailchimp equivalent. Job status tags (e.g., 'Scheduled', 'In Progress', 'Completed') can migrate as Mailchimp tags for segmentation, but the full job record is exported as a separate CSV for reference.

Notifi estimates, invoices, and payment records are standalone financial objects. Mailchimp does not store billing or financial data. These records are exported as a structured CSV with original timestamps and line items — they must be archived or imported into a dedicated accounting tool.

Notifi team members (technicians, dispatchers) are assigned as owners to contacts and jobs. Mailchimp has no per-contact owner field — ownership is account-level. We surface owner assignments as a custom merge tag (ORIGINAL_OWNER) so attribution is preserved for reference. This allows you to trace back original responsibility for each contact.