Migrate from HoneyBook to monday CRM

HoneyBook Contacts export as a CSV from Clients > Contacts and include name, email, phone, address, notes, and creation date. We map each CSV row to a Monday.com People board Item, creating the Person record first so that any project or invoice associations can reference it as a Lookups column. HoneyBook custom fields on contacts migrate as additional columns on the Person Item.

HoneyBook Projects contain inquiry details, pipeline stage, custom fields, files, and associated contacts. We extract project metadata and stage history via HoneyBook's pipeline view (scraped or iterated manually) and map each project to a Monday.com board Item with the project name as Item Name, stage as the status column, and custom fields mapped to typed columns. Associated contacts are linked via a Lookups column pointing to the Person Item.

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, Completed) with stage move timestamps. We map each HoneyBook stage to a Monday.com Status column value, preserving the stage order. Stage move timestamps from HoneyBook's history log are stored as a Timeline column or date columns in Monday.com to preserve the project journey. We flag any non-standard stage names for renaming during Monday.com onboarding.

HoneyBook invoices include line items, payment status, amounts, and client associations. Monday.com CRM has no native invoicing object, so we pre-create an Invoice custom Object with columns for invoice number, client (linked to Person Item via Lookups), line items, amount, status, and payment date. We extract invoice records via HoneyBook's invoice list view and map them into the custom Object. Open invoices are flagged for customer admin review before closing out HoneyBook.

HoneyBook contracts are template-based documents with client associations and signature status. Monday.com has no native contract or e-signature feature. We extract contract metadata (client, template name, status, date) and map it to a Contract custom Object or a dedicated Contracts board Item. Signed PDFs and contract files are re-uploaded to Monday.com Files and attached via the Files column or Content wrapper. We flag DocuSign-connected contracts for admin review since Monday.com does not have a native e-signature integration.

HoneyBook payment records include amount, method, status, and processing date. We extract payment history via the HoneyBook dashboard export and map it to a Payment custom Object in Monday.com with a linked Invoice reference. Bank transfer payments in HoneyBook show a 'Payment Attempted' status for 7-8 days before settlement; we mark these records with their original HoneyBook timestamp rather than the settlement date to avoid misrepresenting payment status in Monday.com.

HoneyBook automations (email triggers, questionnaire delivery, booking confirmations, follow-up reminders) are server-side rule-based workflows with no export mechanism. Monday.com automations use a different trigger-and-action model with per-board trigger events and conditional steps. We do not migrate automations as code. We deliver a written inventory of every active HoneyBook automation including its trigger, conditions, actions, and a recommended Monday.com automation equivalent with trigger step, action steps, and board scope documented for the customer's admin to rebuild post-migration.

HoneyBook stores files in a library (images, PDFs, brand assets) and uses templates for contracts and proposals. File URLs in HoneyBook are session-bound and not publicly accessible via direct URL, which means we cannot programmatically fetch them. We advise customers to download their HoneyBook file library before migration begins. Uploaded files are re-hosted in Monday.com Files and attached to the relevant board Item or custom Object via the Files column. Template files migrate as regular attachments and the customer rebuilds template-based documents from scratch in Monday.com.

HoneyBook client questionnaires are linked to projects and serve as intake forms. We export questionnaire structure and response history as structured data. Each questionnaire maps to a Custom Object with text columns for each question and linked Person and Project Items. Alternatively, we create a dedicated Forms board with items representing each questionnaire response. The questionnaire structure (questions, order, type) is preserved in a separate Setup item within the board for admin reference.