Migrate from MobiWork to Mailchimp

MobiWork stores customers and prospects in a unified contact table with a status flag. Every record maps directly to a Mailchimp contact. The contact's status (active, prospect) is preserved as a tag or merge field. During migration, we validate each email address for deliverability and flag any duplicates for review before import to ensure a clean audience.

MobiWork customer segments (e.g., 'Commercial Pools', 'Residential HVAC') translate to Mailchimp tags. Multiple segments per contact result in multiple tags. Mailchimp's tag-based segmentation replaces MobiWork's segment filters. We also map each segment to a descriptive tag name and optionally prefix tags with a category identifier for easier filtering. This preserves the original grouping logic while enabling Mailchimp's advanced segmentation features.

Work order IDs and status references are preserved as text merge fields on the contact record for traceability. Mailchimp has no native work-order object; operational context must be stored as reference data. If you require detailed work order history, consider exporting the full work order log separately and linking it via the MW_CUSTOMER_ID merge field for future reference in external reporting tools.

Quote totals, dates, and status values migrate as custom merge fields on the contact. Mailchimp cannot render quotes or line items; this is reference data only. These fields enable you to segment contacts by quote status (e.g., Draft, Sent, Accepted) and to trigger follow-up campaigns based on quote activity. However, the actual quote documents remain in MobiWork and must be accessed there.

Invoice reference data migrates as merge fields. Mailchimp has no invoice object. Payment history and amounts are not displayable in email content without third-party tools. We map the most recent invoice date and total to dedicated merge fields so you can create audience segments based on payment recency and value. For full transactional history, a separate export from MobiWork is recommended.

MobiWork employees with customer-facing roles are evaluated for inclusion. If an employee is also a MobiWork customer (e.g., a contractor who receives service), they appear as a contact. Pure internal employees do not migrate. This selective migration ensures your Mailchimp audience contains only contacts who may engage with marketing emails, preventing internal-only records from inflating subscriber counts.

MobiWork customer addresses map to Mailchimp's structured address fields (ADDR1, ADDR2, CITY, STATE, ZIP, COUNTRY). Multiple service locations per customer collapse to the primary address unless additional merge fields are created. If you need to preserve secondary location details, we can add custom address merge fields (e.g., SECONDARY_ADDR) and populate them from MobiWork's additional address records. This maintains address richness for segmented campaigns.

Routing data, dispatch configurations, and scheduling rules are field-service operational constructs with no Mailchimp equivalent. They do not migrate and must be rebuilt as Mailchimp automation triggers if desired. For example, you can create a Mailchimp automation triggered by a tag set during work order scheduling to send a follow-up email after service completion.

Payment records, transaction history, and Clearent/Stripe payment links are operational data outside Mailchimp's scope. Payment integration is handled separately from the email marketing platform. If you need to include payment confirmation details in your campaigns, consider exporting transaction data and attaching it as a PDF or linking to a secure portal via a custom merge field. This keeps your Mailchimp audience focused on marketing while payment data remains accessible elsewhere.

Parts catalog, inventory levels, and equipment records are MobiWork operational data with no Mailchimp equivalent. These do not migrate. If you need to inform customers about parts availability or service reminders based on equipment type, consider exporting the relevant inventory subset and linking it to contacts via the MW_CUSTOMER_ID merge field for external reporting or dynamic content in emails.

Any MobiWork custom fields on the customer record require corresponding merge fields in Mailchimp before import. Merge fields are audience-specific; each audience needs its own merge field setup. If your list includes many custom fields, we prioritize the most operationally relevant ones and document any overflow for future integration via the MW_CUSTOMER_ID reference. This ensures a clean import while preserving a path for additional data later.

Service contract status (active, expired) and renewal dates migrate as a tag and date merge field. Recurring service logic requires rebuilding in Mailchimp Customer Journeys. You can use the migrated contract-end-date merge field to trigger automated renewal reminders, follow-up offers, or upsell campaigns based on the customer's contract timeline. This rebuilds the recurring service workflow within Mailchimp's automation ecosystem.