Migrate from Bluwave CRM to Mailchimp

Bluwave CRM Contacts map directly to Mailchimp Subscribers within a designated Audience. Email address is the dedupe key; we validate that every Contact has a non-null email before import to avoid Mailchimp's mandatory-email requirement. Name fields (first name, last name) map to the FNAME and LNAME merge fields. Phone numbers map to a custom merge field (PHONE) created in the Mailchimp Audience before import. Geocoded latitude/longitude stored against the Contact's address is preserved as a custom merge field pair (LAT, LNG) if the customer requires it; otherwise it is flagged for review as Mailchimp has no native geolocation use for contacts.

Bluwave CRM Leads are distinct from Contacts and carry lifecycle stage attribution. We import Leads as Subscribers in Mailchimp using the same email-based dedupe logic as Contacts, then apply a Mailchimp Segment tag based on the Lead's lifecycle stage (e.g., New Lead, MQL, SQL) so that the customer can target campaigns at the appropriate audience slice. If the Lead record contains a different email address from any existing Contact, it imports cleanly; if the email duplicates a Contact, Mailchimp merges on the email address and the record retains both Lead and Contact tags.

Bluwave CRM Company records (business name, industry, address) do not have a direct Mailchimp equivalent since Mailchimp does not maintain a separate Company object. We map the Company name to a COMPANY merge field on the Subscriber record, industry to an INDUSTRY merge field, and address components to Mailchimp's native ADDRESS merge field group. The customer can use these merge fields for personalisation tokens in campaigns or for segment filtering.

Bluwave CRM stores mail list segments for targeted marketing (e.g., newsletter, product announcements, customer follow-up). We extract the segment definitions and member email addresses, then create equivalent Segments in Mailchimp under the target Audience. Segment rules based on picklist values (e.g., product category, region) are recreated using Mailchimp's Segment builder, which supports similar inclusion/exclusion logic. We deliver a written segment mapping table alongside the migration.

Bluwave CRM Deals with pipeline stages, deal values, and expected close dates have no Mailchimp equivalent. Mailchimp tracks campaign engagement and revenue attribution through e-commerce integrations and revenue tracking features, but not sales pipeline records. We do not migrate Deals as records. We deliver a written Deal inventory as a CSV export for the customer's admin to reference if they configure Mailchimp's e-commerce revenue tracking separately or use a different CRM for pipeline management going forward.

Bluwave CRM Activities (face-to-face visits, calls, emails, tasks) carry geocoded location and travel claim associations that Mailchimp cannot receive. Mailchimp tracks email engagement activity (opens, clicks, unsubscribes) on its own records, not CRM activity history. We do not migrate activity records. We deliver a written activity inventory as a CSV export so the customer's admin has a record for compliance or audit purposes if required.

Bluwave CRM Pipeline Stages define deal progression and are configurable per organisation. Mailchimp has no pipeline model. We extract the current pipeline structure (stage names, reorder logic, probability weights) as a written configuration document for the customer's admin to reference if they set up a separate CRM for ongoing pipeline management.

Bluwave CRM custom fields (no public schema) are inferred from sampled export data during the scoping phase. We infer each field's data type from content (text, number, date, picklist) and create a corresponding Mailchimp merge field of the appropriate type before import. Mailchimp merge fields support text, number, date, phone, address, and birthday types. Picklist values from Bluwave CRM custom fields migrate as text merge fields or as Tags on the Subscriber record, depending on the customer's segmentation strategy chosen during scoping.