---
title: "HoneyBook to Dynamics 365 Migration | FlitStack AI"
description: "Migrate HoneyBook to Dynamics 365 with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/honeybook/to/dynamics-365-sales"
---

# HoneyBook to Dynamics 365 migration

We migrate Contacts, Projects, Invoices, and Contracts from HoneyBook into Microsoft Microsoft Dynamics 365 Sales with the client-centric to account-centric schema bridge resolved during scoping, Pipeline stage logic mapped to Opportunity stages, and every HoneyBook record type placed in the correct Dataverse entity before cutover.

Short answer

FlitStack AI migrates contacts, accounts, opportunities, opportunity stages and opportunity product line items from HoneyBook to Dynamics 365, 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: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/honeybook/to/dynamics-365-sales#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source HoneyBook ![](https://flitstack.ai/platforms-trim/honeybook.webp)

Destination Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Contact Account Opportunity Opportunity Stage Opportunity Product Line Item

Mapped field by field · sample run · one-click rollback

## What moves from HoneyBook to Dynamics 365?

Moving from HoneyBook to Microsoft Microsoft Dynamics 365 Sales is a platform migration with a significant schema mismatch to resolve upfront.

Read the full summary

HoneyBook organizes around clients and Projects with embedded invoices, contracts, and proposals; Microsoft Dynamics 365 Sales organizes around Accounts, Contacts, and Opportunities with separate modules for contract and invoice management. We bridge this by treating HoneyBook Projects as Opportunities with rich notes, preserving client records as Contacts attached to Accounts, and flagging invoice and contract records that require a Dynamics 365 Business Central instance or a third-party contract management tool on the destination side. HoneyBook has no public API, so all source data extraction relies on CSV export and authenticated session extraction, which extends scoping timelines. Workflows, questionnaire flows, and automation rules do not migrate; we deliver a written inventory for the customer's admin to rebuild in Microsoft Dynamics 365 Sales or Power Automate.

1:1

### Contact → Contact

HoneyBook Contacts export as CSV via Clients > Contacts and include name, email, phone, address, notes, and creation date.

How it maps

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.

1:1

### Company → Account

HoneyBook's Company records (business clients versus individual contacts) map to Microsoft Dynamics 365 Sales Account.

How it maps

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.

1:1

### Project → Opportunity

HoneyBook Projects are the primary work container, containing inquiries, pipeline stages, custom fields, files, and client associations.

How it maps

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.

configuration

### Pipeline Stage → Opportunity Stage

HoneyBook pipelines have configurable stages (Inquiry, Follow Up, Proposal Sent, Booked, Completed, etc.) with stage move-time tracking.

How it maps

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.

1:N split

### Invoice → Opportunity Product Line Item (or Dynamics 365 Business Central Invoice)

HoneyBook invoices include line items, payment status, amounts, and client associations.

How it maps

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.

configuration

### Contract → Opportunity (with Contract entity or SharePoint document)

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) 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.

******What moves 10 objects

HoneyBook Dynamics 365

- Contact Contact 1:1
- Company Account 1:1
- Project Opportunity 1:1
- Pipeline Stage Opportunity Stage transformed
- Invoice Opportunity Product Line Item split
- Contract Opportunity transformed

\+ 4 more in the mapping below

## How HoneyBook and Dynamics 365 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                                                                                                         | Dynamics 365                                                                                                         |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Data model orientation | Client-centric: Projects contain all client activity, invoices, contracts, and files                              | Account-centric: Accounts (Companies) and Contacts are separate from Opportunities and Activities                    |
| Invoicing              | Native invoice creation, payment tracking, and processing inside the project                                      | Sales Lite handles basic quotes; full invoicing requires Business Central or third-party CPQ                         |
| API access             | No public REST or GraphQL API; CSV export for contacts only, authenticated session extraction for everything else | Full Dataverse API (REST/OData) with Bulk API for high-volume ingestion and rate-limit controls                      |
| Pipeline model         | Project pipeline with configurable stages and move-time tracking                                                  | Opportunity stages via Sales Process with stage probability and record type scoping                                  |
| Automation             | Rule-based automations for client touchpoints, questionnaire flows, and booking confirmations                     | Power Automate for cloud flows; Sales Hub workflows for record-triggered sequences                                   |
| File attachments       | Session-bound URLs; files not publicly accessible                                                                 | SharePoint or Dataverse file storage with direct URL access                                                          |
| Pricing model          | Flat per-seat subscription with payment processing fees on transactions                                           | Per-user per-month subscription (Sales Lite from $65/user, Sales Pro from $105/user) with Azure infrastructure costs |

