Migrate from ConSol to Mailchimp

ConSol service tickets have no Mailchimp equivalent — ticket history surfaces as tags, not case records

ConSol CM's core object is the service ticket: it tracks request subject, status, priority, assigned agent, email threads, and SLA timers. Mailchimp has no ticket or case object — it tracks email campaign engagement (opens, clicks, unsubscribes) but not support request status. When migrating from ConSol to Mailchimp, all ticket records are surfaced as contact-level tags ('Ticket: [ID] - [Status]') and merge field metadata. If your team relies on ConSol ticket history for customer health scoring or support load reporting, that logic must be rebuilt in Mailchimp using the preserved merge field values or an external reporting layer.

ConSol's N:N contact-to-company model flattens to a single primary-company assignment in Mailchimp

ConSol CM allows a contact to be associated with multiple companies simultaneously — a common pattern for enterprise accounts where a contact works across parent and subsidiary companies. Mailchimp contacts have no native company linkage; each contact record holds one set of company-related fields. We resolve this by assigning the most recently modified ConSol company as the primary (mapped to the COMPANY merge field) and applying additional company associations as tags in 'Company: [Name]' format. If your reporting depends on multi-company contact views, you will need to build Mailchimp segments using the tag data or export the full company-contact mapping for external analysis.

ConSol workflows and service automations do not migrate — escalation rules and SLA timers must be rebuilt in Mailchimp

ConSol CM includes service request routing rules, escalation workflows, SLA timers, and auto-assignment logic based on ticket category and priority. Mailchimp automation is email-campaign-centric: it triggers on opens, clicks, purchases, or date-based conditions. There is no SLA timer, no queue-based routing, and no agent assignment concept in Mailchimp. The migration exports your ConSol workflow definitions as a reference document so your team can evaluate which rules can be approximated in Mailchimp's automation builder and which ConSol-specific logic is not translatable to an email marketing context.

ConSol document attachments do not migrate to Mailchimp — file storage paths are exported as a reference manifest

ConSol stores documents linked to contacts and service tickets — contracts, signed agreements, support screenshots, and uploaded files are tracked in ConSol's document management layer. Mailchimp stores attachments as campaign assets (images in email templates) but has no per-contact document storage. We export the document metadata (file name, ConSol storage path, linked contact ID, linked ticket ID) as a JSON manifest. Files must be migrated separately to a document management system such as SharePoint, Google Drive, or a dedicated DMS, and linked from Mailchimp contact profiles via external URL fields if needed.

Mailchimp contact counts include unsubscribed contacts in billing — ConSol opted-out contacts must be suppressed

Mailchimp billing is based on total contact count in an audience, including unsubscribed and non-subscribed contacts in most plan tiers. ConSol stores explicit opt-in and opt-out flags per contact. Before migration, we identify all ConSol contacts with an active opt-out or bounced-email status and import them as suppressed contacts in Mailchimp so they are not counted toward your plan limit. Contacts that were soft-bounced in ConSol are similarly suppressed in Mailchimp to protect deliverability metrics after migration.