Migrate from Entera to Mailchimp

Entera contact records map to Mailchimp subscribers within a single audience. Every Entera contact field (name, email, phone, company) maps to the equivalent Mailchimp subscriber field. Duplicate email addresses are resolved using Mailchimp's hash-based upsert so existing subscribers update rather than re-create.

Entera custom contact properties (investor_type, acquisition_budget, preferred_market) are created as Mailchimp merge fields before migration. Field types (text, number, date, phone) map to Mailchimp's available merge field types. Each property requires a separate Mailchimp field definition — large custom property counts increase setup time proportionally.

Entera company records do not map to a native Mailchimp object because Mailchimp has no company or account entity. We merge company name and domain into contact-level merge fields on each subscriber so the affiliation is preserved at the individual record level.

Entera deal records (deal name, amount, stage, close date, associated contacts) have no native Mailchimp equivalent. Mailchimp's audience model does not support deal pipelines or opportunity stages. Deals associated with a contact are surfaced as a text merge field (DEAL_REFERENCE) containing deal name, amount, and stage as a concatenated reference string.

Entera property records (address, acquisition price, rental income, property type) have no native Mailchimp counterpart. We extract the primary property associated with each contact and write a reference string to a PROPERTY_REFERENCE merge field. Multiple properties per contact are appended as comma-separated values.

Entera deal pipeline stages (e.g., Under Review, Due Diligence, Closed Won) can be applied as Mailchimp tags on the associated contact. Tags preserve the deal's current stage as a Mailchimp label. Stage history is not preserved — only the final stage value transfers as a tag.

Entera contact notes and activity records map to Mailchimp notes on each subscriber. The original note text, timestamp, and the creating user are preserved in the Mailchimp note. If a contact has multiple notes, each appears as a separate entry. Notes exceeding Mailchimp's 1,000‑character limit are truncated, and the remainder is stored in a custom field for completeness.

Entera file attachments associated with contacts or deals have no native Mailchimp storage mechanism. We export the file list and URLs and provide a reference manifest so your team can re-host files on a document storage platform and link to them from Mailchimp notes.

Entera user records assigned as record owners have no direct Mailchimp counterpart, because Mailchimp lacks a per‑record owner model and treats the audience as a shared workspace. We retain owner attribution by writing the owner's email address to a custom field (ORIGINAL_OWNER) on each subscriber. This allows your team to identify the original responsible user in Entera, though Mailchimp will not enforce assignments or route tasks to that owner.

Entera automations tied to deal stages and property events do not transfer. They require manual rebuild in Mailchimp Customer Journeys. FlitStack exports the automation logic as a JSON specification your team can use as a reference when designing Mailchimp journeys.