Migrate from D-Tools to Mailchimp

Extract D-Tools contacts via Cloud API with pagination handling

FlitStack connects to the D-Tools Cloud API using the account's API key. The GetClients endpoint returns up to 500 records per request; we paginate through all client records, collecting standard fields (name, email, phone, address) and custom field values. D-Tools locations and company associations are pulled from related endpoints. We validate email format before staging and flag records with missing or invalid emails for customer review before the import batch commits.

Audit custom fields and recreate merge fields in Mailchimp audience

We inventory all D-Tools custom field definitions (name, type, pick-list options) and map them to Mailchimp merge field equivalents. D-Tools text fields become Mailchimp text merge fields; list fields become dropdown merge fields with options recreated from the D-Tools pick-list; boolean fields store TRUE/FALSE as text. We validate the total merge field count against the customer's Mailchimp plan limit and prioritize fields if the count exceeds the cap. This step runs before any data loads so the Mailchimp audience schema is ready for incoming records.

Load contacts into Mailchimp in batched API operations

We use Mailchimp's batch member-add endpoint (up to 5,000 members per batch) to ingest D-Tools contacts. Each contact maps to the audience with standard merge fields (FNAME, LNAME, EMAIL, PHONE, COMPANY, address fields) and custom merge fields populated from D-Tools. Service plan associations apply as Mailchimp tags. We run a pre-flight validation on 100 records before committing the full batch, checking that field types, character limits, and required-field constraints are satisfied. Duplicate email addresses are merged per Mailchimp's dedup rules — contacts with duplicate emails are flagged in the migration report.

Handle oversized attachments and store project/proposal references

For D-Tools file attachments under 2MB, we download and re-upload to Mailchimp's file manager, then attach to the relevant contact record. Files exceeding 2MB are noted in the migration report with the D-Tools file URL; the customer provides an external hosting destination, and we store the file URL as a hyperlink merge field. D-Tools proposal IDs and project IDs are written to custom reference fields on the linked contacts — these preserve the D-Tools audit trail without requiring a separate lookup system.

Deliver export package for workflow rebuild and run delta-pickup cutover

FlitStack exports a rebuild-reference document listing all D-Tools workflow rules with their names, trigger entities, criteria, and actions. This document serves as the blueprint for recreating automations in Mailchimp Customer Journeys. A delta-pickup window (24–48 hours after initial load) re-queries the D-Tools API for any contacts modified or created during the migration window. Final validation compares D-Tools contact count against Mailchimp audience member count and flags discrepancies for manual resolution before the account is decommissioned.