Migrate from Resco – Mobility & Productivity to Mailchimp

Resco Contact records map to Mailchimp subscribers within an Audience. We map standard fields: First Name to FNAME, Last Name to LNAME, Email Address to EMAIL (the primary key in Mailchimp), Phone to PHONE, and Job Title to COMPANY (via merge field). Any custom contact properties configured in the underlying CRM migrate as Mailchimp merge fields (maximum 40 per Audience). We resolve duplicate emails using Mailchimp's upsert behavior: existing subscribers with matching EMAIL are updated; new subscribers are created.

Resco Account records contribute to the COMPANY merge field on the corresponding Contact's Mailchimp subscriber profile. Company address fields (street, city, state, zip, country) migrate as additional merge fields if the underlying CRM exposes them. We do not create a separate Company object in Mailchimp because Mailchimp's data model is subscriber-centric, not account-centric. Account-level segmentation requirements are handled via tag assignment post-migration.

Resco marketing lists (static explicit record sets or dynamic query results against Accounts, Contacts, or Leads) do not migrate directly because Resco's native export to Mailchimp was discontinued. We deliver a written inventory of every Resco marketing list with its membership criteria (entity type, query conditions, or explicit record IDs) and recommend Mailchimp Audience or Segment equivalents. The customer or a Mailchimp partner rebuilds the lists in Mailchimp using the exported record identifiers as seed data for manual list building.

If the underlying CRM (Dynamics 365 or Salesforce) has Lead records synced through Resco, they migrate as Mailchimp subscribers with Lead-specific fields (Lead Source, Lead Score, Status) mapped to custom merge fields. Lead status values (New, Open, Qualified, Converted) migrate as tag assignments rather than native Mailchimp fields. Converted Leads that have already become Contacts in the CRM do not duplicate in Mailchimp — we resolve by CRM Contact ID dedupe to avoid double-importing the same email address.

Engagement history (calls logged in the field, email interactions, meeting records, completed tasks) has no Mailchimp equivalent. Mailchimp tracks subscriber engagement through opens, clicks, and campaign delivery — it does not accept historical CRM activity records as a data type. We document the volume and date range of engagement records in the source system and flag that this history does not migrate. The customer can establish Mailchimp engagement tracking from the cutover date forward.

Work orders are Resco Field Service+ entities with no Mailchimp equivalent. Mailchimp is an email marketing platform, not a field service or job management tool. Work order records (status, assignment, line items, associated photos) are excluded from migration scope. We document the total work order count and date range as a written inventory for the customer's records; if the customer retains a separate field service system, we provide the export file for independent archival.

Inspection templates and response data configured in Woodford are Resco-specific artifacts. Mailchimp has no survey, inspection, or questionnaire data model. We export the questionnaire definitions as JSON schema files and response data as CSV files for the customer's independent archival. Any questionnaire response data linked to Contacts is noted as a separate export with the Contact email as a reference key for future reconciliation if the customer implements a survey tool.

Location tracking records stored in Resco's Mobile Auditing entity have no Mailchimp equivalent. These records track field worker GPS positions over time and are owned by the initiating user, not by CRM entities. We export the record set as a CSV with user identity and timestamp columns for the customer's audit archive. Mailchimp does not support location-based subscriber segmentation beyond city/state country merge fields.

Route plans are optimized sequences of work orders or inspections generated by Resco's routing engine. They are configuration data rather than transactional records and are regenerated from scratch when the routing engine runs. Mailchimp has no route-planning capability. Route plan configurations are excluded from migration scope; we deliver a written summary of active route plan templates (name, assigned users, stop sequence) as a handoff document for the customer's operations team if they implement a dedicated routing solution.

Custom entities created in Woodford (mobile form designer) are mapped as part of the Resco project but have no Mailchimp equivalent. Mailchimp supports only the standard subscriber data model. Any custom Resco entities not mirrored in the underlying CRM require explicit archival decisions: we export them as CSV or JSON and document the schema for the customer to reference if a future system accepts the data. Custom entity record counts are included in the migration inventory.