Migrate from Aidoo Mobile to Mailchimp

Aidoo Mobile customer records map directly to Mailchimp contacts within a single audience. Each unique email address creates one Mailchimp contact. Customers with no email address are flagged before migration because Mailchimp requires a valid email for each subscriber. Duplicates arising from multiple service-location records sharing the same email are resolved by the pre-migration deduplication pass.

Aidoo Mobile contact records merge with their parent customer record when both share the same email address. The resulting Mailchimp contact inherits the customer's service-location address if the contact record lacks its own address. This merge ensures that only one contact exists per email while preserving the most relevant location information for each subscriber.

Aidoo Mobile stores separate address records per service location. Mailchimp contacts hold one address per subscriber. When multiple locations share the same contact email, FlitStack preserves the most recently updated address and stores the others as a text merge field for reference.

Aidoo Mobile custom properties on customer records — such as service_type, contract_tier, or preferred_contact_method — are converted to Mailchimp merge fields. Text properties map directly, date properties are reformatted to YYYY-MM-DD, and boolean properties become Yes/No strings. This transformation preserves the original data semantics within Mailchimp's contact model.

Aidoo Mobile work order fields such as technician_name, service_type, and last_service_date are stored as merge fields on the related contact in Mailchimp. This approach preserves operational context without creating a separate work order object, since Mailchimp has no native work order concept. The contact record therefore carries both marketing and reference data.

Mailchimp has no native work order concept. The work order ID is stored as a custom text merge field (WORK_ORDER_ID__c) on the contact record for traceability. If a customer has multiple work orders, their IDs are stored as a comma-separated list within the same field, allowing quick reference without additional records.

Aidoo Mobile work order status values (Scheduled, In Progress, Completed, Cancelled) have no equivalent in Mailchimp's contact model, which tracks subscriber engagement such as opens and clicks. Because Mailchimp does not store job status, the status field is not migrated, and any operational workflow must be managed outside Mailchimp.

Aidoo Mobile technician assignments do not map to any native Mailchimp concept. The assigned technician name is stored as a custom text merge field (TECHNICIAN_NAME__c) on the contact record, allowing customer service teams to view the assigned technician directly within Mailchimp without needing to access a separate system.

If Aidoo Mobile applies customer segments or labels such as 'Premium Contract' or 'High Priority', those labels are imported as Mailchimp tags on the corresponding contacts. Tags enable audience segmentation in Mailchimp without requiring complex merge field conditions, facilitating targeted campaigns based on customer classification.

Aidoo Mobile customer-level notes are migrated as a custom text merge field (NOTES__c) on the Mailchimp contact. Because Mailchimp imposes a 150-character limit per text merge field, longer notes are truncated and flagged in the migration audit for manual review, ensuring no data loss goes unnoticed.