## What to watch for in a HoneyBook to Dynamics 365 migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### HoneyBook has no public API for automated export

HoneyBook exposes no public REST or GraphQL API for bulk 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 — must be extracted via authenticated session scraping or Zapier integrations. 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 is slower than API-based migrations and may require a longer scoping window. File attachments use session-bound URLs that expire and are not publicly accessible, requiring direct download during the extraction window.

high

### Microsoft Dynamics 365 Sales lacks native invoicing

Microsoft Microsoft Dynamics 365 Sales does not include native invoice generation or payment tracking — that functionality lives in Dynamics 365 Business Central (ERP) or requires a third-party CPQ application.

How we handle it

HoneyBook combines CRM, invoicing, and payment processing in a single workflow. During migration, we preserve invoice records as Opportunity-level custom fields or coordinate a parallel Business Central migration for proper invoice accounting. If the customer requires invoice and payment history to live inside Dynamics without Business Central, we document the gap and recommend a CPQ or invoice management ISV from AppExchange.

medium

### HoneyBook Project model does not map directly to a single Dynamics object

HoneyBook Projects are composite work containers that combine project scope, financial line items, client communications, files, and pipeline status in one record.

How we handle it

Microsoft Dynamics 365 Sales separates these concerns: the Opportunity holds deal information, the Quote holds proposals, notes hold communications, and SharePoint holds files. We resolve this by mapping each HoneyBook Project to one Opportunity with all associated metadata in custom fields. This requires upfront schema design to capture the full project context, and the customer's admin should validate that the Opportunity form layout surfaces all migrated project data after cutover.

medium

### Microsoft Dynamics 365 Sales Dataverse API rate limits require batch management

Microsoft Dataverse enforces service protection limits (6,000 requests per five minutes per user for web API) and daily request allocations based on license count.

How we handle it

Large migrations exceeding these limits return HTTP 429 throttling responses. We mitigate this by using Dataverse batch operations with $batch requests, implementing exponential backoff with Retry-After header handling, and chunking large record sets into manageable batches. We monitor request counts against the allocation during migration to avoid throttling that would stall the migration window.

medium

### Automations and questionnaire flows do not migrate

HoneyBook automations (email triggers, questionnaire flows, booking confirmations, follow-up reminders) are rule-based and stored server-side with no export mechanism.

How we handle it

Microsoft Dynamics 365 Sales does not have a direct equivalent to HoneyBook's client-facing automation triggers. We do not migrate automations as code. We deliver a written inventory of every active HoneyBook automation with its trigger, conditions, and actions, and recommend Power Automate or Microsoft Dynamics 365 Sales workflows as rebuild targets. Questionnaire intake forms are documented for rebuilding as Power Apps portals or Dynamics 365 Customer Voice.

## How the migration runs

1. ### Discovery and source extraction assessment

   We audit the HoneyBook account for record volume across Contacts, Companies, Projects, Invoices, Contracts, Proposals, Payments, and custom fields.

   What this step covers

   Because HoneyBook has no public API, we assess which records export via CSV (Contacts only), which require authenticated session extraction (Projects, Invoices, Contracts, Proposals), and which are stored in session-bound URLs (Files). We also assess Microsoft Dynamics 365 Sales environment readiness: tenant, license type (Sales Lite or Sales Pro), existing Dataverse schema, and any Business Central instance that would absorb invoice and payment records. The discovery output is a written migration scope and a source extraction plan.

2. ### Source data extraction and cleansing

   We run authenticated export sessions against HoneyBook, downloading contact CSVs and reconstructing project, invoice, contract, and proposal records from HoneyBook's web interface.

   What this step covers

   We flag duplicate contacts, incomplete addresses, and records with missing required fields before mapping. Any HoneyBook Balance checking account is flagged separately as a banking product outside standard record migration scope. File attachments are downloaded during this window before session URLs expire. We produce a source data quality report identifying records requiring customer-side cleanup before mapping.

3. ### Dataverse schema design and Opportunity modeling

   We design the destination schema in Microsoft Dynamics 365 Sales .

   What this step covers

   This includes pre-creating all custom fields (mapped from HoneyBook custom fields), configuring Opportunity Stages and Sales Processes to match HoneyBook pipeline stages, setting up Account and Contact record types, and defining custom fields to capture invoice metadata and payment status for records that have no native Dynamics equivalent. If the customer has Business Central, we coordinate the schema to share Contact and Account data across both environments via Dataverse. Schema is deployed to a Sandbox environment first for validation.

