Migrate from HomeSpotter Spacio to Mailchimp

Every Spacio guest sign-in becomes one Mailchimp Contact. Email address is the unique identifier — guests without an email address cannot be created as Mailchimp contacts and are flagged for manual review. First name, last name, phone, and address map to Mailchimp's standard merge fields FNAME, LNAME, PHONE, and ADDRESS respectively.

Spacio Properties carry title, price, beds, baths, address, MLS number, and listing agent email. The property address becomes a merge field (PROPADDR) on the Contact. The property title and price can be stored as merge fields or as a tag (e.g., TAG: 'Listings-$2.5M-2BR'). The MLS number becomes a custom merge field (MLS_NUM) for reference.

Spacio Open House Events have a date, property association, and agent. The event date maps to a merge field (EVENT_DATE). The event itself is preserved as a tag on each guest (e.g., TAG: 'OH-2024-06-15-231-Beach-Ave'). Mailchimp has no native event concept — event context must be reconstructed through tagging and merge fields.

Each Spacio check-in question (buyer type, financing, agent contact preference) becomes a Mailchimp merge field. Text responses become TEXT merge fields. Pick-list answers require value_mapping per answer option. Boolean questions (yes/no) become merge fields with 'Y'/'N' or 1/0 string values. FlitStack creates merge fields in Mailchimp before the import run.

The Spacio agent who hosted the open house is identified by email from the property endpoint. Their email becomes a merge field (AGENT_EMAIL) on each guest contact. The agent name can also be stored as a tag (e.g., TAG: 'Agent-John-Smith') for segmentation. Owner resolution is by exact email match.

Mailchimp does not have a native 'record created' timestamp field separate from opt-in time. FlitStack preserves the original Spacio capture timestamp as a custom merge field (SPACIO_CAPTURE_DATE) in ISO 8601 format for reporting continuity. The Mailchimp opt-in timestamp will reflect the migration import date.

Spacio sends one automated email to each guest after the open house closes. This is a platform workflow — it does not export. FlitStack documents the Spacio follow-up email content and trigger logic so your team can rebuild it as a Mailchimp Customer Journey with the same timing and content structure. No data migrates here; the specification document is the deliverable.

Spacio gathers social profile URLs (LinkedIn, Facebook, etc.) on verified contacts as a data-enrichment layer. Mailchimp has no native social profile field. FlitStack can store social profile URLs as a merge field (SOCIAL_PROFILES) in JSON format for reference, but this is informational only — Mailchimp does not use social data for segmentation or personalization natively.

Spacio generates branded seller reports with attendee count, lead quality, and follow-up status. Mailchimp has no report format equivalent. These reports must be rebuilt manually in Mailchimp using campaign performance data and exported contact lists. FlitStack provides a report-field mapping guide to help your team reconstruct the seller report logic in Mailchimp.

The MLS number, property price, beds, baths, and address from the Spacio Property endpoint migrate as direct merge fields (MLS_NUM, PRICE, BEDS, BATHS, ADDRESS). These values are preserved exactly as strings from the API response. The property listing URL is also preserved as a merge field (LISTING_URL) for use in email copy, and property type maps to a PROPERTY_TYPE merge field to support segmentation by residential category.

Spacio records the source URL where a guest submitted their sign-in (web form vs. kiosk). This is preserved as a merge field (SPACIO_SOURCE_URL) for analytics on which channel drove attendance. Mailchimp does not track referral URLs natively for imported contacts.