Migrate from ServiceTitan to Mailchimp

ServiceTitan Customer records map directly to Mailchimp subscribers. Every customer with a valid, deliverable email address becomes a Mailchimp contact. Customers with no email address are flagged in the pre-migration report — they require email collection before import since Mailchimp does not accept contacts without an email address.

First name and last name on the ServiceTitan Customer record map to Mailchimp FNAME and LNAME merge fields. These are standard Mailchimp merge fields present in every audience. If ServiceTitan stores only a company name and no individual name, we map it to a custom merge field and leave FNAME/LNAME blank.

ServiceTitan Customer records map directly to Mailchimp subscribers. Every customer with a valid, deliverable email address becomes a Mailchimp contact. Customers with no email address are flagged in the pre-migration report — they require email collection before import since Mailchimp does not accept contacts without an email address.

ServiceTitan stores phone numbers on the Customer record. Mailchimp provides a PHONE merge field for exactly this purpose. We map phone directly but strip non-numeric characters during transformation to comply with Mailchimp's phone field format. We also validate phone number formats against international standards to avoid formatting errors in Mailchimp.

ServiceTitan allows multiple service locations per customer — each with its own address. Mailchimp stores one address per contact. We migrate the primary service location address to Mailchimp's ADDRESS merge field set (street, city, state, postal code, country). Secondary locations are either appended as a text note in a custom field or deduplicated per your preference.

ServiceTitan custom fields on the Customer object (for example, 'Customer Type', 'Referral Source', or trade-specific pick-lists like 'Service Contract Status') map to Mailchimp custom merge fields. We create merge fields in Mailchimp named to match the source field label. Pick-list values transfer as plain text strings; date fields become formatted text strings.

ServiceTitan Location records carry their own custom fields (for example, 'Equipment Brand', 'System Age', 'Last Service Date'). These cannot map to a standard Mailchimp field. We create prefixed merge fields (for example, LOC_System_Age) to carry this data as reference text on the primary contact record.

ServiceTitan Job records store work order history, job types, technician assignments, and service dates. Mailchimp has no job or work-order concept. Historical job records are not imported into Mailchimp. If you need to communicate service history by email, job summary text can be written to a custom merge field as a reference note — but this is a human-readable digest, not a structured record.

ServiceTitan invoices and payment records have no Mailchimp analogue. Invoice amounts, payment status, and billing history do not migrate. These records remain in ServiceTitan or must be exported separately for accounting purposes. Mailchimp is a marketing platform, not a billing or ERP system.

ServiceTitan stores customer categories or tags (for example, 'Residential Customer', 'Commercial Account', 'HVAC Contract'). We translate these into Mailchimp contact tags. Each unique ServiceTitan category becomes a Mailchimp tag. Multiple categories per customer result in multiple tags on the corresponding Mailchimp contact.

ServiceTitan Customer notes field maps to the Mailchimp contact note. We preserve the full note text. Mailchimp notes have a 2,000-character limit; longer notes are truncated with a marker indicating truncation. If the original note contains special characters or line breaks, we normalize them for display within Mailchimp's note field.

ServiceTitan assigns an owner (CSR or technician) to each customer record. Mailchimp contacts do not have an owner field at the individual contact level — ownership is an administrative concept within Mailchimp, not a per-contact attribute. Owner assignment is not migrated.