Migrate from Salesboom to Mailchimp

Salesboom Contacts map directly to Mailchimp Audience members via email address as the dedupe key. Standard Contact fields (First Name, Last Name, Email, Phone, Mailing Address) map to Mailchimp FNAME, LNAME, EMAIL, PHONE, and address merge fields. We use Mailchimp's batch upsert endpoint (PUT /lists/{list_id}/members/{subscriber_hash}) with status=subscribed to create or update subscribers without creating duplicates. The Contact-to-Account association migrates as a custom merge field (COMPANY_NAME) and as a Mailchimp Tag derived from the related Salesboom Account name, preserving the ability to segment by company without a native parent-child relationship.

Salesboom Leads map to the same Mailchimp Audience as Contacts. We evaluate the Lead status field to determine segmentation: new or open Leads receive a Lead tag; qualified or converted Leads receive a Qualified_Lead tag. The original Salesboom Lead status value is stored in a custom merge field (SB_LEAD_STAT) for audit. If the customer runs multiple Salesboom pipelines (Marketing vs. Sales), we can split Leads into separate Mailchimp Audiences by pipeline during migration to match downstream segmentation strategy.

Salesboom Account records are not a native Mailchimp object type. Account names and Account IDs migrate as a Mailchimp Tag per unique Account (tag name = Account Name, tag source = Mailchimp) and as a custom merge field COMPANY_NAME on the subscriber record. This preserves the ability to filter subscribers by organization in Mailchimp Segments. If the customer has fewer than 50 unique Accounts, we recommend creating one tag per Account. If there are more than 50, we recommend mapping to the COMPANY_NAME merge field only and using segment filters on that field.

Salesboom custom fields on Contact and Lead migrate to Mailchimp merge fields or tags depending on data type. Text, number, and date fields map to Mailchimp merge fields (type: text, number, or date). Multi-select picklist and checkbox fields map to Mailchimp Tags. Note that Mailchimp Essentials supports up to 40 merge fields per audience, Standard supports 80, and Premium supports unlimited. We audit the total count of active custom fields per object during scoping and recommend an Audience split or selective field migration if the count exceeds the destination tier's limit. Custom fields on non-contact objects (Opportunity, Case, ERP modules) are documented but have no Mailchimp target and are excluded from the migration.

Salesboom Opportunities represent pipeline deals with stage, amount, close date, and probability. Mailchimp does not have an Opportunity object. We exclude Opportunities from the migration scope. We deliver a written inventory of all active Opportunities at migration time (exported as a CSV from Salesboom) including stage, amount, close date, owner, and related Account and Contact names. The customer's admin uses this to rebuild a pipeline tracking approach in Mailchimp (Customer Journey with manual status updates, or a third-party CRM if pipeline management is still required).

Salesboom Cases are ticket-style support records with status, priority, origin, and resolution fields. Mailchimp does not have a case or ticket management module. We exclude Cases from the migration scope. Support-related contact history (resolved cases, open case counts) can be preserved as Mailchimp tags on the Contact record if the customer requests it, but this is an opt-in configuration. We deliver a Case inventory CSV as part of the handoff package.

Salesboom ERP add-on modules (Accounts Payable, HR Policy Tracking, Payroll, PTO Management, Expense Tracking) each cost $10/user/month and have distinct transactional schemas unrelated to email marketing. These modules have no Mailchimp equivalent and are excluded from the migration entirely. We confirm whether the customer has licensed any ERP modules during scoping and flag them in the pre-migration audit so that no one expects this data to appear in Mailchimp post-migration. Transactional ERP data requires a separate migration to an accounting or HRIS platform if retained.

Salesboom Workflow & Business Process Automation rules (available on Professional and Enterprise tiers) define automatic lead routing, task assignment, email triggers, and field updates based on record criteria. Mailchimp Customer Journey automations are email-triggered and campaign-focused; they do not replicate CRM workflow logic. We do not migrate Workflows as code. We deliver a written inventory of every active Salesboom workflow rule including its trigger object, conditions, actions, and recommended Mailchimp Customer Journey equivalent (or a note that no equivalent exists in Mailchimp). The customer's admin rebuilds these in Mailchimp post-migration.