Migrate from HoneyBook to Mailchimp

HoneyBook contacts export as a CSV from Clients > Contacts and include name, email, phone, address, notes, and creation date. HoneyBook stores the full name in a single field; Mailchimp uses separate FNAME and LNAME merge fields. We split the combined name at migration time, using the first space as the boundary between first and last name. Any contacts without a valid email address are flagged in a separate report because Mailchimp requires a valid email address for subscriber records. Merge fields from HoneyBook custom fields map to Mailchimp merge fields where the field type is compatible (text, number, date, phone, address, URL). Dropdown and multi-select custom fields that Mailchimp does not support natively become tags in the format 'CF: FieldName = Value'.

HoneyBook company records have no direct Mailchimp equivalent because Mailchimp does not maintain an Account object separate from contacts. We map the company name to the COMPANY merge field on the contact record and apply a tag using the company name (for example, tag 'Company: Acme Photography') so that audience segments can be built by company. If multiple contacts share the same company name in HoneyBook, they receive the same tag in Mailchimp. Company-level reporting in Mailchimp relies on tag-based segmentation rather than a parent-child relationship.

HoneyBook projects contain inquiries, pipeline stages, custom fields, files, and associated contacts. Mailchimp has no project or pipeline object, so projects cannot be created as native records in the destination. We tag each contact with a tag reflecting their associated HoneyBook project membership using the format 'Project: [Project Name]' so that project context is preserved as audience segmentation in Mailchimp. The full project list (project name, stage, client association, stage history timestamps) is exported to a separate Project Inventory CSV for the customer's reference. Customers who rely on HoneyBook projects for project management need to handle this function in a separate tool post-migration.

HoneyBook invoices include line items, payment status, amounts, and client associations. Mailchimp has no invoice or payment object. We extract open invoice metadata (client name, invoice number, amount, status, issue date, due date) to a separate Invoice Inventory CSV for the customer's accounts-receivable team to process manually in their new payment tool. Closed invoices (settled payments) are not migrated because the financial record remains in HoneyBook for audit purposes. Auto-payment profiles connected to HoneyBook invoices are flagged during discovery and must be redirected to the customer's new payment processor before cutover to prevent duplicate or failed charges.

HoneyBook contracts store template-based documents with client associations and e-signature status. Mailchimp has no contract object. We extract contract metadata (client name, template name, status, date signed, signature method) to a Contract Inventory CSV. Contract PDF files are session-bound and not publicly accessible via a direct URL, making programmatic file extraction unreliable. Customers should manually download active contract PDFs from HoneyBook before or after cutover. The Contract Inventory CSV documents which contracts require this manual step.

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, Completed) with move-time tracking per project. Mailchimp does not support pipeline or project-stage objects. Stage history and timestamps are included in the Project Inventory CSV exported alongside the contact migration. Customers who need to preserve pipeline context use the project inventory and contact project-tags as a written reference rather than a live record.

HoneyBook custom fields on contacts support mixed field types. Mailchimp merge fields support eight types: text, number, date, phone, address, URL, dropdown, and radio. During discovery we audit every active HoneyBook custom field, classify each by type, and map compatible types directly to Mailchimp merge fields. Dropdown fields become Mailchimp dropdown merge fields; radio fields become radio merge fields. Multi-select, checkbox, and file-type custom fields that Mailchimp does not support become tags in the format 'CF: [Field Name] = [Value]' applied to the contact at import time.

HoneyBook distinguishes between collaborators (external, limited access) and team members (internal). Team members who are also HoneyBook client contacts migrate as Mailchimp contacts with a ROLE merge field capturing their internal role. Staff-only team members (no associated client contact) have no direct Mailchimp equivalent and are exported to a Team Member Inventory CSV for manual Mailchimp admin user setup post-migration. HoneyBook Balance checking account holders must coordinate with HoneyBook support to close or transfer the account separately, as it is a banking product outside the scope of standard record migration.