Migrate from MeasureSquare to Mailchimp

MeasureSquare contacts map directly to Mailchimp contacts in the target audience. Email address is the unique identifier — contacts without a valid email are flagged before migration since Mailchimp requires an email address for every subscriber. Duplicate emails are resolved by most-recently-modified date, retaining the latest MeasureSquare contact record.

MeasureSquare companies map to a custom contact field or merged text property in Mailchimp (e.g., 'Company Name: Acme Flooring'). Mailchimp does not have a separate Company/Account object. For contacts with multiple associated MeasureSquare companies (N:1 or N:N), we preserve the primary company and surface others as comma-separated text or tags.

MeasureSquare pipeline stages (Lead, Prospect, Bid Sent, Awarded, In Progress, Completed) have no native Mailchimp equivalent. We create Mailchimp segments keyed by pipeline stage name and apply them at import time. Stage names are mapped value-by-value, and contacts are automatically placed into the correct segment based on their MeasureSquare pipeline stage.

MeasureSquare lifecycle stages (Lead, Prospect, Customer, Inactive) require a custom contact field in Mailchimp — typically a pick-list field named 'MS_Lifecycle_Stage'. We create the custom field before import and map every contact's lifecycle value. This field can then drive Mailchimp segments for lifecycle-based email sequences.

MeasureSquare deal amounts (estimated project value) migrate as a custom number field in Mailchimp — typically 'MS_Deal_Amount' — stored on the contact record. This lets you segment customers by estimated project size for targeted re-engagement campaigns. Values are preserved as the decimal amount from MeasureSquare.

MeasureSquare projects, work orders, purchase orders, and job costing records have no Mailchimp equivalent. Mailchimp is a contact and campaign platform, not a project management tool. These records are exported as a separate CSV report for your records. Projects cannot be represented as Mailchimp contacts or custom objects.

MeasureSquare product databases (flooring materials, stone slabs, labor rates, supplier SKUs) are not contacts and do not migrate as Mailchimp objects. For teams using MeasureSquare product data for marketing (e.g., product-interest tags on contacts), we extract product catalog entries and apply them as Mailchimp tags or custom text fields on the contact record.

MeasureSquare tasks, activities, and estimator notes are not imported to Mailchimp. Mailchimp tracks engagement activities (email opens, clicks, unsubscribes) but not internal CRM tasks. Activity history from MeasureSquare is exported as a separate audit CSV and retained for your records.

Any MeasureSquare custom contact properties beyond the standard fields (e.g., 'Flooring Type Interest', 'Estimator Assigned', 'Referral Source', 'Warranty Status') are mapped to Mailchimp custom fields. We create a custom fieldset matching the MeasureSquare property types — text, number, date, or pick-list — and apply field names based on the source property names.

MeasureSquare attachments (floor plan files, cut sheets, slab layout PDFs) are not imported to Mailchimp. Mailchimp's contact record does not support file attachments. We export a list of MeasureSquare file references with their associated contact IDs so you can maintain a link between contacts and their attached documents outside of Mailchimp.