Migrate from HoneyBook to Microsoft Dynamics 365 Sales

HoneyBook Contacts export as CSV via Clients > Contacts and include name, email, phone, address, notes, and creation date. We ingest this CSV directly and map each row to a Microsoft Dynamics 365 Sales Contact. The Contact's parent Account is created from the HoneyBook Company or Project name field. Any custom fields on HoneyBook Contacts are pre-mapped to custom Contact fields in Dataverse during the schema design phase.

HoneyBook's Company records (business clients versus individual contacts) map to Microsoft Dynamics 365 Sales Account. If a HoneyBook contact is not associated with a Company, we create an Account using the contact's name as the Account name and flag it for the customer's admin to merge with any duplicate Accounts created from Project records. Account Website, Industry, and Address fields map from the HoneyBook Company record.

HoneyBook Projects are the primary work container, containing inquiries, pipeline stages, custom fields, files, and client associations. We map each Project to a Microsoft Dynamics 365 Sales Opportunity. The Project name becomes the Opportunity name, the pipeline stage becomes the Opportunity StageName using a configured Sales Process, and the project value maps to Amount. Project-level custom fields migrate to custom Opportunity fields in Dataverse. The Opportunity's AccountId links to the Account created from the associated HoneyBook Company or Contact.

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, Completed, etc.) with stage move-time tracking. We map each HoneyBook stage to a Microsoft Dynamics 365 Sales Opportunity StageName within a custom Sales Process. Stage probabilities migrate to StageProbability. Any custom stage names created in HoneyBook become new Opportunity Stages in Dynamics. Stage move timestamps are preserved as a custom field on the Opportunity record.

HoneyBook invoices include line items, payment status, amounts, and client associations. Microsoft Dynamics 365 Sales does not have native invoicing — this is handled by Business Central or a third-party CPQ app. For migrations targeting Sales-only, we map HoneyBook invoice records to Opportunity Line Items (Amount reflecting invoice total) and preserve invoice metadata (invoice number, due date, payment status) in custom Opportunity fields. For customers with Business Central, we coordinate a parallel engagement to migrate invoices as proper Business Central Sales Invoice records.

HoneyBook Contracts are template-based documents with client associations and e-signature status. We export contract metadata (client, template name, status, date) and map to a Microsoft Dynamics 365 Sales Opportunity-level note with contract status fields, or to the Contract entity (available with Sales Enterprise). The contract PDF is stored in SharePoint or as a Dataverse document and linked via a URL custom field. Active contract status is preserved for renewal tracking.

HoneyBook Proposals are project-level documents combining scope, pricing, and terms tied to the pipeline. Microsoft Dynamics 365 Sales has a native Quote object at Professional tier. We map Proposal records to Salesforce-equivalent Quotes linked to the Opportunity, preserving line items, total amount, and proposal status (Draft, Sent, Accepted, Declined). The proposal PDF migrates as a document attachment.

HoneyBook Payment records include amount, method, status, and processing date. Since Microsoft Dynamics 365 Sales has no native payment tracking, we map payment records to custom fields on the Opportunity (payment_status__c, amount_paid__c, payment_method__c) and preserve the payment timeline in a related custom Activity or Note. Customers requiring full accounting should coordinate with a Business Central migration for payment ledger reconciliation.

HoneyBook distinguishes between collaborators (external, limited project access) and team members (internal). We export team member records including roles and permissions and map to Microsoft Dynamics 365 Sales User records. We resolve team members by email match. Any HoneyBook team member without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

HoneyBook supports custom fields on Contacts and Projects. We identify all active custom fields during the discovery phase, export their values alongside the parent record, and map each to a corresponding Dataverse custom field pre-created in the destination Microsoft Dynamics 365 Sales environment. Field types are mapped: text to String, number to Integer or Decimal, date to DateTime, dropdown to Option Set.