Migrate from HoneyBook to Freshsales

HoneyBook Contacts export as CSV from the Clients > Contacts panel with name, email, phone, address, notes, and creation date. We ingest this CSV and map each row to a Freshsales Contact. The Freshsales Contact email field serves as the dedupe key. Any HoneyBook contact associated with a Company record gets mapped to a Freshsales Contact with the corresponding Account lookup resolved before insert.

HoneyBook Companies (business entities stored under Clients) map to Freshsales Accounts. The company name becomes Account Name, website maps to Website, and any address data migrates to the Account billing address fields. We create Accounts before Contact import so the AccountId lookup is satisfied at the moment of Contact insert.

HoneyBook Projects map to Freshsales Opportunities. Each Project's pipeline stage maps to a Freshsales Sales Process and Record Type that we configure before migration. Project custom fields migrate as Opportunity custom fields. The project value or budget maps to Amount. We preserve project creation date and last modified date as Opportunity fields for historical reference.

HoneyBook pipeline stages (Inquiry, Follow Up, Proposal Sent, Booked, etc.) map to Freshsales Opportunity Stages. Each HoneyBook Project Type becomes a Freshsales Record Type with a corresponding Sales Process that whitelists only the relevant stage values. Probability percentages map from HoneyBook stage logic to Freshsales StageProbability.

HoneyBook Invoices include line items, payment status, amounts, and client associations. We extract invoice records via available CSV exports or structured scraping. On Freshsales Growth ($9/user), invoice records with full line-item detail map to the Invoice object. On lower plans, we store invoice data as custom fields on the parent Opportunity (invoice_number, invoice_date, invoice_amount, payment_status, balance_due) and attach the invoice PDF as a Note.

HoneyBook Contracts are template-based documents with client associations and signature status. We extract contract metadata (client, template name, status, date signed) and map it to Freshsales Note records attached to the corresponding Contact or Opportunity. Contract PDF files are session-bound URLs that require separate download handling; we flag these for the customer to re-upload post-migration.

HoneyBook distinguishes between internal team members and external collaborators. We export team member records including name, email, and role, then map to Freshsales User records. Owner assignments on Projects, Invoices, and Contracts resolve by matching the team member email against Freshsales User.email. Any HoneyBook team member without a Freshsales User goes to a reconciliation queue.

HoneyBook custom fields on Contacts and Projects are identified during discovery and exported alongside their parent records. We pre-create corresponding custom fields in Freshsales (with appropriate field types — text, number, date, picklist) before migration begins. Custom field API names follow Freshsales naming conventions and are validated in a Sandbox import before production migration.