Migrate from Fieldmagic to Mailchimp

Fieldmagic has no native unsubscribe tracking — all contacts import as active Mailchimp members

Fieldmagic is a field service CRM, not an email marketing platform, so it does not track subscriber consent or unsubscribe status. Every contact exported from Fieldmagic arrives in Mailchimp with an active subscription status unless your team has manually tracked opt-outs in a separate spreadsheet. Sending to a list where unsubscribe records are unknown creates a spam complaint risk and potential campaign reputation damage in Mailchimp. FlitStack mitigates this by checking contact records for any indication of opted-out status and importing known unsubscribes into the Mailchimp suppression list before the main import, but a re-permission confirmation campaign is strongly recommended after go-live to establish documented consent for the Mailchimp audience.

Mailchimp merge fields are capped at 255 characters — truncated data for long-text Fieldmagic fields

Mailchimp's merge field system enforces a 255-character limit on all text-type merge fields. Fieldmagic custom fields that store long-form text — such as site inspection notes, job descriptions, asset service history, or custom textarea fields — will be truncated at 255 characters during migration. This is a hard Mailchimp platform constraint with no workaround beyond splitting the content across multiple merge fields or removing it from the audience model entirely. FlitStack flags any Fieldmagic field exceeding 255 characters during the field mapping phase so your team can decide whether to truncate, split, or exclude the field before migration runs.

Job records cannot be represented in Mailchimp fields — migration relies on tag-based job status mapping

Fieldmagic's Job object stores operational service records — job type, status, scheduled date, technician assignment, parts used, and notes. Mailchimp has no Job object and no operational record concept; its data model is limited to member attributes and tags. Job type and job status from Fieldmagic are migrated as Mailchimp tags (e.g., job-completed, job-scheduled, maintenance) applied to the Contact member, which enables segmentation for service-reminder automations. However, job history timelines, technician notes, parts pricing, and quote line items cannot be represented in Mailchimp fields — they require either a separate data export or a rebuild in a dedicated field service tool alongside Mailchimp.

Multi-site customer contacts can create duplicate Mailchimp members by email — deduplication resolves this

Fieldmagic allows a single Contact to be associated with multiple Sites — for example, a facilities manager responsible for three locations under one Customer account. Mailchimp members are unique by email address; there is no native multi-site association on a member record. When one Contact email appears across multiple Site associations in Fieldmagic, the standard Mailchimp import would create one member per unique email address and apply all site tags to that single record. This is the correct behavior for Mailchimp's flat audience model, but it means that the same contact's Mailchimp profile will show all site tags rather than separate records per site. Teams expecting one record per site per contact in Mailchimp need to understand this is not how Mailchimp's audience model works before the migration runs.

Fieldmagic custom field names use mixed casing — Mailchimp merge field names require sanitization

Fieldmagic allows custom field names with mixed casing and special characters that do not conform to Mailchimp's merge field naming requirements. Mailchimp merge field names must start with an uppercase letter, contain only alphanumeric characters and underscores, and use camelCase or snake_case conventions. FlitStack sanitizes every Fieldmagic custom field name during the mapping phase — converting spaces to underscores, removing special characters, and ensuring the resulting merge field name does not conflict with Mailchimp's reserved field names. Your team should review the sanitized merge field names in the migration plan before the audience is created, as a renamed merge field will display differently in Mailchimp campaign emails than it did in Fieldmagic.