Migrate from StreetSmart to Mailchimp

StreetSmart customers map to Mailchimp subscribers one-to-one by email address. Email is the unique identifier in Mailchimp — contacts without a valid email cannot be imported as subscribers and are flagged for manual review before migration. All other contact fields map as merge fields or custom fields.

Mailchimp has no native company object. StreetSmart company names map to a COMPANYNAME merge field on the contact record. If companies in StreetSmart have multiple contacts, each contact carries the same company name. Company-level segmentation in StreetSmart rebuilds in Mailchimp using tags applied per company group.

Mailchimp has no job or work order object. Each StreetSmart job record associated with a contact flattens into custom merge fields on that contact: job ID, job name, job status, job type, technician name, scheduled date, and completion date. Multiple jobs per contact concatenate into a job history custom field.

Every StreetSmart custom property becomes a Mailchimp merge field. Merge fields must be pre-created in the Mailchimp audience before migration runs — we deliver a merge field creation checklist as part of the planning phase. Merge field type (text, date, number, dropdown) maps from the StreetSmart property data type.

StreetSmart multi-location setups consolidate into one Mailchimp audience. Each location name applies as a tag to every contact from that location, preserving the location segmentation that StreetSmart uses. Audience-level tags allow location-based segmentation for campaigns without creating separate Mailchimp audiences.

StreetSmart address fields (street, city, state, postal code, country) map to Mailchimp's native ADDRESS merge field, which handles all five address components in a single field. Mailchimp uses this for geo-targeting and address-based segmentation when those features are available on the plan.

StreetSmart asset records have no direct Mailchimp equivalent. We link assets to the customer contact as a custom text field (ASSET_REF__c) containing asset IDs or names. If assets need to be searchable in Mailchimp, they can be stored as comma-separated values on the contact or as a tagged reference list.

Employee count stored in StreetSmart on the company record maps to a custom number field (EMPLOYEE_COUNT__c) on the contact record in Mailchimp. This field supports segmentation by business size tier — for example, targeting campaigns to enterprise contacts with 500+ employees or SMB contacts with fewer than 50. The numeric format enables range-based filters in Mailchimp's segment builder without requiring additional data transformation during import.

StreetSmart uses tags or labels for categorizing contacts (by service type, customer tier, or location). Tags map to Mailchimp tags directly. If tag naming conventions differ between StreetSmart locations, we normalize them during transformation to avoid tag sprawl in Mailchimp.

StreetSmart contact notes map to a custom text field in Mailchimp. Rich text formatting strips to plain text since Mailchimp notes are plain text. If a contact has multiple notes, they concatenate with line separators. Notes do not become separate Mailchimp objects — all history sits in one field on the contact.

Mailchimp does not store files attached to contacts. We export all StreetSmart attachments (photos, signed documents, inspection reports) to a cloud storage folder and place a reference URL on the contact record as a custom field. Teams can relink files post-migration. This is disclosed upfront so no data loss surprises occur at cutover.

StreetSmart owner or assigned technician data maps to a custom text field (FSM_OWNER__c) on the Mailchimp contact. Mailchimp has no native owner/user link since contacts are audience members, not CRM records. Owner names as tags allow segmenting contacts by their assigned technician for service communications.

StreetSmart customer type values (residential, commercial, industrial, etc.) map to Mailchimp tags applied at import time. The raw value also stores in a CUSTOMER_TYPE__c merge field for filtering in reports. This dual mapping preserves both marketing segment and raw data reference.

Contract start date and contract type from StreetSmart become Mailchimp custom date and text merge fields on the contact. These support renewal reminder automation in Mailchimp — for example, triggering an email 30 days before contract end. The contract data is preserved as reference fields, not as a separate object.