Migrate from KulaHub to Mailchimp

KulaHub Contacts map 1:1 to Mailchimp Members within an Audience. We extract the full contact record including email address, first name, last name, phone number, and any standard KulaHub contact properties. GDPR unsubscribe flags from KulaHub migrate as Mailchimp non-subscribed Members (HasOptedOutOfEmail = true) to honor existing consent states. KulaHub's UK-based contact fields (address, county) map to Mailchimp merge fields ADDRESS and CITY. Duplicate detection uses email address as the primary key; Mailchimp's batch upsert with skip_if_exists prevents re-creation of existing Members.

KulaHub email campaigns and templates migrate to Mailchimp Campaigns. Subject line, preview text, HTML body, and plain-text version transfer directly. Open and click tracking data migrates as engagement metrics on each Member where KulaHub's export includes these fields. Campaign tags migrate as Mailchimp Tags on each recipient Member. KulaHub campaign-level GDPR unsubscribe data migrates to Mailchimp suppression lists so existing unsubscribes are not contacted in Mailchimp after migration.

KulaHub stores email unsubscribe state and GDPR preference flags per contact but does not publish the field schema or data format used. We export any preference-related fields from the contact record during discovery and configure Mailchimp merge fields (GDPR_CONSENT, EMAIL_PREFERENCE) to carry these values. Unsubscribe records are exported as non-subscribed Members in a suppression-audience so Mailchimp respects existing consent before any campaign sends. Customer confirmation of the preference-field mapping is required before production migration.

KulaHub notes attached to contacts migrate as Mailchimp Notes on each Member. Each Note carries the original KulaHub note body, creation timestamp, and—if KulaHub exposes author attribution—the author name. Mailchimp Notes are limited to 1,000 characters per note; KulaHub notes exceeding this threshold are truncated with a notation that the full content is preserved in the migration staging table.

KulaHub contact tags migrate as Mailchimp Tags on each Member. Tags preserve the original KulaHub label without transformation so that segmentation logic built around tags in KulaHub maps directly to Mailchimp Tag-based segments. Tags with high cardinality (more than 500 distinct values) are flagged for a mapping review during scoping to ensure the Mailchimp audience is segmented efficiently.

Documents attached to KulaHub contacts are extracted as binary blobs and re-associated with the corresponding Mailchimp Member record where Mailchimp supports attachment metadata. Mailchimp does not provide native CRM document storage; we stage the extracted document blobs with the corresponding Member email address so the customer's admin can re-associate them via Mailchimp integrations (e.g., linking to Google Drive or Dropbox) or a third-party document management integration after migration.

KulaHub tasks assigned to contacts with due dates, descriptions, and owner assignments have no direct Mailchimp equivalent. Mailchimp does not provide a native task management or reminder object. We deliver a written inventory of all active and historical KulaHub tasks with contact name, due date, owner, and status so the customer's admin can recreate them in their preferred task management tool or in Mailchimp automation sequences if applicable.

KulaHub form submissions linked to contacts (website enquiry forms) export as key-value pair records keyed to the contact email address. Mailchimp does not accept form submission data as a native import object. We stage form-submission data in a CSV with the corresponding contact email as the merge key, and we deliver a written form-field inventory showing which KulaHub fields map to Mailchimp merge fields or tags. The customer's admin rebuilds the equivalent Mailchimp signup forms post-migration.

KulaHub reports including All Contacts, CRM activity reports, and system event logs export as data extracts but do not have Mailchimp equivalents. Mailchimp analytics (open rates, click rates, audience growth, revenue tracking) are rebuilt on the Mailchimp platform using imported contact and campaign data. We deliver a written inventory of all KulaHub report types, column headers, and last-run data so the customer's admin has a reference point for rebuilding equivalent reports in Mailchimp.

KulaHub internal users appear in activity logs and task assignments. We export the full KulaHub user list and resolve them against the Mailchimp destination audience. Users who are also email subscribers are added as Members with a tag (e.g., Kulahub_User) identifying their original role. Non-subscriber users are noted in the migration handoff document for the customer's admin to provision access in Mailchimp's account settings if needed.