Migrate from Dialytica - Marketing Automation Platform to Mailchimp

Dialytica Contacts map directly to Mailchimp Contacts as subscribers within an Audience. We map the contact name (first_name, last_name), primary email address, and phone number. Custom fields on Dialytica Contacts migrate as Mailchimp merge fields. Phone numbers are critical because Dialytica Contacts with SMS campaign assignments need the phone field populated for Mailchimp SMS delivery. We apply a pre-import deduplication check on email address and phone to prevent duplicate subscribers in the destination Audience.

Dialytica SMS Campaigns map to Mailchimp Campaigns with the original campaign name preserved in the campaign title. We create Mailchimp campaigns in a paused state during migration and apply a tag matching the Dialytica campaign name to every contact that was assigned to that campaign. This tag-based attribution preserves which Dialytica campaign drove each contact's enrollment, enabling segmentation and reporting in Mailchimp without replicating Dialytica's campaign assignment logic.

Dialytica SMS Activities record individual message events: message body, delivery status, timestamp, and contact reference. We map these as contact-level activity records in Mailchimp, using tags (e.g., sms_delivered_2024-03-15) to preserve event-level history that Mailchimp does not store as discrete objects. We cannot create individual activity records in Mailchimp's standard object model, so the tag-based event log serves as the proxy for contact-level SMS history.

Dialytica SMS Templates with body text and merge field placeholders map directly to Mailchimp SMS templates. We preserve the template body, variable names, and placeholder structure so that Mailchimp's personalization tokens can be mapped during campaign setup. Template metadata (creation date, last modified) migrates as custom fields on the Mailchimp template record.

Dialytica Agent records (name, email, role) cannot map to Mailchimp users because Mailchimp does not have a user object for agents. We preserve agent attribution by creating contact tags in the format agent_[agent_name] on each contact that has a recorded call or SMS interaction with that agent. This allows the customer's team to see which agent handled which contact without a native agent management module in Mailchimp.

Dialytica Payments track transaction records associated with campaigns or contacts. Mailchimp does not have a payments or transactions object. We extract payment records as a CSV export and deliver it alongside the migration, noting that the customer may attach this as a supplementary data file or import it to a separate financial tool. Payment data does not connect to Mailchimp's contact or campaign model.

Dialytica Call Campaigns are distinct from SMS Campaigns and contain dialing configurations, IVR logic, and call scripts. Mailchimp is an email and SMS platform with no outbound dialing capability, so Call Campaigns have no structural equivalent. We document the call campaign names, schedules, and contact assignments as a written inventory for the customer's operations team to evaluate whether a separate dialer tool (e.g., a CRM with built-in dialer, or a dedicated dialer platform) is needed post-migration.

Dialytica Call Records store duration, disposition, agent assignment, recording URL, and AI-evaluated metadata. Mailchimp does not support call records as a data object. We export call records as a CSV file with all available fields and deliver it as a supplementary data archive. The recording URLs are preserved as links within the CSV, but Mailchimp cannot display or play back call recordings within its interface. This data loss is disclosed upfront during scoping.

Dialytica QA Reviews store supervisor evaluations tied to specific call records with scorecard criteria and free-text notes. Mailchimp has no quality assurance module or call review capability. We export QA Reviews as a structured CSV with review criteria, scores, agent names, and timestamps. This data serves as an audit record but cannot be reconstructed within Mailchimp's marketing data model. The customer may retain this data for compliance or HR purposes separately from the marketing platform.