Migrate from ServiceNow Field Service Management to Mailchimp

ServiceNow customer records map directly to Mailchimp subscribers. The customer.email field populates the subscriber email address. First name, last name, and phone map to standard Mailchimp merge fields. Custom properties on the customer record migrate to Mailchimp merge fields where data types are compatible. During the migration, we validate each email address format and flag any records with invalid or malformed email addresses for manual review before importing into Mailchimp.

ServiceNow internal user accounts (technicians, dispatchers) do not map to Mailchimp subscribers. These records are preserved as internal reference tags on the corresponding customer subscriber record so your team can track which technician last serviced a customer. The technician name and assignment date become part of the internal reference tag for audit and reporting purposes within your Mailchimp audience.

Work order status (Open, In Progress, Closed Complete, Closed Incomplete) and work order type become Mailchimp tags applied to the associated customer subscriber record. Each work order generates one tag with the format WO-{number}: {status}. Tags enable segmentation by service history without creating records in Mailchimp. The work order type (Preventive, Corrective, Emergency) is appended to the tag for additional segmentation granularity.

ServiceNow location records with full street address, city, state/province, and postal code map to Mailchimp's address merge field group. Parent-child location hierarchies flatten to the most granular address per customer — the customer's primary service location is used when multiple locations exist. The most recent work order associated with each location determines which address becomes the primary service location for Mailchimp.

Incident records associated with a customer contact become tags on that subscriber. Tag format INC-{number}: {state} preserves the incident number and current state for segmentation by support history. High-priority incidents can be tagged separately for targeted re-engagement campaigns. We also capture the incident category and priority level within the tag metadata for enhanced segmentation options.

When a customer contact is associated with one or more configuration items (equipment under service contract), the most-recently-modified CI's class and model populate a text merge field. Multiple CI associations merge into a pipe-delimited custom merge field listing all associated equipment. The merge field captures the equipment type, manufacturer, and model for targeted product-related email campaigns.

ServiceNow assignment groups (dispatch teams, service regions) have no Mailchimp equivalent. We tag the customer subscriber record with the most-recently-assigned group name for internal segmentation only. These assignment group tags are used for internal reporting and routing of marketing communications, but Mailchimp does not use these for determining send eligibility or campaign delivery logic.

SLA definitions linked to customer records migrate as a text merge field capturing the SLA name and tier level. This enables segmentation by service tier in Mailchimp campaigns without rebuilding the tier logic. Premium SLA customers can be segmented for priority communications, while standard tier customers receive standard campaign treatment based on their migrated SLA classification.

ServiceNow work notes and customer communication logs have no Mailchimp equivalent. These are exported to a CSV reference file for audit purposes and not imported into Mailchimp. The full note history is preserved in the migration package. This ensures your complete service history documentation remains accessible for compliance and customer service purposes even though it does not map to Mailchimp's subscriber activity model.

Any custom fields added to ServiceNow FSM base tables become Mailchimp merge fields where field type supports it (text, number, date, phone). Fields with unsupported types (reference lookups, glide lists) are exported as text strings. Up to 40 merge fields per audience are available; additional fields are exported to CSV reference. During pre-migration audit, we identify all custom field definitions and their data types to determine optimal merge field assignments and reference exports.

ServiceNow contact records (separate from customer records) that have an email address migrate as additional subscribers to the Mailchimp audience. Contacts without email are flagged for manual review and not imported. The migration checks for duplicate email addresses between customer and contact records to prevent creating redundant subscriber entries in your Mailchimp audience.

ServiceNow account/company records linked to customers migrate as a COMPANY_NAME merge field on the subscriber record. The account name also becomes a tag on the subscriber enabling company-based segmentation in Mailchimp campaigns. Industry classification from the account record is mapped to a separate INDUSTRY merge field for sector-based targeting and personalization of campaign content.