Migrate from BSI CRM to Mailchimp

BSI CRM Contact records map to Mailchimp Audience Members. Standard fields (first name, last name, email, phone, job title) map directly to Mailchimp native contact fields. Custom Contact properties from BSI CRM migrate as Mailchimp custom merge fields. Email address serves as the dedupe key. We validate email format and suppress invalid addresses before import to protect Mailchimp sender reputation. Subscription status (opted-in vs. unsubscribed) maps from BSI CRM's contact preferences or consent fields.

BSI CRM Company records do not have a direct Mailchimp equivalent. We offer two strategies: (1) Tag strategy — apply a company name tag to every Contact linked to that Company, preserving the relationship as a label; (2) Group strategy — create a Mailchimp Group category named Companies and add each Contact to the Group matching their Company. We recommend the Group strategy for businesses that need to filter by company in segmentation. Company hierarchy (parent-child) cannot be preserved in Mailchimp.

BSI CRM Deals with pipeline stage, value, owner, and expected close date have no Mailchimp equivalent. Mailchimp does not support Opportunity, Deal, or pipeline objects. We document every active Deal in a written inventory with stage, value, owner, and close date so the customer's admin can recreate the pipeline data in a spreadsheet or a separate Deal-tracking tool post-migration. This is a critical scope item that must be confirmed with the customer before project commitment.

BSI CRM engagement history (logged calls, emails, meetings, tasks, notes) has no Mailchimp equivalent. Mailchimp captures campaign-level engagement (opens, clicks, unsubscribes) for emails sent from within Mailchimp, but BSI CRM activity records are internal CRM logs. We do not migrate activity history. We document the count of each activity type (calls, emails, meetings, tasks, notes) per contact during discovery so the customer understands the scope of history being left behind.

BSI CRM custom objects and fields require pre-migration schema discovery because the platform does not publish a self-service export. We enumerate all custom object names, field definitions, and record counts during discovery. Each custom object field maps to either a Mailchimp custom merge field (if scalar data type) or a Mailchimp tag (if categorical data type). Highly relational custom objects (with foreign keys to other custom objects) cannot be represented in Mailchimp's flat contact model and are flagged as data loss requiring manual reconstruction.

BSI CRM Users and Owner assignments on Contacts, Companies, and Deals have no Mailchimp equivalent. Mailchimp has Account Users (admin, manager, author, viewer roles) but no record-level ownership assignment on contacts. Owner assignments on migrated contacts are documented in the migration inventory so the customer can use Mailchimp tags or custom fields to replicate ownership tracking if needed.

BSI CRM tags and custom classification fields migrate to Mailchimp tags. BSI multi-select classification fields migrate to multiple Mailchimp tags on the same contact. BSI single-select classifications migrate to either a Mailchimp tag or a Mailchimp Group depending on whether the customer wants the value as a standalone label or part of a group category. We confirm the tagging strategy during scoping based on the customer's segmentation plan.

File attachments associated with BSI CRM Contacts, Deals, or Activities do not migrate to Mailchimp. Mailchimp does not support file attachments on individual contacts. We document the count of attachments per contact during discovery. The customer's admin is responsible for migrating critical attachments manually (e.g., via shared drive link stored as a custom field value) or accepting them as non-migrated.