Migrate from HoneyBook to Pipedrive

HoneyBook Contacts export as a CSV via Clients > Contacts and include name, email, phone, address, notes, and creation date. We ingest this CSV and map each row to a Pipedrive Person record. The contact's associated Company (if any) becomes a separate Organization in Pipedrive linked via the person_id on the Organization. HoneyBook contact tags migrate to Pipedrive custom fields as comma-separated text or multi-select picklist depending on the customer's tag strategy chosen during scoping.

HoneyBook Projects are the primary container for inquiry data, pipeline stages, custom fields, files, and associated contacts. We export project metadata and stage history via HoneyBook's pipeline view and map each project to a Pipedrive Deal. The HoneyBook Project name becomes the Deal title; the project status (Active, Archived) maps to Pipedrive's open/closed Won/Lost deal status. Stage history with move timestamps migrates to the Pipedrive Deal's stage change log preserved as custom fields.

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, Completed, Declined) with stage-level move-time tracking. We map each HoneyBook stage to a corresponding Pipedrive Pipeline Stage, creating a new Pipedrive Pipeline named after the HoneyBook pipeline if multiple pipelines exist. Stage probabilities in Pipedrive are set to match HoneyBook's implicit close rates or are left at Pipedrive defaults for the customer to tune post-migration.

HoneyBook Invoices include line items, payment status, amounts, due dates, and client associations. HoneyBook does not have a native invoice object in Pipedrive, so we map invoice records as custom fields on the corresponding Pipedrive Deal (invoice_number__c, invoice_amount__c, invoice_status__c, invoice_due_date__c, invoice_paid_date__c). Open invoices are flagged for the customer to recreate or connect via a FreshBooks or QuickBooks integration post-migration.

HoneyBook Contracts are template-based documents with client associations, signature status, and date. We export contract metadata (client, template name, status, date) and any associated PDF file URLs, then link the contract document as a file attachment to the corresponding Pipedrive Deal via the Google Drive or Dropbox integration, or as a raw file upload. Signature status migrates as a custom field contract_signature_status__c on the Deal.

HoneyBook Proposals are project-level documents combining scope, pricing, and terms. We extract proposal records and map them to the corresponding Pipedrive Deal, preserving proposal amount as the Deal value. The proposal PDF or document URL migrates as a file attachment to the Deal. Pipedrive's native Proposal tool (Google Docs integration) serves as the long-term replacement for new proposal creation post-migration.

HoneyBook Payment records include amount, method, status, and processing date. We extract payment history via the HoneyBook dashboard export and map payment status (Completed, Pending, Refunded) to deal-level custom fields (payment_amount__c, payment_method__c, payment_status__c, payment_date__c). Bank transfers with a 'Payment Attempted' status are marked with their original HoneyBook timestamp rather than the settlement date to avoid confusing an attempted payment with a completed one. Pipedrive has no native payment processing; payment tracking is informational only.

HoneyBook distinguishes between Collaborators (external, limited project access) and Team Members (internal). We export Team Member records including roles and permissions, then map to Pipedrive Users by email match. Collaborators without an email match in Pipedrive are mapped to Person records instead of Users. Any HoneyBook Team Member not yet provisioned in Pipedrive goes to a reconciliation queue for the customer's admin to create the corresponding User account before migration.

HoneyBook Automations (email triggers, questionnaire flows, booking confirmations, follow-up reminders) are rule-based and stored server-side with no export mechanism. These do not migrate. We deliver a written inventory of every active HoneyBook Automation with its trigger, conditions, actions, and recommended Pipedrive Workflow equivalent, so the customer's admin can rebuild them in Pipedrive's workflow builder starting at the Advanced tier. The automation handoff document is delivered at the close of migration.

Client questionnaires in HoneyBook 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 Pipedrive custom fields on the relevant Person or Deal. Since Pipedrive does not support custom objects, questionnaire data flattens into custom fields; the questionnaire template itself is documented for the customer to recreate in Pipedrive's form tool or a third-party alternative.

HoneyBook supports custom fields on Contacts and Projects. We identify all active custom fields during discovery, export their values alongside the parent record, and map each to a Pipedrive custom field of matching type (text, number, date, dropdown). Pipedrive custom fields attach to Person, Organization, Deal, or Product standard objects. Custom field options (dropdown values) migrate as picklist values in Pipedrive. Any HoneyBook custom fields that do not have a natural Pipedrive equivalent are flagged for the customer to either drop or map to a text custom field.