Migrate from HoneyBook to Twenty CRM

HoneyBook contacts export as a CSV from Clients > Contacts and include name, email, phone, address, notes, and creation date. We ingest this CSV and map each row to a Twenty Person record, preserving the original HoneyBook contact ID in a custom field hb_contact_id__c for audit and cross-reference. Any contact records with duplicate emails are flagged during scoping for manual resolution before import.

HoneyBook projects represent client inquiries and contain pipeline stage, custom fields, associated contacts, and project metadata. We extract project metadata from HoneyBook's pipeline view and map each project to a Twenty Opportunity record. The HoneyBook pipeline stage becomes the Opportunity stage, with a custom field hb_project_id__c and hb_pipeline_stage__c preserving the original HoneyBook stage name and move timestamp for historical accuracy.

HoneyBook's configurable pipeline stages (Inquiry, Follow Up, Proposal Sent, Booked, etc.) with stage-move timestamps are mapped to Twenty Opportunity stage values. We configure Twenty's opportunityPipeline setting to mirror HoneyBook's stage names and probabilities, and we preserve the stage history as a JSON array in a custom field hb_stage_history__c on the Opportunity.

HoneyBook invoices include line items, payment status, amounts, and client associations. We extract invoice records via CSV export or HoneyBook's invoice list view, then create a custom Invoice object in Twenty with fields for invoice_number, amount, status, line_items (JSON), and linked_hb_project_id. Each invoice links to the corresponding Opportunity via a custom lookup field. Open invoices requiring continued payment processing are flagged separately.

HoneyBook contracts are template-based documents with client associations and e-signature status. We extract contract metadata (client, template name, status, date, signature status) and store it as a structured custom field block on the linked Twenty Opportunity: hb_contract_status__c, hb_contract_template__c, hb_signed_date__c, hb_signature_provider__c. The actual contract PDF requires separate file handling (see Files note).

HoneyBook proposals are project-level documents combining scope, pricing, and terms. We extract proposal records and map them to the linked Opportunity's custom fields: hb_proposal_status__c, hb_proposal_amount__c, hb_proposal_sent_date__c, hb_proposal_response__c. Proposal documents themselves require separate file migration handling.

HoneyBook payment records include amount, method, status, and processing date. We extract payment history and map to the custom Invoice object with fields for amount, method, status (Completed, Pending, Refunded), and processing_date. We preserve the original HoneyBook timestamp for bank transfers (which carry a 7-8 day clearing window) rather than the settlement date to avoid conflating Payment Attempted with Completed status.

HoneyBook supports custom fields on contacts and projects. We identify all active custom fields during discovery, export their values alongside the parent record, and create matching custom fields in Twenty via Settings → Data Model before import. Custom fields must exist in Twenty before CSV import begins; import will reject records referencing non-existent fields.

HoneyBook distinguishes collaborators (external, limited project access) from team members (internal). We export team member records including roles and permissions, then map internal team members to Twenty WorkspaceMembers. Collaborators without a Twenty user account are mapped to a custom field hb_collaborator__c on the relevant records. The customer provisions Twenty users before migration so that Owner and assignee lookups are satisfied at import time.

HoneyBook automations (email triggers, questionnaire flows, booking confirmations) are rule-based and stored server-side with no export mechanism. Twenty CRM's own migration documentation explicitly states that views, workflows, and permissions must be recreated manually after import. We do not migrate automations as code. We deliver a written inventory of every active HoneyBook automation with its trigger conditions, actions, and recommended manual rebuild steps for Twenty. This inventory is provided as a handoff document for the customer's admin.

HoneyBook stores files in a library (images, PDFs, brand assets) and attaches them to projects and contracts. File URLs are session-bound and not publicly accessible. We handle file migration by downloading attachments during an authenticated session and storing them in a customer-provided storage location (S3, Google Drive, Dropbox), then recording the file URL in a custom field on the relevant Twenty record. File migration is scoped separately from record migration.