Migrate your HoneyBook data

Contacts export as a CSV via the Clients > Contacts panel and include name, email, phone, address, notes, and creation date. We ingest this CSV directly and map each row to the destination's contact record, preserving notes and custom contact-level fields.

Projects in HoneyBook contain inquiries, pipeline stages, custom fields, files, and associated contacts. We export project metadata and stage history via the pipeline view, then map stages to the destination's pipeline configuration. Attachments and embedded files are exported separately and linked by project ID.

HoneyBook invoices include line items, payment status, amounts, and client associations. We extract invoice records via CSV export where available, or by scraping the invoice list view. Open invoices require careful status mapping — paid, partial, overdue — against the destination's invoice state model.

Contracts are stored as template-based documents with client associations and signature status. We export contract metadata (client, template name, status, date) and flag any contract files that need to be migrated as binary attachments separately from the record data.

Proposals are project-level documents combining scope, pricing, and terms. They are tied to the project pipeline. We extract proposal records and map them to the destination's equivalent object, preserving total value and acceptance status.

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, etc.) with move-time tracking. We map these to the destination pipeline stages, flagging any custom stage names that need renaming.

HoneyBook automations (email triggers, questionnaire flows, booking confirmations) are rule-based and stored server-side with no export mechanism. These cannot be migrated programmatically and must be rebuilt in the destination platform manually.

Payment records include amount, method, status, and processing date. We extract payment history via the dashboard export and map payment status (Completed, Pending, Refunded) to the destination's invoice payment model. HoneyBook Balance transactions are noted as a separate ledger requiring bank account migration.

HoneyBook stores files in a library (images, PDFs, brand assets) and uses templates for contracts and proposals. File URLs are session-bound and not publicly accessible. We handle file migration by downloading through an authenticated session and re-uploading to the destination or cloud storage, preserving folder structure where possible.

HoneyBook distinguishes between collaborators (external, limited project access) and team members (internal). We export team member records including roles and permissions, then map to the destination's user model. Collaborator records are treated as contacts with a collaborator flag.

Client questionnaires are linked to projects and serve as intake forms. We export questionnaire structure and response history as structured data, mapping each question and answer pair to a custom object or contact property in the destination.

HoneyBook supports custom fields on contacts and projects. We identify all active custom fields during the discovery phase, export their values alongside the parent record, and map them to destination custom fields, flagging any field-type mismatches (e.g., dropdown vs. free text).