Migrate from Fergus to Mailchimp

Fergus Customer maps directly to a Mailchimp Contact. Email address is the primary key — contacts without an email address in Fergus are flagged before migration because Mailchimp requires a valid email for subscription. Phone number, address, and company name map to standard Mailchimp contact fields.

Every custom property on a Fergus Customer — such as trade type, license number, or credit limit — requires a named Merge Field in the Mailchimp Audience. TEXT merge fields handle strings; NUMBER merge fields handle numeric values; DATE merge fields handle date values. We create the merge field schema before importing contacts.

Mailchimp has no native job object. We convert Fergus job records into a tagging taxonomy: each job type (e.g., Plumbing Repair, Electrical Install) becomes a tag applied to the associated Customer-Contact. Job status (Scheduled, In Progress, Completed) becomes a tag or a TEXT merge field. Job notes become a long-text merge field or an external note linked from the contact.

Fergus custom fields on Job objects (e.g., equipment make, site conditions, permit required) map to Mailchimp Merge Fields on the Contact. Each custom field requires a named merge field in the Audience. Mailchimp TEXT merge fields are limited to 255 characters — long-text custom fields are flagged for truncation or external storage.

Fergus Quotes have no direct Mailchimp equivalent. We migrate Quote number, total amount, and status as TEXT and NUMBER merge fields on the Contact record. The full quote PDF and line-item detail cannot live inside Mailchimp — we store a link reference and recommend linking to an external document store from the contact record.

Fergus Invoices map to Contact-level merge fields for invoice number and total amount paid. Invoice line items, payments, and credits have no Mailchimp representation. We recommend connecting Fergus or your accounting tool to Mailchimp via Zapier or native integration for ongoing invoice event triggers.

Fergus Pricing Tiers assign per-customer pricing categories (e.g., Residential, Trade, Wholesale). We map each tier to a TEXT merge field (Fergus_Pricing_Tier__c) holding the tier name, and apply a Mailchimp tag (Tier: Residential) to each contact. This lets you segment Mailchimp campaigns by pricing tier.

Fergus file attachments (photos, signed quotes, permits) have no native Mailchimp equivalent. We extract attachment metadata (filename, URL, upload date) and store it as a TEXT merge field. The actual file must live in an external storage system. We can include a reference link in the contact record if Fergus provides a public URL for the attachment.

Fergus custom objects vary by customer configuration. We map each custom object field to a named Mailchimp Merge Field. Where the custom object represents a categorical value (e.g., Equipment Type, Certification Level), we also apply a Mailchimp Tag Group. Your team defines the tagging taxonomy before migration.

Fergus staff who create or own records have no direct Mailchimp equivalent. Mailchimp contacts are customers, not internal users. If you want to track which Fergus staff last updated a contact, we store that as a TEXT merge field (Last_Updated_By__c). Staff should be managed in Fergus or your HR system, not in Mailchimp.