Migrate from Atollon Lagoon CRM to Mailchimp

Atollon Folders (individual contact records) map directly to Mailchimp Contacts. The Folder's full name becomes the contact's FULLNAME merge field; email becomes EMAIL; phone becomes PHONE. Folder classification columns (client, potential client, partner) map to Mailchimp Tags applied per contact. Folder status (active/inactive) maps to Mailchimp opt-in status. We use the Mailchimp Members API endpoint to create or update contacts and apply tags in the same batch operation.

Atollon Firms are company-level records that may link to multiple Folders (contacts). We map the Firm name to the COMPANY merge field on each related Mailchimp Contact. The Firm's classification and address data (street, city, country) map to additional merge fields (COMPANY_NAME, BUSINESS_ADDRESS, CITY, COUNTRY) that we configure in the Mailchimp audience before migration. If a Firm has no linked Folders, it is held in a reconciliation queue for the customer to decide whether to create standalone contacts or merge into existing records.

Atollon Activities (calls, emails, meetings, tasks) are engagement records linked to Folders or Firms. Mailchimp does not have structured activity objects; we migrate the most recent 10-20 activity entries per contact as Contact Notes in reverse-chronological order, preserving the activity type, timestamp, and a brief description. Full activity history that exceeds the note cap is omitted from the standard scope and documented in a separate engagement history inventory for the customer's admin to review.

Atollon Custom Forms attached to Folders store field values in formvalue records linked by formID. We parse each formvalue record, resolve the field schema via formID, and create corresponding Merge Fields in the Mailchimp audience before importing. Text fields map to text Merge Fields; date fields to date Merge Fields; dropdowns to dropdown Merge Fields. One-to-many formvalue relationships (one Folder with multiple form submissions) map to the most recent form submission, with earlier values documented as historical note entries.

Atollon Campaign management is an Ultimate-tier feature with no Mailchimp API migration path because the campaign action model differs (Atollon sequences steps against targets; Mailchimp Customer Journeys use trigger-based branching). We extract Atollon campaign names, target audience descriptions, and send dates as a written inventory delivered to the customer's admin. The admin rebuilds campaigns in Mailchimp Customer Journeys using the inventory as a reference; we do not export campaign content or automate the rebuild.

Atollon Projects (Contracts, Business cases, Service contracts, Consultations) are project management records with no Mailchimp equivalent. Mailchimp has no project, contract, or service record object. We flag the existence and count of Projects in the discovery phase, extract project names and linked Firm references as a written inventory, and recommend the customer export the project list to a project management tool (Notion, Asana, ClickUp) post-migration if the data is required.

Atollon's Service and support module manages ticket-like records with status, priority, and assigned agent fields. Mailchimp does not have a support ticket or case object. We extract the total count and status distribution of service records during discovery and hold them for the customer to export manually or migrate to a dedicated helpdesk platform (Zendesk, Freshdesk) as a separate project.

Atollon Milestones track timeline checkpoints within Projects or Activities, potentially carrying custom form data. Mailchimp has no milestone or timeline checkpoint object. Milestone records with custom form values are parsed (where applicable) and merged into the related Contact Notes; standalone Milestones without a contact link are documented in the written inventory and excluded from the Mailchimp migration scope.

Atollon Workflow Automations (Advanced tier, EUR 496+/month) sequence business process steps and are not accessible via API. Mailchimp Customer Journeys use a different trigger-and-condition model. We do not migrate automation rules as code. We deliver a written inventory of every active Atollon Workflow with its trigger, conditions, and action sequence, along with a recommendation for the equivalent Mailchimp Customer Journey setup. The customer's admin rebuilds the automation in Mailchimp using this guide.

Atollon invoicing generates invoices linked to Projects or Firms with line items, amounts, and payment status. Mailchimp has no invoice, billing, or financial record object. Invoice header data (invoice number, total amount, currency, status) is documented as a written export for the customer's finance team to review. Detailed financial history migration depends on the customer's accounting system (NetSuite, QuickBooks, Xero) and is outside the standard Mailchimp migration scope.