Migrate from HoneyBook to HighLevel

HoneyBook Contacts export as a CSV from the Clients > Contacts panel, including name, email, phone, address, notes, and creation date. We ingest this CSV and map each row to a GoHighLevel Contact record, using email as the dedupe key. Any Contact without an email address is flagged for manual review because GoHighLevel requires an email for workflow triggers and email marketing. Active HoneyBook custom fields on contacts are pre-created as custom fields in GoHighLevel before import.

HoneyBook Projects map to GoHighLevel Opportunities. Each Project carries inquiry details, associated contacts, custom fields, stage history, and linked invoices. We extract project metadata via HoneyBook's pipeline view and reconstruct the record for GoHighLevel. The Pipeline stage name in HoneyBook (e.g., 'Inquiry', 'Follow Up', 'Proposal Sent', 'Booked') maps to the equivalent GoHighLevel pipeline stage. Project value and close date transfer to Opportunity Amount and Close Date.

HoneyBook's pipeline stages are configurable and include move-time timestamps. We map each HoneyBook stage to a corresponding GoHighLevel pipeline stage, preserving stage order and probability if set. Custom stage names from HoneyBook are replicated as custom stage labels in GoHighLevel's pipeline builder. The migration team configures the GoHighLevel pipeline in the account before Opportunities are written.

HoneyBook invoices include line items, payment status, amounts, and client associations. We extract invoice records via HoneyBook's invoice list view where available, or reconstruct from project financial records. Invoice status (Paid, Partial, Overdue, Draft) maps to GoHighLevel Invoice status. Line items transfer as invoice line entries. Note that GoHighLevel invoices are part of the Payments add-on module — we confirm this is active on the destination account during scoping.

HoneyBook contracts are template-based documents with client associations and e-signature status. We export contract metadata — client name, template used, status, and date — and map it to a GoHighLevel Custom Object (Contract) with fields for client reference, template name, and signature status. The actual contract PDF is not migratable through GoHighLevel's API as a document upload; we flag the file for the customer to re-upload manually to the associated Contact or Opportunity record post-migration.

Proposals in HoneyBook are project-level documents combining scope, pricing, and terms. We export proposal metadata (client, project, status, amount, date) and map it to a GoHighLevel Opportunity Note or a Custom Object (Proposal) depending on the customer's reporting needs. The proposal PDF follows the same handling as contracts — flagged for manual re-upload to the associated Opportunity.

HoneyBook distinguishes between collaborators (external, limited project access) and team members (internal, full access). We export team member records including name, email, and role. Each team member maps to a GoHighLevel User, using email as the match key. Collaborators without an email in HoneyBook are flagged for manual review. Permissions are noted as a text inventory because HoneyBook role permissions do not have a direct GoHighLevel equivalent — the customer's admin configures GoHighLevel user roles post-migration.

HoneyBook supports custom fields on contacts and projects. During discovery we identify all active custom fields and their field types (text, number, date, dropdown). We pre-create each custom field in GoHighLevel with the equivalent field type before any record import begins. Field values transfer alongside their parent record (Contact or Opportunity) using GoHighLevel's custom field API support on the Contact and Opportunity objects.

HoneyBook automations (email triggers, questionnaire flows, booking confirmations) are rule-based and stored server-side with no export mechanism. We do not migrate automations as code. We deliver a written inventory of every active HoneyBook automation with its trigger, conditions, and actions. The customer's admin rebuilds these in GoHighLevel's Workflow builder, which uses a different trigger-and-action model. The inventory document includes a recommended GoHighLevel Workflow equivalent for each automation.

Client questionnaires in HoneyBook serve as intake forms linked to projects. We export questionnaire structure and response history as structured data — question text and answer pairs — and map them to a GoHighLevel Custom Object (Questionnaire Responses) with fields for contact reference, project reference, question, and answer. The questionnaire form itself does not migrate; GoHighLevel Forms replace it and the customer rebuilds the intake form there.