Migrate from ServeManager to Mailchimp

ServeManager Contact maps directly to a Mailchimp audience member. The email address is the primary key for deduplication — if a contact has no email, the record is flagged and held for manual review before import. First name, last name, phone, and address move as standard Mailchimp merge fields.

ServeManager contacts with role 'Client' receive a Mailchimp tag 'Client-Contact' on import. This preserves the role distinction that exists in ServeManager but has no native equivalent in Mailchimp's field model. Tags are applied as a post-import automation step using the imported role data.

Process server contacts are imported as audience members with the tag 'Process-Server' to distinguish internal staff from client contacts. Since Mailchimp has no role field, tagging is the only structural way to preserve this classification — it enables segment filtering post-migration.

ServeManager Company maps to the COMPANY merge field on a Mailchimp audience member. If the same company appears across multiple contacts in ServeManager, each contact imports independently with the same company name — Mailchimp does not support a separate company object, so the name lives as a merge field on each member record.

ServeManager's structured address fields (address, city, state, zip, country) on the Company record map to Mailchimp's flat ADDRESS merge field (ADDR1, ADDR2, CITY, STATE, ZIP, COUNTRY). If ServeManager stores a separate service address on a Job record, that does not map — it is preserved in the export reference file only.

ServeManager Job records have no Mailchimp equivalent. Jobs contain case number, service type, due date, court info, and GPS-linked addresses — these are legal-operations data unrelated to email marketing. We export the full job dataset as a structured JSON/CSV reference file for manual consultation. No job data is imported into Mailchimp.

Each Attempt record in ServeManager stores GPS coordinates, timestamp, photo proof URL, electronic signature, and attempt outcome (served, refused, not home). These have no Mailchimp analogue — attempt history is preserved in the export reference file but not imported. The GPS and photo data specifically cannot be represented in Mailchimp's audience member record.

ServeManager Invoice records contain invoice number, amount, status (paid/unpaid/overdue), line items, and Stripe payment reference. Mailchimp has no invoice or payment data model. Invoice data is preserved in the export reference file. Clients who need invoice history accessible to contacts must use a separate billing tool post-migration.

ServeManager Payment records track amounts, payment method (Stripe), date, and linked invoice. Mailchimp does not store payment records. Payment history is exported as a reference file. Stripe integration settings in ServeManager must be reconfigured independently if needed in the Mailchimp context.

ServeManager's payroll tracking for process servers — including payables, rates per job type, and payment status — has no Mailchimp equivalent. This is an internal operations dataset focused on server compensation and financial reconciliation, not a contact or marketing dataset. It is excluded from the Mailchimp migration scope entirely and remains in ServeManager for payroll processing.

ServeManager Company custom fields — such as practice area, bar number, client tier, or billing arrangement — are created as Mailchimp merge fields on the audience before import begins. These merge fields enrich the audience member profile and enable segmentation based on company characteristics. All merge fields are created with the correct type (text, date, or number) to match Mailchimp's requirements before the import batch runs.

Any custom fields on ServeManager Contact records (beyond standard firstname/lastname/email/phone) are created as Mailchimp merge fields before import. Text fields under 255 characters migrate directly; longer values are truncated to 255 characters and flagged in the field-level diff report.