HoneyBook to Salesforce migration
We migrate Contacts, Projects, Invoices, Contracts, and Proposals from HoneyBook into Salesforce with project-to-Opportunity mapping resolved up front, pipeline stage logic preserved, and every HoneyBook field matched to a typed Salesforce field before cutover.
FlitStack AI migrates account and contacts, contacts, opportunity or custom objects, opportunity stage + sales process and custom object or opportunitylineitems from HoneyBook to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

What moves from HoneyBook to Salesforce?
Moving from HoneyBook to Salesforce is a structural migration from a client-centric flat model to a relational CRM with separate Account, Contact, Opportunity, and custom object structures.
Read the full summary
HoneyBook organizes work around Projects and Inquiries tied directly to Clients; Salesforce separates Accounts (companies), Contacts (people), and Opportunities (deals) with explicit lookup relationships. We resolve project-to-Opportunity mapping during scoping, preserve pipeline stage history in Salesforce Sales Processes, and handle HoneyBook's CSV-only export constraint by building connector fallbacks and chunked data extraction from internal views. HoneyBook automations, templates, and file attachments do not migrate as code; we deliver a written inventory for admin rebuild.
Client → Account and Contact (split required)
HoneyBook Clients are person-centric records containing both company and individual data.
How it maps
We split each Client into a Salesforce Account (using the company name field if present) and a Salesforce Contact (using the client name and email). If no company name exists on the HoneyBook Client, the Contact is created as an Individual Account (a Salesforce Person Account or an Account with no Website). The original HoneyBook Client ID is preserved in a custom field hb_client_id__c on both Account and Contact for reconciliation.
Contact (CSV export) → Contact
HoneyBook's native CSV export from Clients > Contacts includes name, email, phone, address, notes, and creation date.
How it maps
We ingest this CSV directly and map each row to Salesforce Contact. Email becomes Contact.Email, phone becomes Contact.Phone, address fields map to Contact.MailingAddress components. The hb_original_createdate__c custom field preserves the HoneyBook creation timestamp.
Project → Opportunity or Custom Object (Project__c)
HoneyBook Projects are the primary work container, linking Clients to pipeline stages, custom fields, files, and invoices.
How it maps
We map Projects to Salesforce Opportunity when the project maps to a sales deal (Proposal Sent, Booked stages). For Projects representing ongoing retainer work or service delivery without a clear close date, we create a custom object Project__c with a lookup to Account and the original pipeline stage preserved in hb_pipeline_stage__c. The customer chooses the strategy during scoping based on their reporting needs.
Pipeline Stage → Opportunity Stage + Sales Process
HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, etc.) with stage-move timestamps.
How it maps
We create a Salesforce Sales Process with corresponding StageName values for each HoneyBook pipeline stage. Stage probabilities migrate from HoneyBook (if configured) to Salesforce StageProbability. Closed dates and stage-move history migrate as Salesforce OpportunityFieldHistory or a custom stage_timeline__c object.
Invoice → Custom Object (Invoice__c) or OpportunityLineItem
HoneyBook invoices include line items, payment status, amounts, and client associations.
How it maps
We extract invoice records via CSV export or scraped invoice list views, then map to a custom Invoice__c object with fields: hb_invoice_id__c, Invoice_Number__c, Amount__c, Status__c (Open, Paid, Overdue, Void), Due_Date__c, and a lookup to Account and Contact. Open invoices preserve their original HoneyBook status for the customer's accounting team to reconcile against the destination accounting system.
Contract → ContentDocument + Custom Fields (Contract__c)
HoneyBook Contracts are template-based documents with client associations and e-signature status.
How it maps
We export contract metadata (client, template name, status, date) to a custom Contract__c object with hb_contract_id__c, Template_Name__c, Status__c, Signed_Date__c, and a lookup to Account. The contract PDF content migrates as a Salesforce ContentDocument attached via ContentDocumentLink to the Account or Contact record.
- ClientAccount and Contactsplit
- ContactContact1:1
- ProjectOpportunity or Custom Object1:1
- Pipeline StageOpportunity Stagetransformed
- InvoiceCustom Object or OpportunityLineItem1:1
- ContractContentDocument1:1
+ 8 more in the mapping below
How HoneyBook and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | HoneyBook | Salesforce |
|---|---|---|
| Data model | Client-centric: Projects and Inquiries link directly to Clients with no Account-Contact separation | Relational: Accounts (companies) own Contacts (people) which link to Opportunities (deals) |
| Pipeline structure | Single pipeline with configurable stages per project | Multiple Sales Processes with Record Types, stage probabilities, and stage-specific actions |
| Pricing model | Flat-rate per subscription tier ($29-$129/month), no per-seat billing | Per-user per month ($25-$165/user/month depending on edition) |
| API access | No public REST or bulk API; CSV export for contacts only | Full REST API and Bulk API 2.0 with documented rate limits and OAuth 2.0 authentication |
| Custom objects | Custom fields on Contacts and Projects; no independent custom object type | Full custom object support (__c API) from Professional tier |
| Invoice handling | Native invoice and payment processing with processing fees on every transaction | Invoice and payment data migrates as custom objects; payment processing requires separate setup |
| Automations | Automation engine for email triggers, questionnaire delivery, booking confirmations | Salesforce Flow (record-triggered, scheduled, screen); automations do not migrate as code |
What to watch for in a HoneyBook to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
HoneyBook has no bulk API requiring CSV extraction
HoneyBook exposes no public REST, GraphQL, or bulk API for programmatic data extraction.
How we handle it
The only native export is a CSV of contacts from Clients > Contacts. All other data — projects, invoices, contracts, proposals, pipeline history, team members — must be scraped from the web interface or extracted via Zapier integrations with limited field coverage. We mitigate this by running an authenticated export session, downloading available CSVs, and using HoneyBook's internal data views to reconstruct project and financial records. Customers should be aware that this process takes longer than API-based migrations and may require a longer scoping window to validate data completeness.
Lead-Contact-Account model requires explicit mapping design
HoneyBook Clients are person-centric records without an explicit Account-Contact separation.
How we handle it
Salesforce requires Accounts (companies) to own Contacts (people) with Opportunities linked to Accounts. We split HoneyBook Clients into Salesforce Accounts and Contacts during migration, but the mapping strategy (when does a Client become an Account vs a Person Account vs a Contact under an existing Account) must be defined during scoping. Migrations that skip this design step end up with orphaned Contacts or duplicated Accounts.
Payment and invoice data requires accounting reconciliation
HoneyBook charges payment processing fees on every transaction, and bank transfers take 7-8 days to clear with a 'Payment Attempted' status before settlement.
How we handle it
When importing payment history to Salesforce custom objects, we mark records with their original HoneyBook timestamp rather than the settlement date to avoid confusing a 'Payment Attempted' status with a completed payment. The customer's accounting team should reconcile migrated invoices and payments against their destination accounting system before closing the HoneyBook account.
HoneyBook automations and templates do not migrate as code
HoneyBook automations (email triggers, questionnaire flows, booking confirmations) and document templates are rule-based and stored server-side with no export mechanism.
How we handle it
We deliver a written inventory of every active automation and template for the customer's admin to rebuild in Salesforce Flow and Salesforce Docs or a third-party document generation tool. HoneyBook Balance (a checking account product tied to the subscription) is outside migration scope and must be closed or transferred directly with HoneyBook support.
Salesforce field validation rules can block CSV import
Salesforce orgs commonly enforce validation rules (required formats, conditional requireds, picklist whitelists) and field-level security that can cause record rejection during data load.
How we handle it
We coordinate with the customer's Salesforce admin to grant migration credentials the required permissions, and we either temporarily disable validation rules during load or extend them with a migration-context check. Skipping this step typically results in 5-30 percent record rejection on the first import attempt, requiring reprocessing.
How the migration runs
Discovery and export strategy
We audit the source HoneyBook account across subscription tier, active custom fields, pipeline stage count, project volume, invoice and payment history, team member count, and any active automations.
What this step covers
Because HoneyBook has no bulk API, we map out the exact extraction path for each object: CSV download for contacts, scraped invoice list views for financial records, project export for pipeline history. The discovery output is a written migration scope with extraction sequencing and a Salesforce edition recommendation (Starter Suite at $25/user, Professional at $80/user, or Enterprise at $165/user).
Account-Contact split design
We design the destination schema in Salesforce, including the Account-Contact mapping strategy for HoneyBook Clients.
What this step covers
This involves deciding whether each HoneyBook Client becomes a Salesforce Account (Person Account or Business Account), a Contact under an existing Account, or a split between Account and Contact. We provision any required custom objects (Project__c, Invoice__c, Payment__c, Contract__c, Questionnaire__c) with their custom fields, lookups, and validation rules. Schema is deployed via Salesforce metadata API into a Sandbox org first for validation.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-like data volume.
What this step covers
The customer reconciles record counts (Accounts in, Contacts in, Opportunities or Projects in, Invoices in), spot-checks 25-50 random records against the HoneyBook source, and validates that the Account-Contact split produces the expected hierarchy. Any mapping corrections happen in Sandbox before production migration begins.
Owner and team member reconciliation
We extract every distinct HoneyBook team member referenced on Projects, Invoices, and Contracts and match by email against the Salesforce destination org's User table.
What this step covers
Collaborators without a matching Salesforce User are mapped to Contact records with a custom collaborator flag. The customer's Salesforce admin provisions any missing Users before record import resumes because OwnerId references are required on most standard objects.
Production migration in dependency order
We run production migration in record-dependency order: Users (validated), Accounts (from HoneyBook Clients with company name), Contacts (from HoneyBook Clients without company name or as split records), Custom Objects schema (Project__c, Invoice__c, Payment__c), Projects (mapped to Opportunity or Project__c), Invoices, Contracts, Proposals, Questionnaires, Team Members, and Files (via ContentVersion upload and ContentDocumentLink).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation handoff
We freeze HoneyBook writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We deliver the Automation and Template inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild HoneyBook automations as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.
HoneyBook - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, CSV extraction scope, and custom object count. HoneyBook's lack of a bulk API means we invest additional scoping time in building connector fallbacks, which affects the lower bound. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for HoneyBook to Salesforce →Why teams move from HoneyBook to Salesforce
- HoneyBook's 2025 price increases nearly doubled the Starter tier from $19 to $36/month and pushed Premium to $129/month, prompting freelancers and small service businesses on fixed margins to evaluate alternatives. Salesforce's per-user model at $25/user/month on Starter Suite offers a more predictable cost structure for teams that only need core CRM functionality without HoneyBook's bundled payment processing and clientflow tools.
- HoneyBook has no public bulk API or documented export endpoints. All data extraction relies on manual CSV downloads of contacts or Zapier-based connectors that miss project history, attachment metadata, and invoice records. Salesforce's full REST and Bulk API 2.0 eliminates this extraction bottleneck permanently and enables ongoing bidirectional sync if needed.
- HoneyBook is designed for U.S. and Canadian creative independents and lacks multi-currency, multi-language, and international tax compliance features. Growing agencies and consultancies serving international clients move to Salesforce for its multi-currency support, localized data formats, and global data residency options across its cloud infrastructure.
- HoneyBook's opinionated clientflow model constrains advanced CRM needs like custom objects, complex lead scoring, multi-tier pipelines, territory management, and advanced forecasting. Salesforce's data model accommodates these requirements from Professional tier without forcing a workaround, making it the destination of choice for agencies scaling beyond the solopreneur tier.
- HoneyBook lacks native SMS capabilities and has limited email marketing features compared to dedicated marketing automation tools. Teams that need rich formatted email campaigns, SMS outreach, and marketing automation move to Salesforce for its native Sales Cloud features plus the Marketing Cloud and Marketing Cloud Account Engagement (Pardot) ecosystem available within the same platform family.
Questions, answered
HoneyBook to Salesforce migration questions
How long does a HoneyBook to Salesforce migration take?
Most migrations land between four and eight weeks for accounts under 15,000 contacts and 3,000 projects with a straightforward Account-Contact split strategy. Migrations with multiple project pipelines, large invoice and payment histories, questionnaire data (mapped to custom objects), or multiple team members move to ten to sixteen weeks because of manual CSV extraction scope, custom object schema design, and Salesforce Sandbox validation cycles. HoneyBook's lack of a bulk API is the primary variable affecting timeline.
Do HoneyBook automations and templates migrate to Salesforce?
No. HoneyBook automations (email triggers, questionnaire flows, booking confirmations) and document templates are rule-based and stored server-side with no export mechanism. We do not migrate them as code. We deliver a written inventory of every active HoneyBook automation and template with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration.
Can we keep HoneyBook for payments while moving CRM to Salesforce?
Yes. A hybrid stack is a common pattern for businesses that want to retain HoneyBook's payment processing while moving client management and pipeline tracking to Salesforce. In this scenario, we migrate all CRM records (Contacts, Accounts, Opportunities, Projects, pipeline stages) to Salesforce and create a custom Payment__c object that can receive new payment records via a HoneyBook-to-Salesforce Zapier integration or a custom API integration post-migration. Existing HoneyBook payment history migrates as historical records on the custom object.
Do we lose historical pipeline and project data?
No. We extract pipeline stage history from HoneyBook's project views and migrate it to Salesforce OpportunityFieldHistory or a custom stage_timeline__c object. Project custom fields, associated contacts, invoice links, and file attachments migrate to the destination object (Opportunity or Project__c) with all original metadata preserved. HoneyBook Balance (checking account product) is outside migration scope and must be handled separately with HoneyBook support.
How do we handle the Account-Contact split for HoneyBook's person-centric Clients?
HoneyBook Clients are person-centric records without an explicit company-person separation. We split each Client during migration based on a strategy defined during scoping: if the Client has a company name, we create a Salesforce Account (business) and a Contact under it; if the Client is an individual without a company, we create a Salesforce Person Account or an Account with no Website and a Contact under it. The original HoneyBook Client ID is preserved in hb_client_id__c on both records for reconciliation. The customer chooses the split strategy based on their Salesforce org configuration (Person Accounts enabled or not).
What happens to HoneyBook contracts and proposals during migration?
Contract and proposal metadata (client, template name, status, date, amount) migrate to Salesforce custom objects (Contract__c, Proposal__c or Quote) with a lookup to Account and Contact. The PDF content migrates as Salesforce ContentDocument records attached via ContentDocumentLink to the parent Account or Contact. E-signature status and signing URLs from HoneyBook are preserved as custom fields, but the actual e-signature workflow does not replicate in Salesforce and must be reconfigured in Salesforce's native e-signature tools or a third-party like DocuSign.
Can FlitStack AI also handle moving our team collaboration data (collaborators, questionnaires) to Salesforce?
Yes. HoneyBook collaborators (external team members with limited project access) migrate as Salesforce Contact records with a custom hb_collaborator__c flag and a lookup to the Account. HoneyBook questionnaires and their response history migrate as two custom objects: Questionnaire__c (template structure) and Questionnaire_Response__c (client responses linked to Account and Project__c). The customer defines during scoping whether to store questionnaire responses as repeating custom fields or as a JSON blob on the response record.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → FotoNotes to SalesforceMapping · history · rollbackHousecall Pro to SalesforceMapping · history · rollbackDaylite to SalesforceMapping · history · rollbackCustomer.io to SalesforceMapping · history · rollbackmonday CRM to SalesforceMapping · history · rollbackFreshsales to SalesforceMapping · history · rollback HoneyBook to PipedriveMapping · history · rollbackHoneyBook to HubSpotMapping · history · rollbackHoneyBook to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from HoneyBook to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote