Migrate from Genoo to Mailchimp

Genoo Leads map directly to Mailchimp Audience members. All standard fields (email address, first name, last name, phone, company, lead source, subscription status) migrate to Mailchimp profile properties and Merge Fields. We use email address as the primary dedupe key during import. Unsubscribed and bounced Lead statuses migrate to Mailchimp's suppressed member state. Genoo's manual export UI does not include a standard column for unsubscribe timestamp; we extract this from the export header where available or set the member to subscribed by default and deliver a separate suppression list CSV for import before first send.

Genoo Contacts and Leads often share the same email address when lists are deduplicated upstream. We merge Contact and Lead records during the transform phase by email address, pulling the superset of available fields (name, phone, company, source, any custom properties) into a single Mailchimp Audience member profile. We flag any Contact records with a different email address than a matched Lead as a separate Audience member. Source attribution (landing page, form, imported list) migrates as a Merge Field rather than a native segment tag.

Genoo Accounts carry company name, website, industry, and phone. We map Account.company_name to the Mailchimp COMPANY Merge Field on the Audience member. Industry maps to a custom Merge Field (INDUSTRY) configured in the Audience before import. Website has no direct Mailchimp profile field; we map it to a custom Merge Field (WEBSITE). Because Mailchimp has no standalone Account or Company object, Account-level associations (multiple Contacts at the same company) are not preserved as separate records; instead we tag members by company name using Mailchimp Tags for grouping.

Genoo Campaigns (drip nurture programs with associated program steps and enrollment criteria) map to Mailchimp Automations. We extract the Campaign name, enrollment trigger logic, step sequence, delay between steps, and email template content from Genoo's UI. Because Genoo does not expose Campaign configuration via API, we document this manually during discovery and deliver a written Automation Rebuild Guide that maps each Genoo drip step to a Mailchimp Automation canvas step, including trigger conditions, time delays, and subject line. The customer or their Mailchimp admin rebuilds the automation in Mailchimp's visual builder using the guide; we do not generate Mailchimp automation code as part of standard migration scope.

Genoo Campaign membership (which Leads entered which Campaign and when) migrates to Mailchimp as Audience Tags plus a custom Merge Field (GENOO_CAMPAIGN) carrying the Campaign name, and a date Merge Field (GENOO_ENROLLMENT_DATE) carrying the enrollment timestamp. If the customer rebuilds the automation in Mailchimp, they can use the Tag as a re-enrollment trigger so that members who were in a specific Genoo Campaign re-enter the equivalent Mailchimp Automation without manual re-import.

Genoo landing pages and microsites are stored as HTML and template blobs with associated form configurations. Mailchimp has a separate Landing Page product but it is a distinct tool from the core email marketing platform and landing pages do not transfer between vendors. We extract the page content and form field definitions as structured text where available, but note that full page rendering assets do not map to Mailchimp. We deliver a landing page manifest listing every Genoo landing page URL, form field configuration, and traffic source so the customer's marketing team can recreate pages using Mailchimp Landing Pages, a CMS, or a dedicated landing page tool post-migration.

Genoo email templates are HTML-based. We extract the template body, subject line, and inline CSS styling. Modern email builders use block-based composition that does not map cleanly to raw HTML; we present the extracted HTML as a Content document in Mailchimp's Saved Content library so the customer's team can reference design elements when rebuilding in Mailchimp's drag-and-drop editor. Template-level variables (personalization tokens) are mapped to Mailchimp Merge Tags in the extraction notes.

Genoo lead scores are calculated values generated by the platform's scoring engine using behavioral and demographic weights defined within Genoo. These scores are displayed in the Genoo UI but are not exported as discrete data points. Mailchimp does not have a native lead scoring engine; customers typically implement scoring using third-party tools (e.g., Nutshell, SharpSpring) or Mailchimp integrations. We do not migrate lead scores. During discovery we document the Genoo scoring configuration (weighting rules, thresholds, and the fields that drive scores) and deliver it as a Scoring Reconstruction Guide for the customer's admin to implement in their chosen scoring tool.

Event registrations in Genoo are stored as activity records linked to Leads. We import registration data (event name, event date, registration status, attendance status) as custom Merge Fields on the corresponding Mailchimp Audience member (EVENT_NAME, EVENT_DATE, REG_STATUS, ATTENDED). Multiple event registrations for the same contact create multiple Merge Field values; we concatenate event names into a single EVENT_HISTORY text field. Post-event data (attendance, no-show) migrates as a separate Merge Field update after the registration import. Mailchimp does not have a native events object; if event tracking is critical, customers should use a dedicated event management integration (Eventbrite native to Mailchimp) post-migration.