Migrate from Serviceform to Mailchimp

Discovery and extraction feasibility assessment

We audit the Serviceform account to identify all active Leads, conversation history volumes, form schemas, chatbot flows, integration connections, and team member accounts. Because Serviceform lacks a documented public API, we assess the feasibility of UI-based bulk export, direct Serviceform support engagement, or CSV/manual extraction for each data type. We produce a written extraction plan that identifies which data can be exported cleanly, which requires support team coordination, and which (such as granular chatbot flow logic) should be documented rather than exported. This phase also includes a Mailchimp Audience audit to confirm merge field configuration and suppression list readiness.

Data extraction and preprocessing

We execute the extraction plan identified in discovery. Leads export from Serviceform's UI or via support-coordinated bulk export. Conversation transcripts are extracted per lead and formatted as structured text. Form submission data is extracted with field labels and values. We preprocess all exported data to clean duplicates (by email address), flag suppressed contacts, normalize phone number formats, and map custom Serviceform properties to placeholder merge field names in Mailchimp. Any data that cannot be extracted cleanly is flagged with a severity rating and a recommended workaround in the migration report.

Mailchimp merge field and Audience configuration

We create all required Merge Fields in the destination Mailchimp Audience before any contact import. This includes standard fields (FNAME, LNAME, EMAIL, PHONE), custom merge fields for Serviceform custom properties (lead score, source, qualification tier), and a SERVICE_SOURCE merge field with value 'Serviceform' for audit. We configure the Audience settings including default language, opt-in requirements, and email notification preferences. If multiple Audiences are required (per scoping decision), we set up the Audience structure now. Suppression list import preparation happens at this stage to ensure bounced and unsubscribed contacts are blocked from the main import.

Contact import and suppression list handling

We import Serviceform Leads as Mailchimp Members using Mailchimp's REST API with batch operations for large lists. Email address is the dedupe key. Suppressed contacts (unsubscribed, bounced, cleaned) are imported as a separate suppression list and merged into the Audience's global suppression state so they are never charged against the contact tier. Each imported Member receives tags indicating the original chatbot source and form submission context. We run reconciliation reports comparing the Serviceform lead count to the Mailchimp Member count, verifying no unintended exclusions or duplicates.

Conversation history and note attachment

We attach Serviceform conversation transcripts as Contact Notes to each imported Member using Mailchimp's Notes API. Each conversation thread becomes one Note record. Notes include the chatbot name, conversation date range, and the full message transcript formatted as a text block. If conversation volume is large (thousands of transcripts), we batch note creation to respect Mailchimp API rate limits and provide a progress report. Note: Mailchimp Notes have a 10,000-character limit; long transcripts are truncated with a reference to the original export file.

Handoff documentation and rebuild specifications

We deliver the migration handoff package including: a contact count reconciliation report (source vs. destination), a chatbot-to-email-journey mapping document for rebuilding Serviceform chatbot flows as Mailchimp Customer Journeys, a form rebuild guide for translating Serviceform conditional form logic into Mailchimp embedded form configuration, a merge field reference sheet documenting every Serviceform property mapped to a Mailchimp field, and a Mailchimp user provisioning guide mapping Serviceform team roles to Mailchimp account roles. We do not rebuild automations, forms, or chatbot flows inside the migration scope; these are admin tasks guided by the documentation we deliver.