Migrate from Bloomr to Mailchimp

Bloomr Contact records map to Mailchimp Members. The Bloomr contact email address is the primary identifier and serves as the subscriber hash for Mailchimp's upsert API (MD5 hash of lowercase email). We preserve the Bloomr contact's full name in the FNAME and LNAME merge fields, phone in the PHONE merge field, and any additional custom field values in their corresponding Mailchimp merge fields. Status mapping: Bloomr Active maps to subscribed, Bloomr inactive or unsubscribed maps to the appropriate Mailchimp Member status. We run a deduplication pass before insert using email as the unique key.

Bloomr's Companies/Accounts object has no direct Mailchimp equivalent. Company name maps to a COMPANY merge field if present in the destination audience schema. Company domain, industry, and size map to Mailchimp Tags with labels like Company:AcmeCorp, Industry:Technology, CompanySize:51-200. We recommend tagging over merge fields for company data because tags support multi-value assignment (a contact can belong to one company) and are easier to query for segmentation in Mailchimp's audience view.

Bloomr Deals have no Mailchimp equivalent. Mailchimp does not offer a pipeline, opportunity, or deal stage object. We flag this as a structural gap during scoping. For teams that require deal value tracking, we document every Bloomr Deal with its name, value, stage, and expected close date as a CSV export for the customer's admin to evaluate alternatives: a dedicated CRM rebuild in Mailchimp-compatible tools like Pipedrive or HubSpot, or a Google Sheets integration maintained alongside Mailchimp.

Bloomr custom fields discovered during API profiling map to Mailchimp merge fields in the destination audience. Mailchimp merge field names must be uppercase alphanumeric with underscores (FNAME, LNAME, COMPANY). We transform Bloomr's camelCase or space-separated custom field names to Mailchimp's naming convention during the transform step. Note: Mailchimp text merge fields are limited to 255 characters. Any Bloomr text custom field exceeding 255 characters must be truncated with a truncation flag set in the migration log, and the customer must decide whether to split into multiple fields or accept data loss at the boundary.

Bloomr's activity records (calls, emails, meetings, tasks with timestamps and notes) have no Mailchimp equivalent. Mailchimp tracks campaign engagement (opens, clicks, unsubscribes) per Member, but this is marketing activity not sales activity. We do not migrate sales activity history to Mailchimp. If the customer requires activity tracking post-migration, we recommend a CRM add-on or a separate activity logging system integrated via Mailchimp's Webhooks.

Bloomr User records (team members with owner assignments on contacts and deals) are not migrated to Mailchimp in the same way. Mailchimp User accounts are workspace-level logins with permission roles (Admin, Manager, Author, Viewer). We map Bloomr owner assignments on Contacts to Mailchimp Member tags (Owner:[email protected]) to preserve the assignment context in Mailchimp, but we do not create Mailchimp User accounts as part of the migration scope. The customer provisions Mailchimp User accounts separately through their workspace settings.

Bloomr workflows and automation rules cannot be exported via any documented API mechanism. We do not migrate them as structured data. We deliver a written automation audit during scoping that lists every active Bloomr automation with its trigger conditions, actions, and recipient logic for the customer's admin to rebuild in Mailchimp Customer Journeys. Customer Journeys use event-based triggers (Member joins audience, email opened, link clicked) that differ from Bloomr's rule-based workflow model, so a direct mapping is not possible.

If Bloomr supports contact tags or labels, these map directly to Mailchimp Tags on the corresponding Member. We preserve the original tag names. Mailchimp tags are per-audience, so if the migration targets multiple Mailchimp audiences, we apply tag-scoping logic during the transform phase to ensure tags are assigned only to Members in the appropriate audience.