Migrate from MobileWorker to Mailchimp

MobileWorker worker profiles map 1:1 to Mailchimp contacts. Email address is the primary key — workers without an email address on record are flagged for manual review before migration. First name, last name, phone, and job title transfer as standard Mailchimp contact fields.

Work order attributes (order ID, status, priority, due date, assigned date) cannot map to a native Mailchimp object. We store each attribute as a Mailchimp merge field on the associated Contact record so the full work-order context travels with the contact.

Work order status values (Pending, In Progress, Completed, Cancelled) become Mailchimp tags on the contact. This allows segmenting contacts by work-order state without creating additional merge fields — useful for filtering active vs. completed workers in Mailchimp campaigns. Tag names are prefixed with the order identifier for uniqueness.

Each work-order assignment creates a Mailchimp tag on the assigned worker contact. Tags are namespaced by order ID (e.g., WORKORDER_12345) so assignment history is preserved as a tagged audit trail accessible within Mailchimp's contact profile. The tag format also supports filtering assignments across multiple orders using pattern‑matching queries in Mailchimp's segment builder.

MobileWorker stores GPS coordinates and last-known location per worker. Mailchimp has no native location field — coordinates cannot be stored. We preserve the last address text as a plain-text address field for reference only; location-based segmentation is not available in Mailchimp.

Work order priority (High, Medium, Low) maps to Mailchimp tags prefixed PRIORITY_HIGH, PRIORITY_MEDIUM, PRIORITY_LOW. This enables segmentation by urgency level across all contacts with open work orders. When multiple priorities exist for a single contact, separate tags are applied for each, allowing you to filter contacts that have any high‑priority orders or to focus on medium‑priority tasks in specific campaigns.

Worker-level notes from MobileWorker transfer as Mailchimp contact notes. Notes are appended with a timestamp prefix indicating the original MobileWorker create date so audit trail is preserved within the contact record. If multiple notes exist per worker, they are imported in chronological order and retain their individual timestamps, ensuring a complete history within each Mailchimp contact profile.

Any MobileWorker custom properties defined beyond standard fields (e.g., certification_type, fleet_vehicle_id) require a corresponding Mailchimp merge field. We create merge fields with appropriate data types — text, number, date, or dropdown — based on the source property type before migration runs.

Mailchimp campaign history does not transfer from MobileWorker. There is no equivalent object in MobileWorker — campaigns must be created fresh in Mailchimp using migrated contacts as the audience. Historical send logs remain in MobileWorker and are preserved as exported files for reference.

MobileWorker task-assignment logic and notification triggers have no Mailchimp equivalent. We export the workflow definitions as a JSON specification so your Mailchimp admin can reference them when building Customer Journeys. Automated assignment sequences must be rebuilt manually in Mailchimp. The JSON export includes condition nodes, assignee rules, and timing parameters, providing a clear blueprint for reconstructing the logic in Mailchimp's visual workflow builder.