Migrate from Field Pros to Mailchimp

FieldPros candidate records map 1:1 to Mailchimp contacts. Every candidate's email, name, phone, and location fields become Mailchimp standard merge fields. Candidates without an email address are flagged as partial records — they cannot be imported to Mailchimp since email is required.

FieldPros candidate tiers (e.g., Bronze, Silver, Gold, Platinum) become Mailchimp tags applied per contact. Tags are additive — a candidate can carry multiple tier tags if their status has changed. Mailchimp applies all tags during bulk import using the API tagging endpoint.

FieldPros placement statuses (Active, Placed, Withdrawn, On Hold) map to Mailchimp tags: 'status-active', 'status-placed', 'status-withdrawn', 'status-on-hold'. These tag values are pre-defined in the migration plan before import so Mailchimp audience segments can filter by recruitment stage immediately after data lands, enabling instant segmentation by candidate availability.

FieldPros skill tags (e.g., 'EdTech Sales', 'Curriculum Design', 'Data Science') map directly to Mailchimp tags. These tags enable audience segmentation for targeted talent outreach campaigns — a candidate tagged 'EdTech Sales' can be included in a product launch campaign email.

FieldPros source channel (LinkedIn, referral, job board, event) has no native Mailchimp field. We create a text merge field (SOURCE_CHANNEL) and populate it from FieldPros during migration. This field is filterable in Mailchimp segmentation but not as performant as a tag.

FieldPros client company records do not map to a native Mailchimp object — Mailchimp has no company/ account concept. We create a text merge field (CLIENT_COMPANY) on each candidate contact and optionally apply a tag matching the client name so segmenting by employer is possible in Mailchimp.

FieldPros salary band fields (hourly rate, annual salary range) migrate as number merge fields (SALARY_MIN, SALARY_MAX, RATE_TYPE). Mailchimp's standard merge fields support number types for filtering in segmentation — however, range-based filtering (e.g., candidates between $80k-$100k) requires manual segment creation in the Mailchimp UI.

FieldPros last-activity timestamp (last outreach, interview, offer date) preserves as a datetime merge field (LAST_ACTIVITY_DATE). Mailchimp does not expose activity timestamps natively for segmentation — the merge field is stored for reporting reference but cannot trigger automation logic without Mailchimp's Event API.

FieldPros candidate notes migrate to Mailchimp contact notes. Resume content or file URLs are stored as a text merge field (RESUME_URL) pointing to a hosted copy — Mailchimp does not natively store file attachments on contact records, so we preserve a reference URL for manual retrieval.

A FieldPros placement (candidate + client + compensation + start date) is not a native Mailchimp concept. We merge placement data across three merge fields on the candidate contact: PLACEMENT_CLIENT, PLACEMENT_SALARY, and PLACEMENT_START_DATE, plus a 'placed' tag. Historical placements are preserved as read-only reference data on each contact record.

FieldPros job req records (title, requirements, open/closed status) have no Mailchimp equivalent. Mailchimp is not an ATS — job req data must be exported as a reference CSV and re-entered in a dedicated applicant-tracking tool. We preserve the full job req export for manual rebuild.

FieldPros interview scheduling data (date, interviewer, round, outcome) has no Mailchimp construct. Mailchimp automations trigger on email opens, link clicks, or dates — not on recruiting workflow events. Interview history is exported as a CSV reference; the recruiting workflow must be rebuilt in an ATS.