Migrate from Novo Work Order to Mailchimp

Direct map. Novo Work Order contacts (citizens, employees, contractors) migrate as Mailchimp subscribers within a designated Audience. Standard fields — first name, last name, email, phone — map to Mailchimp's built-in contact properties. Mailchimp requires a valid email address for every subscriber; contacts without emails are flagged before import and excluded from the migration run.

Novo Work Order department assignments on contacts (Public Works, Utilities, Facilities, IT) migrate as Mailchimp subscriber tags. Tags are applied per contact based on the source department field value. Mailchimp creates tags automatically if they do not exist — no pre-configuration required. Tags enable segmented campaign sends by department without requiring separate Audiences.

Service-type or request-category values from Novo Work Order contacts (pothole repair, water leak, fleet maintenance, etc.) migrate as Mailchimp tags. If a contact has multiple service types associated across their history, each type gets its own tag. Tags are additive, not exclusive, matching Mailchimp's tag-on-contact model. Tags enable customer-journey automations by service type in Mailchimp.

Novo Work Order custom request properties of type text (e.g., Request Source Channel, Preferred Contact Method, Service Location) map to Mailchimp text merge fields. Field label from Novo Work Order becomes the merge field name in Mailchimp, with spaces converted to underscores and prefixed by an asterisk for Mailchimp's merge field naming convention.

Novo Work Order numeric custom properties (e.g., Priority Score, Asset ID reference, Estimated Cost) map to Mailchimp number merge fields. Number fields preserve integer or decimal values as stored in Novo Work Order. Mailchimp number fields can be used in segmentation rules for range-based filtering (e.g., contacts with Priority Score greater than 5).

Novo Work Order date-type custom properties (e.g., Last Service Date, Inspection Due Date) map to Mailchimp date merge fields. Date values are stored in ISO 8601 format during import. Mailchimp date merge fields support relative date segmentation (e.g., Last Service Date within last 30 days) for campaign targeting.

Novo Work Order dropdown or picklist properties map to Mailchimp dropdown merge fields. Each picklist value from Novo Work Order becomes a corresponding option in the Mailchimp dropdown merge field. If a Mailchimp dropdown cannot accommodate all values due to the 40-merge-field limit, values are consolidated into a text field and documented in the migration plan.

Email address maps directly from Novo Work Order contact email to Mailchimp subscriber Email Address field. This is the only required field for a Mailchimp subscriber record. Contacts with missing or invalid email addresses are listed separately and require manual resolution before the migration run commits.

Work order records, asset associations, labor hours, parts costs, and maintenance history have no equivalent object in Mailchimp. Mailchimp's data model is subscriber-centric — it does not support work order or asset objects. We do not migrate work order records; the scope is limited to contact and subscriber data. Work order history can be preserved as a custom text merge field (JSON blob of work order IDs) for reference, but Mailchimp cannot display or manage work orders natively.

Novo Work Order does not have an email consent model equivalent to Mailchimp's subscriber status. All contacts migrate as Subscribed by default unless the organization's data export includes an explicit opt-out field. If an unsubscribe list was maintained separately in Novo Work Order, those emails are imported as Unsubscribed in Mailchimp to suppress future sends.

File attachments on work order records (photos, PDFs, inspection reports) do not migrate to Mailchimp. Mailchimp does not have a subscriber-level file attachment object. Photos or documents associated with contacts in Novo Work Order are documented in the migration plan as a separate file inventory — teams can re-upload assets to Mailchimp's Content Studio manually or host them on a linked platform.

Novo Work Order assigned technician or owner information does not map to a native Mailchimp subscriber field. We create a custom text merge field (e.g., Primary_Technician__c) to store the assigned technician name or ID for reference. Mailchimp does not have a technician assignment or staff contact model — this field is informational only.