4. ### Sandbox migration and reconciliation

   We run a full migration into a Microsoft Dynamics 365 Sales Sandbox using production-like data volume.

   What this step covers

   The customer's admin reconciles record counts (Contacts in, Accounts in, Opportunities in), spot-checks 25-50 random records against the HoneyBook source, and validates that Opportunity stages, custom field values, and project metadata are correctly placed. Any mapping corrections and schema adjustments happen here. We also validate that file attachments are accessible in SharePoint or Dataverse document storage and that contract and proposal PDFs render correctly.

5. ### Owner reconciliation and User provisioning

   We extract every distinct HoneyBook team member referenced on Projects, Invoices, Contracts, and other records and match by email against the Microsoft Dynamics 365 Sales destination User table.

   What this step covers

   Collaborators without a matching Dynamics User are flagged for the customer's admin to provision. Migration cannot proceed past record import because OwnerId references are required on Opportunities and many standard entities.

6. ### Production migration and automation handoff

   We run production migration in dependency order: Users (validated), Accounts (from HoneyBook Companies), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and stage resolved), Quotes, custom fields, and payment metadata.

   What this step covers

   Files and documents load to SharePoint or Dataverse. We freeze HoneyBook writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the Automation and Questionnaire inventory document to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild HoneyBook automations in Power Automate inside the migration scope.

