Migrate from HoneyBook to HubSpot

HoneyBook clients map directly to HubSpot Contacts. Name, email, phone, address, and notes fields translate to their HubSpot equivalents. The original HoneyBook client ID is stored as a custom property (Source_Client_ID__c) for delta-run de-duplication and cross-reference.

HoneyBook companies map to HubSpot Companies. Company name, website, industry, phone, and address fields migrate directly. HubSpot's N:1 contact-to-company model means each HoneyBook client with a primary company gets associated via the Company field on the Contact record.

HoneyBook projects are the equivalent of HubSpot Deals. Project name maps to Deal name, project status maps to a HubSpot Deal pipeline stage, and the project value (if set) maps to Deal amount. FlitStack creates a HubSpot Deal per HoneyBook project and associates it with the primary Contact.

HoneyBook's pipeline stages (e.g., Inquiry, Proposal Sent, Contract Signed, Active, Completed) are mapped value-by-value to HubSpot Deal stage names. If the HoneyBook account has multiple pipelines, FlitStack creates a HubSpot Deal Pipeline per HoneyBook pipeline and maps stages within each.

HoneyBook invoices contain line items, tax, discounts, and payment status. FlitStack maps the invoice total to the associated HubSpot Deal's Amount field and creates Line Item records for each invoice line. Invoice files (PDFs) are attached to the Deal as Salesforce Files-style attachments in HubSpot.

HubSpot has no native contract object. HoneyBook contracts migrate as file attachments on the associated Deal or Contact record. Contract status (Sent, Viewed, Signed, Declined) is preserved as a custom pick-list property (Contract_Status__c) on the Contact or Deal.

HoneyBook payment records (amount, date, method, status) are stored on the associated Invoice in HoneyBook. FlitStack preserves payment status as a custom property on the Line Item (Payment_Status__c: Paid, Partial, Refunded, Pending) and records the last payment date.

HoneyBook team members assigned as project or client owners are resolved by email match against HubSpot portal users. Unmatched owners are flagged before migration; the client can either invite them to HubSpot first or reassign records to a fallback HubSpot user.

HoneyBook calendar events (client calls, meetings, sessions) map to HubSpot engagements of type 'meeting'. Original start time, duration, attendee list, and meeting notes are preserved. If the event has a HoneyBook-generated video link, that URL is stored in a custom property.

HoneyBook client notes and project comments migrate as HubSpot engagement notes or as Notes on the Contact record, depending on context. Rich-text formatting in HoneyBook notes is preserved where the HubSpot API supports it. Timestamps and note authors are retained.

HoneyBook custom properties on clients (e.g., referral_source, preferred_contact_method, birthday) are created as HubSpot custom contact properties. FlitStack infers the property type from the data (string, number, date, or pick-list) and creates the HubSpot property before migration.

HoneyBook custom properties on projects (e.g., project_type, deliverable_format, revision_count) are created as HubSpot custom deal properties. Each property is type-mapped and validated against HubSpot's property API before the full run.

HoneyBook projects that are still in early pipeline stages (e.g., Inquiry or Follow Up) may represent leads that haven't converted to clients yet. FlitStack maps these to HubSpot Contacts with lifecycle_stage set to 'lead'; projects with a signed contract map to 'customer'.

HoneyBook Smart Files and reusable templates (proposals, contracts, questionnaires) have no direct HubSpot equivalent. FlitStack exports these as files and re-uploads them to HubSpot's file manager. The client rebuilds templates in HubSpot's Sales Hub template tools or documents the mapping for their admin.