Migrate from ServiceTracker to Mailchimp

ServiceTracker Client records hold the business entity — company name, billing address, primary contact, and custom fields. We extract these as contact profiles in a Mailchimp Audience. The client name becomes the subscriber's company affiliation stored in a merge field; the primary contact name and email become the subscriber's core record.

ServiceTracker Contact records map 1:1 to Mailchimp subscribers — first name, last name, email, phone, address. These are Mailchimp's standard subscriber fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Each Contact from ServiceTracker becomes one subscriber in the target Mailchimp audience. Each mapped field is validated against Mailchimp's schema to ensure compatibility.

ServiceTracker custom fields on Client records (dropdown menus, text fields, date fields) require manual creation as Merge Tags in the Mailchimp Audience before migration. We provide a field-mapping manifest listing every custom field name, type, and pick-list value so your Mailchimp admin creates the correct tag type (text, number, dropdown, date, or checkbox) in advance.

ServiceTracker custom fields on Contact records map to Mailchimp merge tags the same way. Pick-list values in ServiceTracker become Mailchimp merge tag options. We flag any field types (like multi-select or rich text) that cannot map directly to a Mailchimp merge tag type and recommend alternatives such as tag-based segmentation.

ServiceTracker uses customer-type or category pick-lists to classify clients (e.g., Residential, Commercial, Industrial). These values map to Mailchimp Tags applied at import time so you can build segments in Mailchimp without needing a matching merge tag. Each ServiceTracker category value is applied as a tag on the subscriber record.

ServiceTracker stores separate service-location address fields per client or work order. Mailchimp's standard address merge field uses a combined street/city/state/zip structure. We split ServiceTracker's service address fields into Mailchimp's address merge fields. If multiple service locations exist per client, additional locations are stored in a custom merge tag as a comma-separated reference.

Work orders are the core operational record in ServiceTracker — job type, status, assigned technician, parts used, service notes, and timestamps. Mailchimp has no work-order or job-record schema. Work orders cannot migrate to Mailchimp; they remain in ServiceTracker or get exported as a CSV and archived separately.

ServiceTracker projects and service contracts associate multiple work orders, milestones, and billing terms. Mailchimp organizes contacts into audiences and segments but has no project or contract object. These records have no Mailchimp equivalent and stay behind or are exported as reference CSVs.

ServiceTracker generates invoices and tracks payment status linked to work orders and clients. Mailchimp is an email platform with no billing or payment schema. Invoices cannot migrate and must remain in ServiceTracker or be moved to a dedicated accounting tool.

ServiceTracker asset records track equipment, serial numbers, maintenance schedules, and service history linked to client sites. Mailchimp has no asset or equipment schema. Asset records cannot migrate and remain in ServiceTracker or are exported as a standalone CSV. This preserves historical context even if the records cannot be used within Mailchimp.

ServiceTracker may store internal notes or file attachments on contact records. Mailchimp does not have a native note or attachment feature for subscriber profiles. Notes text is preserved in a merge tag as a read-only reference; attachments cannot migrate. Please review the exported notes for completeness.