Migrate from Inmovilla to Mailchimp

Property data has no native home in Mailchimp

Inmovilla's core object is the property listing — every contact, lead, and activity is anchored to a property or portfolio. Mailchimp has no Property or Listing object. Property references, listing status, and real estate portal sync data must be converted to custom fields on the subscriber record. This means a contact's full property context becomes a set of custom field values rather than a relational object graph. Teams should plan which property attributes are critical for segmentation (budget range, property type, listing status) and prioritize those as custom fields before migration. Property photos and documents do not migrate at all — Inmovilla's document attachments have no Mailchimp equivalent.

Mailchimp contact-based billing vs. Inmovilla's agency-based model

Inmovilla bills per agency instance with user-seat pricing. Mailchimp bills per subscriber per audience — contacts who appear in multiple audiences are counted multiple times. For real estate agencies with large client databases and separate audiences for different property types or regions, Mailchimp's billing model can significantly increase costs compared to Inmovilla's flat agency fee. We flag any Inmovilla contacts that would be imported into multiple Mailchimp audiences so your team can decide whether to consolidate audiences before migration or accept the multi-count billing.

Workflows and automation sequences do not transfer

Inmovilla's lead distribution rules, follow-up sequences, and portal auto-sync workflows are built on Inmovilla's event model and cannot be exported in a format compatible with Mailchimp Customer Journeys. The trigger-and-action architecture is fundamentally different. We export your Inmovilla workflow definitions as a structured reference document listing each workflow's triggers, conditions, and actions. Your Mailchimp team then rebuilds these as Customer Journeys. Any workflows that depend on Inmovilla's property status changes (e.g., 'notify client when property status changes to Reservado') require custom trigger logic in Mailchimp.

Tags lack hierarchy — Inmovilla segments may not map cleanly

Inmovilla supports hierarchical segment definitions (nested conditions by lead source, property interest, and team assignment). Mailchimp tags are flat — no nesting, no AND/OR group logic within a single tag. Inmovilla segments that combine multiple conditions need to be rebuilt as Mailchimp saved segments or as pre-configured tag bundles. We document the original segment logic before migration so your team can test equivalent Mailchimp segment definitions. Some Inmovilla segments that rely on property attributes may require custom field setup before the equivalent segment can be created.

Activity history reconstruction requires tagging strategy

Inmovilla stores detailed activity records (call duration, email subject, meeting attendees, note body) with original timestamps and owner attribution. Mailchimp has no native activity log for sales-style engagement. We reconstruct activity history using a combination of subscriber notes (for note body and call summaries) and tags prefixed by activity type. However, this is a one-directional record — Mailchimp will not surface activity history in the same timeline view that Inmovilla agents are accustomed to. Tags provide filtering capability but not a full activity feed per subscriber.