Migrate from Camp Automation to Mailchimp

Camp Automation Contacts map to Mailchimp Audience Members. The Camp email, first_name, last_name, phone, and address properties map to Mailchimp's email_address, FNAME, LNAME, PHONE, and ADDRESS merge fields. Camp custom fields on Contacts require schema discovery—we prompt the customer to export the full field list from the Camp UI before migration so that we create equivalent Mailchimp merge fields with correct types (text, number, date, dropdown). Contacts without an email address are flagged during scoping because Mailchimp requires a valid email address for every Audience Member.

Camp Automation Company records do not have a direct Mailchimp object. Companies with a single primary Contact are attached as a note to that Contact record with the company name, domain, industry, and size preserved. Companies with multiple associated Contacts receive a Mailchimp Tag (format: Company: [Name]) applied to all linked Contact records so the customer can segment by company in Mailchimp. If the customer requires full Company CRM after migration, we recommend a separate CRM migration (Pipedrive, HubSpot Starter, or Less Annoying CRM) as a follow-on engagement.

Camp Automation Deals map to Notes and Tags on the associated Contact record. Deal name, value, stage, and close date are stored as a structured note text block plus a Mailchimp Tag (format: Deal: [Stage] - $[Value]). The pipeline and stage mapping is documented in the migration scope so the customer can optionally create a Google Sheets or Airtable pipeline tracker as a reference. We do not migrate Deals as structured records because Mailchimp has no pipeline object. If deal tracking is critical, a CRM migration should be scoped separately.

Camp Automation Tags migrate directly to Mailchimp Tags. We preserve the tag taxonomy exactly, including any tag prefixes (e.g., source:, segment:, deal:) that the customer uses for segmentation. Tags that do not exist in the destination Audience are created during import. Tag count is preserved so that Mailchimp segments built on tags continue to function identically after migration.

Camp Automation Campaign records that contain email assets map to Mailchimp Campaigns. We extract the email subject, HTML body (with inline CSS preserved), from name, and from email address and create a corresponding Mailchimp Campaign. Campaign send history (sent date, open count, click count) is not imported into Mailchimp's reporting because Mailchimp does not accept historical send data through its API; we deliver a CSV export of campaign performance metrics for the customer's records.

Camp Automation Campaigns with SMS assets map to Mailchimp SMS Campaigns if the destination Mailchimp account has SMS enabled (Essentials tier or above). We create SMS campaigns with the original message content, scheduled send time, and audience segment preserved. SMS campaigns sent from Camp Automation that used a specific sender ID are flagged during scoping because Mailchimp assigns its own sender ID for SMS sends.

Camp Automation Campaigns with social post assets (Facebook, Instagram, Twitter/X) and push notification assets do not map to Mailchimp because Mailchimp does not have social posting or push notification sending capabilities. We extract social post content and push notification text as structured CSV exports and tag the associated Contacts with the original campaign name. The customer rebuilds social and push campaigns in their preferred platform (Later, Buffer, or OneSignal).

Camp Automation Email Templates export as HTML with inline CSS preserved and variable placeholders intact. We create Mailchimp Saved Templates using the HTML content. Where Camp uses variable syntax like {{contact.first_name}}, we convert to Mailchimp merge tag format (*|FNAME|*). Template names and categories migrate as Template tags in Mailchimp.

Camp Automation Automation workflows define triggers (form submit, email open, email click, deal stage change, tag applied) and multi-branch action sequences. Mailchimp Customer Journeys use a different trigger and action model with entry-based triggers and linear or branching paths. We do not migrate automations as code. We deliver a written inventory of every Camp Automation with its trigger, conditions, and action sequence mapped to a recommended Mailchimp Customer Journey configuration. The customer's admin rebuilds each Journey in Mailchimp using the documented map.

Camp Automation custom fields on Contacts require schema discovery before migration because the platform does not expose field metadata through a public API. We prompt the customer to export the full field list from the Camp UI or provide a screen recording of the Contact settings page. Field types (text, number, date, dropdown, checkbox) are mapped to equivalent Mailchimp merge field types (text, number, date, dropdown, radio, birthday). Custom fields on Deals and Companies are documented in the same format and attached as note text because Mailchimp does not support custom objects.

Camp Automation Forms export with field configurations, submission data, and response counts. Mailchimp signup forms use a different builder and structure, so forms do not migrate as functional objects. We deliver a CSV export of form submission data mapped to the corresponding Mailchimp Audience, and we document the form field structure so the customer's admin can rebuild equivalent Mailchimp embedded or hosted signup forms. Form responses are appended to the relevant Audience Member records during migration.

Camp Automation Owner records (sales reps assigned to Contacts and Deals) do not map to Mailchimp because Mailchimp does not have a user-assignment model for contacts. Owner names and email addresses are preserved as a Contact note (format: Camp Owner: [Name] <email>) so that the customer can reference the original assignment if needed for a follow-on CRM migration.