Migrate from Kursaha to Mailchimp

Discovery and export capability audit

We audit the source Kursaha account for available CSV exports across all data objects (Contacts, Campaigns, Segments, Templates). We confirm which objects have complete dashboard exports, which have partial exports, and which have no export path (WhatsApp/SMS templates, analytics events). We check whether the account is cloud SaaS or on-premise deployment because on-premise requires direct database extraction. We also confirm subscriber status fields, custom contact properties, and any behavioral data stored as properties. The discovery output is a written export availability report and a migration scope with confirmed export paths for every object.

CSV extraction and field inventory

We request and receive CSV exports for each confirmed data object from the Kursaha dashboard. We inventory every column header against Mailchimp's supported Merge Fields and API field names, identifying direct 1:1 mappings (email, first name, last name) and custom fields requiring type decisions (text, number, date). We flag columns with no Mailchimp equivalent for exclusion or custom field creation. We validate row counts against in-platform counts reported by the customer to confirm export completeness before mapping begins.

Mailchimp audience and template setup

We create the Mailchimp Audience in the destination account, configure Merge Fields to match the Kursaha contact schema, and map subscriber status values. For email templates, we import HTML content where available and document any AMP markup or interactive elements for the customer to redesign in Mailchimp's template editor. We set up domain authentication (SPF, DKIM) in the customer's DNS and verify it with Mailchimp's check tool before any sends are initiated. This step includes importing unsubscribed and bounced contacts as a suppression list to protect deliverability.

Segment logic documentation

We extract and document the logic for every Kursaha Audience Segment as a written specification with the original filter conditions and audience count. We map simple segments directly to Mailchimp Segment rules. For complex segments that cannot transfer automatically, we deliver a detailed rebuild guide with the original conditions translated into Mailchimp's segment builder syntax, including operator equivalents and field name mappings. The customer's admin rebuilds segments using this guide post-migration.

Batch import via Mailchimp API

We push Contact records into Mailchimp using the Mailchimp API with batch chunking (typically 5,000 records per batch) and rate-limit handling with exponential backoff. Email serves as the dedupe key. Subscriber status, tags, and custom Merge Fields populate from the mapped CSV columns. Each batch emits a row-count reconciliation report. Campaigns are created in Mailchimp using the imported contact list, with subject line, from name, and from email mapped from the Kursaha export. Template content is uploaded as HTML files with a written review checklist for the customer's admin to verify layout rendering.

Cutover, suppression list review, and automation handoff

We freeze writes to the source Kursaha account, run a final delta migration of any contacts modified during the migration window, and enable Mailchimp as the system of record for email marketing. We deliver a suppression list of all bounced, unsubscribed, and cleaned contacts from Kursaha to the customer's admin for Mailchimp audience hygiene review. We deliver the automation and segment rebuild inventory document listing every active Kursaha workflow and segment requiring rebuild in Mailchimp's Automation builder, with recommended equivalents for common trigger types. We support a one-week post-cutover window for reconciliation issues.