Migrate from Service Buddy to Mailchimp

Service Buddy customer records map directly to Mailchimp audience contacts, using the email address as the unique identifier. During import, contacts lacking a valid email are flagged and held for manual resolution to prevent hard bounces. Duplicate email entries are merged or flagged, and opted‑out contacts are directed to Mailchimp’s suppression list rather than the active audience, preserving list hygiene and sender reputation.

Service Buddy allows a customer to be associated with multiple companies (N:N). Mailchimp contacts have a single COMPANY merge field. The primary company (most recently modified association) becomes the COMPANY value; secondary companies are appended to a CUSTOM_COMPANIES__c merge field or a tagged note for reference.

Service Buddy customer status values (Active, Prospect, Inactive, etc.) translate into Mailchimp segments created by querying the CUSTOMER_STATUS__c merge field. Each status can be turned into a named segment—Active, Prospect, Inactive—allowing targeted campaigns such as re‑engagement for inactive contacts or exclusive offers for prospects. Active customers form the primary sendable segment, while Inactive contacts can be kept in a separate suppression‑ready segment to maintain clean audience health.

Service Buddy supports multi-location customer records. When locations represent distinct customer bases (different brands or geographic markets), FlitStack creates separate Mailchimp audiences and maps customers into the correct audience by location tag. A single audience using location-based segments is preferred where list overlap exists.

Service Buddy job records (scheduling, installation, cleaning, repair) have no Mailchimp equivalent. Job IDs and current status are preserved as a JOBS_REFERENCE__c merge field and tagged as historical context. Campaign segmentation based on job type must be rebuilt using Mailchimp's Customer Journeys and segment queries against other merge fields.

Service Buddy digital proposals and quotes have no native Mailchimp equivalent. Quote values, approval status, and line items are collapsed into a LAST_QUOTE__c text merge field for reference. Active quote pipeline data must be exported separately as a CSV report for internal use post-migration.

BuddyPay payment records (card transactions, ACH, invoice status, balances owed) do not map to Mailchimp. Payment history summary fields (last payment date, outstanding balance) are migrated as text merge fields for reference only. Actual financial reconciliation remains in Service Buddy or QuickBooks Online — Mailchimp has no payment object.

Service Buddy inventory records, QR-code labels, stock levels, and vendor purchase history have no Mailchimp equivalent. Product interest signals embedded in customer records (e.g., preferred product categories) are migrated as PRODUCT_INTEREST__c merge fields if present; full inventory data is exported as a separate CSV for internal use.

Service Buddy custom fields on the customer object (pricing tier, store number, referral source, etc.) are migrated as Mailchimp merge fields. The merge field API name follows Mailchimp's ALL_CAPS naming convention. Field type mapping: text to text, pick-list to dropdown merge field, date to date merge field.

BuddyAI-generated customer insights and notes are migrated to Mailchimp's per-contact note field where possible, but note length and formatting limitations apply. Extended AI summaries exceeding Mailchimp's note length are exported as a separate CSV keyed to the contact's email address.

Service Buddy contacts with an opt-out or inactive flag are imported to Mailchimp's suppression list rather than the active audience. Importing suppressed contacts as subscribed would violate Mailchimp's compliance policy and damage sender reputation — FlitStack handles this as a separate import step using Mailchimp's native suppression CSV format.

Service Buddy's two-way QuickBooks Online integration for invoicing and accounting has no Mailchimp equivalent. Payment-triggered email automations in Service Buddy (e.g., invoice sent, payment received) cannot migrate — they must be rebuilt using Mailchimp's Customer Journeys or an intermediate integration layer connecting QuickBooks to Mailchimp.