Migrate from Service In Sync to Mailchimp

Direct 1:1 map. Every Service In Sync contact becomes a Mailchimp audience member. Email address is the primary key — matched by subscriber hash in Mailchimp. If a contact has no email, it is flagged before migration and excluded or held pending manual review. First name, last name, phone, and address fields map to Mailchimp merge fields FNAME, LNAME, PHONE, and address fields respectively.

Mailchimp has no native company or account object. Service In Sync company name, domain, industry, and employee count migrate as custom merge fields on each associated contact (COMPANY_NAME, COMPANY_INDUSTRY, COMPANY_SIZE). Companies with multiple contacts inherit the same field values across all linked members. If your team needs company-level segmentation, company names map to tags for segment filtering rather than a separate object.

Service In Sync jobs have no direct Mailchimp equivalent because Mailchimp has no job object. We convert job records to contact-level merge fields: JOB_ID, JOB_STATUS, JOB_TYPE, JOB_DESCRIPTION, JOB_ADDRESS, JOB_AMOUNT. Service In Sync status values (created, dispatched, in progress, completed, invoiced) are stored as tags on the contact rather than a field, since Mailchimp pick-list fields cannot represent multi-state workflow progression. Staff name and service type also become tags used for segmentation.

Estimate records from Service In Sync map to ESTIMATE_STATUS (text merge field) and ESTIMATE_AMOUNT (number merge field) on the associated contact. Estimate line items, approval history, and version tracking have no Mailchimp equivalent and are documented in the migration plan as reference-only data that does not migrate.

Payment records migrate as PAYMENT_AMOUNT (number), PAYMENT_METHOD (text), and LAST_PAYMENT_DATE (date) merge fields on the contact. Full payment history and invoice records cannot be represented in Mailchimp and are flagged as reference-only data. If your team needs payment-based segmentation (e.g., 'customers with overdue invoices'), payment status becomes a tag applied at migration time.

Service In Sync service types (e.g., HVAC repair, plumbing, electrical) map to a SERVICETYPE text merge field and a service-type tag applied to each contact. Tags enable Mailchimp segment filtering by service type — e.g., a segment for 'all HVAC customers' to send seasonal maintenance campaigns. Custom service types require value-by-value tag creation during the migration plan phase.

Service In Sync staff names associated with a contact's job history migrate as Mailchimp tags on that contact. Multiple technicians on different jobs produce multiple tags on the same contact. Tags enable segmentation by assigned technician — useful for teams that want customers to receive communications from their regular technician or for routing follow-up campaigns by service region.

Service In Sync review star ratings (1–5) migrate as a REVIEW_STARS number merge field on the contact. The review text itself has no Mailchimp equivalent and is documented as reference data in the migration plan. Tags can also be applied for quick segmentation — e.g., '5-star reviewer' as a tag for requesting referrals or testimonials via Mailchimp campaigns.

Service In Sync records the last service date per contact from completed job history. This maps to a LASTSERVICEDATE date merge field in Mailchimp. Date merge fields enable time-based segmentation in Mailchimp — e.g., contacts whose last service was more than 12 months ago for a re-engagement campaign. Original timestamps from Service In Sync are preserved; current date is not substituted.

Scheduled future appointments from Service In Sync map to NEXTSERVICE_DATE date merge fields on contacts. Date-based segmentation supports appointment reminder automation in Mailchimp — e.g., a journey that sends a reminder 48 hours before NEXTSERVICE_DATE. If multiple future appointments exist, the nearest date is used; additional appointments are noted in the migration record as reference data.

Contacts flagged as unsubscribed in Service In Sync are set to 'unsubscribed' status in Mailchimp at import time, bypassing the normal subscribed state. Mailchimp's GDPR-compliant suppression list is respected — no subscribed records are imported for contacts who have opted out. This preserves deliverability and protects sender reputation from the moment the Mailchimp audience launches.

The original Service In Sync contact ID is stored in a SOURCE_RECORD_ID text merge field on each Mailchimp member. This field enables traceability between the two systems, supports delta-run de-duplication on future sync runs, and allows your team to cross-reference Mailchimp engagement back to the original Service In Sync job and payment record without maintaining a separate lookup table.