Migrate from Agworld to Mailchimp

Agworld contacts with a valid email address map directly to Mailchimp subscribers. Contacts without email addresses are exported to a JSON file for manual review — Mailchimp requires an email address for every subscriber. Duplicate email addresses across Agworld contacts trigger a match-first import that preserves the most recently updated Agworld record.

Agworld stores a primary farm or company record linked to each contact. The farm name, physical address, and total managed acreage migrate as custom merge tags on the Mailchimp subscriber. Farm-level data is denormalized onto each contact so segmentation is possible without Mailchimp's API-level farm-to-contact linking.

Agworld custom properties on contact records (e.g., preferred crop type, agronomist assignment, certification status) map to Mailchimp merge tags. Each custom property requires a corresponding merge tag to be pre-created in the Mailchimp audience before import. We provide a merge tag creation guide as part of the migration plan so the audience is ready before data lands.

Agworld crop types (wheat, corn, cotton, etc.) are associated with fields rather than contacts directly. We aggregate crop types from linked fields and apply them as Mailchimp tags or merge field values on the contact. Contacts managing multiple crop types receive multiple tags for segment-based campaign targeting.

Agworld field records (boundary geometry, acreage, crop assignments) have no Mailchimp equivalent. Field data is preserved as a JSON export and referenced via the original Agworld field ID stored in a custom merge tag on the subscriber. Mailchimp segments use tags and merge field values instead of relational field data.

Agworld spray records, planting logs, and harvest activities do not map to Mailchimp. These operational records are exported as a structured JSON file keyed by Agworld job ID and contact ID. Rebuilding campaign triggers based on crop cycle stages requires manual configuration in Mailchimp Customer Journeys using merge tag values as conditions.

Agworld owner and agronomist assignments on contacts have no Mailchimp equivalent. Owner metadata is preserved as a text merge tag (Owner_Name__c equivalent) for reference, but Mailchimp does not support record-level user assignments — campaigns are sent to subscribers, not assigned to staff within the platform.

Agworld stores attachments on jobs and field records. Mailchimp has no attachment storage per subscriber. Attachments are excluded from the migration and noted in the audit log. Any attachments needed for email campaigns must be hosted externally and linked in campaign content.

Agworld contact addresses include state, region, and postal code. We extract the state-level region and write it as a merge tag so Mailchimp segments can group subscribers by growing region. Regional segmentation supports state-specific agronomic recommendations and seasonal campaign timing aligned with regional crop calendars.

Agworld has no explicit unsubscribe flag in the contact object. All imported contacts land as Mailchimp subscribed status. If Agworld data includes bounced or inactive contacts identified by export criteria, those receive a bounced or archived Mailchimp status based on documented source flags.