Migrate from HoneyBook to Nutshell

HoneyBook Contacts export as a CSV from the Clients panel and include name, email, phone, address, notes, and creation date. We ingest this CSV directly and map each row to Nutshell Person records via the JSON-RPC API using the email address as the dedupe key. Custom fields on HoneyBook contacts (client type, referral source, birthday) map to Nutshell custom fields on Person. If multiple HoneyBook contacts share the same email address, we flag duplicates for the customer's review before import.

HoneyBook stores company information within the contact record or as a separate business profile. We extract company records by parsing the business name and address fields from the contact CSV, then deduplicate by domain. Each unique company domain creates one Nutshell Account record with the business name as Account.name and the domain as Account.webpage. Contacts link to their parent Account via the Nutshell Person.accountId field.

HoneyBook Projects are the primary work container and map to Nutshell Deals. Each Project contains an inquiry, pipeline stage, associated contacts, custom fields, and financial records. We reconstruct the project list by scraping the pipeline view or extracting from HoneyBook's internal project list if accessible. The HoneyBook pipeline stage maps to a Nutshell Pipeline Stage (New, Contacted, Qualified, Proposal Sent, Won, Lost), and we either match existing stage names or create new stages that reflect the customer's HoneyBook stage names.

HoneyBook supports custom fields on projects including text fields, date fields, dropdowns, and checkboxes. We identify all active project-level custom fields during discovery, export their values alongside the project metadata, and map each to a corresponding Nutshell custom field on the Deal object. Custom field type mapping converts HoneyBook dropdown values to Nutshell dropdown options and preserves checkbox states as true/false strings.

HoneyBook Invoices include line items, payment status, amounts, tax, and client associations. Nutshell has no native Invoice object, so we store invoice metadata as a formatted Note on the parent Deal. The Note body contains invoice number, line items, amounts, payment status (Paid, Partial, Overdue), and date. Open invoices (unpaid or partially paid) are flagged for the customer to recreate in their accounting tool post-migration. We do not migrate invoice PDFs as native records; these are flagged for manual upload to the Account or Deal as ContentDocument attachments.

HoneyBook contracts are template-based documents with client associations and signature status. We export contract metadata (client name, template name, status, date) and flag any contract files that need separate download. Contract PDFs cannot be programmatically migrated because HoneyBook file URLs are session-bound. We deliver a manifest of all contract records with their associated Account and Deal, and the customer uploads the actual PDF files manually post-migration. The contract metadata (status, date, template name) migrates as a Note on the Deal.

HoneyBook Proposals are project-level documents combining scope, pricing, and terms. They are tied to the project pipeline. We extract proposal records including the client, project association, proposal date, and status (Draft, Sent, Viewed, Accepted, Declined). Each proposal migrates as a Note on the corresponding Nutshell Deal, with the Note title set to the proposal name and the body containing the proposal content if accessible via export. Proposal PDFs follow the same constraint as contracts and are flagged for manual upload.

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, etc.) with move-time tracking. We map these to Nutshell Pipeline Stages by name match where possible, creating new Nutshell stages for any HoneyBook stage names that do not exist in the destination. The stage probability percentages are set on Nutshell's stage configuration. If the customer has multiple HoneyBook pipelines (Premium tier feature), we map each to a separate Nutshell pipeline and assign the relevant Deal to the correct pipeline at import time.

HoneyBook distinguishes between collaborators (external, limited project access) and team members (internal). We export team member records including name, email, and role. Each team member maps to a Nutshell User record, resolved by email match. Collaborators without an email in the destination Nutshell account are flagged for the customer to provision as User records before the migration phase begins. Owner assignments on Projects and Deals resolve to the mapped Nutshell User ownerId.

HoneyBook payment records include amount, method, status, and processing date. Bank transfers show a 'Payment Attempted' status for 7-8 days while clearing. We extract payment history via the dashboard export and map payment status (Completed, Pending, Refunded, Payment Attempted) to a formatted Note on the parent Deal. We preserve the original HoneyBook timestamp rather than the settlement date for 'Payment Attempted' records to avoid misclassifying them as completed payments. Payment method and processing fee details are stored in the Note for audit purposes.