![](https://flitstack.ai/platforms/honeybook.png) HoneyBook ![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Dynamics 365 Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**8-12 weeks** Large or heavily customised accounts

A quote scales with record volume, source extraction complexity, and schema gap resolution. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for HoneyBook to Dynamics 365 →](https://flitstack.ai/contact)

## Why teams move from HoneyBook to Dynamics 365

- HoneyBook executed significant price increases in 2025 — Starter nearly doubled from $19 to $36/month and Premium reached $129/month — prompting customers on thin margins to evaluate alternatives. Reviewers on G2 and Capterra cite the 2025 pricing as the tipping point for switching to a platform with predictable per-user licensing and enterprise-tier capabilities at a comparable price.
- HoneyBook has no public bulk API for programmatic data extraction. All data beyond basic contact CSV must be scraped from authenticated web sessions or extracted via Zapier integrations that may miss historical records. Microsoft Microsoft Dynamics 365 Sales offers a full Dataverse REST and OData API with Bulk API support for high-volume ingestion, enabling cleaner and faster ongoing integrations after migration.
- Growing agencies and small service businesses outgrow HoneyBook's CRM depth. Advanced CRM requirements — custom objects, complex lead scoring, multi-tier pipelines, territory management, and multi-currency support — are not well supported in HoneyBook. Microsoft Dynamics 365 Sales Professional ($105/user) and Enterprise ($150/user) tiers support these capabilities natively without third-party plugins.
- Microsoft ecosystem integration is a primary driver for mid-market migrations to Microsoft Dynamics 365 Sales . Native connectivity to Outlook, Teams, SharePoint, Excel, Power BI, and Azure Active Directory provides a unified productivity environment that standalone CRMs cannot match. Organizations already using Microsoft 365 for productivity gain immediate value from the tight integration.
- HoneyBook's automations are rule-based and server-side with no export mechanism, while Microsoft Dynamics 365 Sales pairs with Power Automate for cloud flows and Power Apps for custom interfaces. Organizations requiring sophisticated workflow automation, approval chains, and cross-system triggers benefit from the Power Platform ecosystem that extends Microsoft Dynamics 365 Sales well beyond HoneyBook's automation scope.

Questions, answered

## HoneyBook to Dynamics 365 migration questions

How long does a HoneyBook to Microsoft Microsoft Dynamics 365 Sales migration take?

Most migrations land between three and five weeks for accounts under 10,000 contacts and 2,000 projects with no Business Central coordination. Migrations with large financial histories (over 1,000 invoices), extensive file attachments, or a requirement to model HoneyBook Projects across multiple Dynamics entities (Opportunity plus Business Central Invoice) move to eight to twelve weeks because of authenticated session extraction time, Dataverse schema design, and invoice-accounting gap resolution. HoneyBook's lack of a public API extends extraction timelines compared to API-based migrations.

Do HoneyBook Automations and Questionnaire Flows migrate to Microsoft Dynamics 365 Sales ?

No. HoneyBook automations (email triggers, questionnaire flows, booking confirmations, follow-up reminders) are rule-based and stored server-side with no export mechanism. Microsoft Dynamics 365 Sales uses a different automation model — Power Automate for cloud flows and Sales Hub workflows for record-triggered sequences. We do not migrate automations as code. We deliver a written inventory of every active HoneyBook automation and questionnaire with its trigger, conditions, and actions, plus a recommended Power Automate rebuild approach. The customer's admin or a Microsoft partner rebuilds them post-migration.

Where do my HoneyBook Invoices and Payments go in Microsoft Dynamics 365 Sales ?

Microsoft Dynamics 365 Sales does not include native invoice generation or payment tracking — that functionality is in Dynamics 365 Business Central (the ERP layer) or requires a third-party CPQ application. For migrations targeting Sales-only, we preserve invoice records as Opportunity-level custom fields and payment status as a custom field on the Opportunity. For customers needing full accounting, we coordinate a parallel Business Central migration to handle invoice ledger entries and payment reconciliation. We flag this gap during scoping so the customer can decide whether a Sales-only migration or a Sales-plus-Business Central migration is the right scope.

Can we keep HoneyBook alongside Microsoft Dynamics 365 Sales for a transition period?

Yes, a dual-system transition is possible but requires careful coordination. During the transition window, new Projects and Invoices created in HoneyBook would not flow to Dynamics unless a Power Automate integration is built. We recommend cutting over to Microsoft Dynamics 365 Sales as the system of record on a defined date and running HoneyBook in read-only mode for 30 days post-cutover to reference historical data. Any new contracts or invoices created in HoneyBook during the window would need manual entry into Dynamics or a separate data entry scope.

Do we lose Project history and pipeline stage move dates?

No. We preserve the full Project history including pipeline stage move timestamps. Each HoneyBook Pipeline Stage change is captured as a date-stamped custom field on the corresponding Microsoft Dynamics 365 Sales Opportunity (e.g., stage\_inquiry\_date\_\_c, stage\_proposal\_sent\_date\_\_c). This preserves the historical timeline that HoneyBook tracks natively, even though Microsoft Dynamics 365 Sales does not store stage move dates in the same structure. The customer's admin surfaces this history in Dynamics views or a Power BI report post-migration.

What happens to HoneyBook Balance (the checking account product)?

HoneyBook Balance is a checking account product tied to the HoneyBook subscription (pending eligibility). It is not a standard platform record — it is an external bank account that customers may have connected within HoneyBook. We flag HoneyBook Balance separately during migration scoping and advise customers to coordinate directly with HoneyBook support to close or transfer the Balance account. It falls outside the scope of standard CRM record migration and must be handled as a separate banking relationship.

What file types and attachments migrate from HoneyBook?

HoneyBook stores files in a library (images, PDFs, brand assets) and attaches them to Projects, Contracts, and Proposals. File URLs in HoneyBook are session-bound and not publicly accessible, meaning they expire when the export session ends. We handle file migration by downloading attachments during the active extraction window and uploading them to SharePoint or Dataverse document storage. PDF contracts and proposal documents migrate as document records linked to the Opportunity or Account. We flag any files that cannot be retrieved before session expiry for customer-side resolution.

## Related migrations

[![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp) Migrate to **Dynamics 365** Every source we move into Dynamics 365, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/dynamics-365-sales)

### [Dynamics 365 implementation](https://flitstack.ai/services/dynamics-365-implementation)

[Set up Dynamics 365 and migrate into it as one engagement.](https://flitstack.ai/services/dynamics-365-implementation)

[See the service →](https://flitstack.ai/services/dynamics-365-implementation) [**Housecall Pro to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/dynamics-365-sales) [**Attio to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/dynamics-365-sales) [**Twenty CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/dynamics-365-sales) [**Leadforce CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/leadforce-crm/to/dynamics-365-sales) [**Close to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/dynamics-365-sales) [**Jobber to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/dynamics-365-sales) [**HoneyBook to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/pipedrive) [**HoneyBook to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/hubspot) [**HoneyBook to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
2. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
3. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)
4. [Execute Batch Operations on Dataverse — Microsoft Learn](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/execute-batch-operations-using-web-api)
5. [Service protection limits (Microsoft Dataverse)](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/api-limits)
6. [Entity relationship behavior — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/entity-relationship-behavior?view=op-9-1)

Get a quote

## Moving from HoneyBook to Dynamics 365?

Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
