Migrate from Urban-Hawks to Mailchimp

Urban Hawks Contact records map to Mailchimp audience members by email address match. Phone, name, and address fields map to Mailchimp's native merge fields (FNAME, LNAME, PHONE, ADDRESS). Primary company association becomes a merge field value. The migration uses the email address as the unique identifier for deduplication across both platforms.

Urban Hawks Company name, industry, and website become Mailchimp merge fields (COMPANY, INDUSTRY, WEBSITE) attached to each contact record. Parent-child company hierarchies in Urban Hawks are flattened into a single company merge field value per contact. Secondary company associations are surfaced as tags for segmentation flexibility.

Work order status (Open, In Progress, Completed, Invoiced) becomes a Mailchimp tag applied to the contact so you can segment by service stage. Work order type (Maintenance, Repair, Installation) becomes a separate tag or merge field value for campaign targeting. Each status transition can trigger segmentation logic in Mailchimp automations.

Last service date and service type are stored as merge fields (LASTSERVICE, SERVICETYPE) on the audience member. Multiple service types per contact are reflected as separate tags so re-engagement automations can target specific maintenance categories. This enables segmentation like contacts with HVAC service tags for seasonal follow-up campaigns.

Contract status (Active, Expired, Pending) and contract end date map to merge fields (CONTRACTSTATUS, CONTRACTEND) on the audience member. These drive renewal-campaign segmentation logic in Mailchimp automations. Expiration dates enable date-based triggers for 60/30/7-day renewal outreach sequences.

Urban Hawks assigns technicians to contacts or work orders. The assigned technician name maps to a merge field (TECHNICIAN) so you can attribute service communications or send technician-specific follow-up campaigns from Mailchimp. This preserves the customer-technician relationship for post-service satisfaction surveys.

Open quotes map to merge fields (QUOTESTATUS, QUOTEAMOUNT) that trigger Mailchimp automations for follow-up on proposals. Accepted quotes become tags for segmentation into customer lifecycle campaigns. Pending quotes enable re-engagement sequences for stalled deals.

Urban Hawks inventory tracking (parts, equipment, stock levels) has no Mailchimp equivalent. This data is not migrated. It is noted in the migration plan for rebuilding as internal operational records outside Mailchimp, such as in inventory management or ERP systems.

Urban Hawks dispatch assignments and GPS route logs are field operations data with no Mailchimp analog. These records are excluded from migration. The technician name association is preserved via merge field on the contact, but granular routing and scheduling data cannot be represented in Mailchimp.

Urban Hawks custom fields on Contact objects (license number, preferred service area, equipment type) map to Mailchimp custom merge fields. Text, number, date, and phone field types translate directly. Pick-list values require value-mapping setup per field in Mailchimp admin before migration runs.

Invoice payment status (Paid, Overdue, Pending) becomes a Mailchimp tag on the contact. This enables payment follow-up automation sequences in Mailchimp triggered by tag application. Tags can drive dunning campaigns for overdue invoices without manual intervention.

Urban Hawks email opt-in flag maps to Mailchimp subscriber status. Contacts marked as opted-in become subscribed members. Unsubscribed contacts are imported to Mailchimp suppression list to protect deliverability and prevent bounce penalties from affecting sender reputation.

Urban Hawks contacts with no active work order or quote are migrated as Mailchimp unsubscribed members. This allows you to trigger re-engagement automation campaigns targeting cold prospects without violating Mailchimp deliverability standards or spam regulations.

Urban Hawks time tracking records (technician clock-in/out, job duration) are internal operations data with no Mailchimp equivalent. These records are excluded from migration scope. Time tracking remains in Urban Hawks or your field operations system for payroll and job costing purposes.