Migrate from SuiteDash to Mailchimp

SuiteDash Contact records map directly to Mailchimp contacts within a designated audience. Standard fields (first name, last name, email address, phone, address) map to Mailchimp's corresponding merge field names (FNAME, LNAME, EMAIL, PHONE, ADDRESS). We resolve the email address as the primary key and flag any duplicate email addresses across SuiteDash contacts during scoping. The primary associated Company name from SuiteDash can be stored as a company merge field in Mailchimp if the customer wants to preserve that context.

SuiteDash tags on contacts migrate as Mailchimp tags on the corresponding audience member. Tags serve as the primary segmentation mechanism in Mailchimp and are applied directly at import time via the Mailchimp Tags API. Multi-word tags from SuiteDash are preserved as written; we normalize any special characters that would cause import errors. Tags from both the Contact-level and Company-level tag sets are merged into a single tag namespace to avoid duplicates.

SuiteDash Contact-scoped custom fields map to Mailchimp merge fields of the appropriate type. Text fields become Mailchimp text merge fields, date fields become date merge fields, and dropdown or select fields become radio or dropdown merge fields depending on the number of options. We create the merge field schema in Mailchimp before importing contact records. Any Contact Custom Field that uses a Dynamic Data Placeholder type unsupported by Mailchimp is flagged and resolved to a text merge field as a fallback.

SuiteDash Company records have no direct Mailchimp equivalent as independent objects. During scoping, we confirm whether the customer wants to associate each contact with a Mailchimp company name (using a company merge field) or prefer a flat contacts-only model. If a Company-to-Company association is needed, Mailchimp Plus and Premium tiers support company records; we note this tier requirement and map accordingly. Company revenue, employee count, and industry fields map to custom text merge fields if the customer chooses to preserve them.

SuiteDash Company Private custom fields are visible only to the Primary Contact and are not exposed via Dynamic Data Placeholders. Mailchimp has no concept of visibility-scoped custom fields on contacts. We identify every Private-scoped Company field during scoping, confirm with the customer which should be dropped (data is not migratable), stored as a plain-text merge field, or documented for manual follow-up post-migration. We do not silently drop these fields without sign-off.

SuiteDash Deals with pipeline stages, probabilities, and Won/Lost status have no equivalent in Mailchimp. Mailchimp is an email service provider, not a CRM with deal tracking. We export Deal records as a CSV inventory during migration for the customer's reference, but Deal data does not load into Mailchimp. The customer should retain SuiteDash access or a Deal export for historical record-keeping if pipeline reporting is required.

SuiteDash Invoice Custom Fields are a separate schema from CRM Custom Fields and are only discoverable via the Invoice API endpoints, not via GET /contact/meta. We run a dedicated Invoice-specific field discovery during scoping. Invoice data does not migrate to Mailchimp because Mailchimp does not support invoice objects. Historical invoice records are exported as a CSV file delivered alongside the contact migration.

SuiteDash email drip sequences and Flows that reference email sending actions have no direct Mailchimp equivalent as migrated data. We produce an Automation Audit Report listing every active SuiteDash Flow with trigger conditions, step sequence, delay intervals, and Dynamic Data Placeholder usage. The customer rebuilds these in Mailchimp Customer Journey Builder. We do not migrate automation logic as code.

SuiteDash Support Tickets with conversation threads and custom fields have no equivalent in Mailchimp. Mailchimp does not provide a ticketing or support case system. We export ticket records as a CSV with thread history for the customer's reference. If the customer needs support ticket functionality, it should be addressed by a dedicated helpdesk platform separate from the Mailchimp migration scope.

SuiteDash contacts with an unsubscribe or opt-out status are exported and imported into Mailchimp as a suppression list rather than as active audience members. Mailchimp's suppression list prevents accidentally emailing unsubscribed contacts after migration, which protects sender reputation and deliverability. We recommend exporting unsubscribes as the first step in migration scoping and importing them before any contact records load into the audience.