Migrate from Anyone Home to Mailchimp

Every Anyone Home contact with a valid email address becomes a Mailchimp subscriber in your target audience. Contacts without email addresses are excluded from the migration and flagged in the audit log. Duplicate email addresses (same address associated with multiple Anyone Home records) are surfaced for manual resolution before the full run.

Email address serves as the primary identifier for Mailchimp subscribers, and FlitStack uses each contact's resolved email from Anyone Home as the unique subscriber key during bulk import operations. The communication preferences stored in Anyone Home—including opted-in, unsubscribed, and cleaned statuses—are mapped directly to Mailchimp's subscriber status field to maintain consent compliance across both platforms.

Standard first-name field in Anyone Home maps directly to Mailchimp's built-in FNAME merge tag. If Anyone Home stores first name in a single 'name' field, FlitStack splits on the first space before mapping. Empty or null values pass through as blank merge field values.

The standard last-name field in Anyone Home maps directly to Mailchimp's LNAME merge tag, a required field for subscriber profiles. When Anyone Home stores first and last names together in a single combined field, FlitStack applies the token-splitting approach: it extracts the final token as the last name, handling edge cases where no delimiter exists by using the complete string as the LNAME value.

Phone numbers migrate as a text merge field (PHONE) in Mailchimp. Phone number formatting is preserved as stored in Anyone Home — no reformatting is applied unless a specific normalization rule is documented in the migration plan. Mobile and office numbers are not differentiated in Mailchimp's standard merge field model.

Anyone Home tags (property interest, lead source, prospect status) are mapped to Mailchimp tags. Tag names are normalized to Mailchimp's 85-character limit. Tags with identical names across multiple Anyone Home records are consolidated — each unique tag name becomes a single Mailchimp tag applied to all matching subscribers. Tag categories in Anyone Home do not have a native Mailchimp equivalent and are encoded as prefixed tag names (e.g., 'Source::Organic' becomes a tag with that prefix).

Anyone Home's prospect-to-property association has no direct Mailchimp equivalent. FlitStack creates a custom text merge field (PROPERTY) to store the associated property name or ID. If the team prefers a tag-based model, the property association is applied as a tag prefixed with 'Property:' for segmentation. The choice between merge field and tag is confirmed during the planning phase.

Anyone Home lead-source attribution (e.g., 'Organic Search', 'Referral', 'Walk-in') migrates as a custom merge field (LEADSOURCE) or as a tag depending on segmentation needs. Mailchimp's built-in SOURCE merge tag is reserved for import-source tracking and should not be confused with business-level lead attribution — a custom field avoids this collision.

Anyone Home prospect lifecycle stages (Tour Scheduled, Application Started, Lease Signed, etc.) have no native Mailchimp equivalent. FlitStack creates a custom pick-list merge field (LEASESTAGE) with values mapped directly from Anyone Home. Alternatively, stages can drive Mailchimp segment criteria — this is evaluated per migration based on segment count and complexity.

Lease timeline data from Anyone Home migrates as custom date merge fields in Mailchimp. These fields are useful for segmentation (e.g., 'lease expiring within 60 days') but require your Mailchimp plan to support date merge fields. Standard Mailchimp plans include date merge fields; the free plan does not.

Original create and last-modified timestamps from Anyone Home are preserved as custom datetime merge fields. These are not native Mailchimp system fields — Mailchimp's SUBSCRIBED_TIME reflects the import timestamp, not the source-system creation date. Custom datetime fields allow reporting on source-system age without data loss.

Anyone Home communication activities (call logs, email threads, note history) have no migratable equivalent in Mailchimp's subscriber model. Mailchimp tracks campaign engagement (opens, clicks) per subscriber but does not store historical activity records. FlitStack exports activity history as a supplementary CSV for manual reference or import into a separate note-tracking system.

Anyone Home property records (address, unit count, amenities, rent schedules) have no Mailchimp equivalent. Mailchimp is an email platform, not a property management system. Property data remains in Anyone Home and can be referenced by property name or ID stored on the contact record via the PROPERTY merge field described above.

Anyone Home leasing workflows (tour-follow-up sequences, renewal reminders, rent-default triggers) are not migratable to Mailchimp Customer Journeys. The automation logic, triggers, and action sequences are exported as a structured JSON document that your Mailchimp admin can use as a specification for rebuilding. This export is included in every migration deliverable.

Files attached to Anyone Home contacts or properties (lease documents, ID scans, correspondence attachments) cannot migrate to Mailchimp's subscriber model. Mailchimp attachments refer to files attached to campaigns, not to subscriber records. Attachments are excluded from the migration and documented in the audit log for manual retrieval from Anyone Home before decommissioning.