Migrate from Honcho CRM to Microsoft Dynamics 365 Sales

Discovery and Honcho export scoping

We audit the source Honcho CRM account via the Report Builder, extracting Leads, Deals, Companies, Contacts, and Pipeline Stages. We identify custom field definitions, pipeline stage names, owner assignments, and any QuickBooks-linked deals. We assess the export file sizes and confirm whether chunking by object type or date range is required. The discovery output is a written migration scope document that defines the object list, field mapping, and any records requiring reconciliation before migration.

Dynamics 365 environment preparation and schema pre-creation

We assess the destination Microsoft Dynamics 365 Sales edition and license type. We pre-create any missing custom fields on Lead, Contact, Account, and Opportunity via the Dataverse Web API or maker portal, matching Honcho field names and types. We configure the Sales Process and stage values to align with Honcho's pipeline structure. If the customer uses multiple Honcho pipelines, we create a corresponding Record Type per pipeline. All schema work happens in the destination sandbox or dev environment before production migration begins.

CSV parsing, field normalization, and parent-record resolution

We parse the Honcho CSV exports and normalize field values: text encoding issues, date formats, null handling, and special character escaping are resolved in this step. We reconstruct the Company-Contact relationship by resolving each Honcho Company name against the Account.Name dedupe key. We resolve Deal-to-Account lookups and Deal-to-Contact lookups using the extracted relationship columns. Any records with missing parent references are flagged and held in a reconciliation queue for the customer's admin.

Owner reconciliation and User provisioning

We extract every distinct Honcho owner referenced on Deal, Contact, and Company records and match by email against the destination Dynamics 365 User table. Owners without a matching Dynamics 365 User are listed with their email addresses and roles for the customer's admin to provision before production migration. We cannot import records with OwnerId references pointing to non-existent users — this is a required field on most Dynamics 365 entities. This step is a manual gate that requires the customer's admin to act.

Production migration in dependency order

We run the production migration in strict dependency order: Accounts (from Honcho Companies), Contacts (with AccountId resolved), Leads (with status mapped to Dynamics 365 Lead Status), Opportunities (with AccountId, OwnerId, and Sales Process resolved), Deal Timeline entries (as Task records linked to Opportunity by WhatId), and Custom Fields (last, with their data values). Each phase emits a row-count reconciliation report before the next phase begins. We use the Dataverse Web API with batch requests and retry logic on 429 rate-limit responses.

Cutover, validation, and automation handoff

We freeze Honcho CRM writes during the cutover window and run a final delta migration of any records created or modified during the migration run. We deliver a reconciliation report comparing Honcho record counts against Dynamics 365 record counts per object, with a discrepancy list for the customer to investigate. We deliver a written inventory of Honcho automation configurations (if any exist) and reporting setups requiring rebuild in Dynamics 365. We support a one-week post-cutover window for data-quality flag resolution. We do not rebuild automations or workflows as part of the standard migration scope.