Migrate from Kickserv to Mailchimp

Kickserv Customers (representing businesses) map to Mailchimp contacts. The primary customer name becomes the contact's company merge field. Billing address and service address from Kickserv collapse to Mailchimp's single address merge field — we use the billing address as primary and flag service address in a custom merge field if both exist.

Kickserv Contacts (people linked to a Customer) map 1:1 to Mailchimp contacts. Email address is the unique key. When a Kickserv contact shares an email with an existing Mailchimp contact, we match by email and update; otherwise we create a new contact. First name, last name, and phone map to their Mailchimp equivalents.

Kickserv custom fields on Customer records create Mailchimp merge fields in the target audience. We infer field type from Kickserv's field type: text fields become TEXT merge fields, number fields become NUMBER, date fields become DATE. Pick-list fields in Kickserv become TEXT merge fields with the original values preserved as text strings in Mailchimp.

Kickserv custom fields scoped to Jobs have no Mailchimp equivalent because Mailchimp has no job object. We offer two paths: (1) create contact-level merge fields on the customer record to capture the most recent job field values, or (2) export job custom field data as a separate structured CSV linked by customer ID. We surface this choice in the migration plan before execution.

Kickserv Contact Tags map directly to Mailchimp tags on the contact record. Tags such as 'Residential', 'Commercial', 'Referral', and 'Priority' become Mailchimp tags that you can use for segmentation and automation triggers. Tags applied across multiple contacts aggregate correctly in Mailchimp's tag management view, and duplicate tags are automatically merged, ensuring clean segmentation for campaigns and audience reports.

Kickserv Work Tags apply to Jobs and Opportunities, not contacts. Since Mailchimp has no job object, Work Tags cannot map cleanly to contact-level tags. We extract Work Tags as a separate CSV export keyed by customer ID, which your team can import into a tag management tool or re-apply to contacts manually based on job history.

Kickserv Jobs (work orders with status, assigned technician, scheduled time, and line items) have no Mailchimp equivalent. We export Jobs as a structured CSV including job ID, customer ID, contact ID, status, scheduled date, assigned employee, and all job custom field values. This file is available for import into your operational reporting tool or a job-management system you retain.

Kickserv Estimates (with line items, totals, approval status) do not exist in Mailchimp. We export Estimates as a CSV keyed by customer ID with estimate ID, creation date, total amount, status (Draft, Sent, Approved, Declined), and line item details. This data supports your finance team's record-keeping independent of Mailchimp.

Kickserv Invoices (with payment status, amount due, items, and QuickBooks sync status) cannot map to Mailchimp contacts. We export all invoices as a CSV including invoice ID, customer ID, total amount, balance due, payment status, and creation date. If you use QuickBooks integration with Kickserv, the invoice data already syncs there and the export serves as a backup.

Kickserv Items and Services (products and labor types used on jobs and invoices) have no equivalent in Mailchimp's contact-centric model. We export your full Items catalog as a reference CSV so you can rebuild price lists or product catalogs in any downstream system that supports it.

Kickserv Employees (technicians and office staff with scheduling and time-tracking data) do not map to Mailchimp. Employee records and time-entry data are exported as a separate CSV keyed by employee ID. This data is outside Mailchimp's scope and supports your HR or payroll systems.