Migrate from OneHash CRM to Microsoft Dynamics 365 Sales

OneHash Lead records (with status, source, converted flag, and conversion timestamp) map directly to Microsoft Dynamics 365 Sales Lead. The DocType field names (custom fields via ERPNext Customize Form) are resolved during pre-migration schema discovery. OneHash lead_type and lead_owner fields map to LeadSource and OwnerId respectively. We create the Dynamics 365 Lead first, then run the Lead qualification and conversion as a separate post-import validation step rather than auto-converting during migration to avoid creating orphaned Contact-Account pairs.

OneHash Contact records with first_name, last_name, email_id, phone, and organization linkage map to Dynamics 365 Contact. We resolve the Organization link to a parent Account (created first) and set the Contact's AccountId at insert time to satisfy the required lookup. OneHash's DocType-level custom fields (discovered via schema introspection) map to typed Dataverse columns on Contact; unmapped custom fields are flagged in the pre-migration report and either become custom fields in Dynamics 365 or are noted as requiring manual re-entry.

OneHash Customer (organization-level record with billing and shipping addresses) maps to Dynamics 365 Account. Customer name maps to Account Name; website maps from the stored domain field. The customer_type field (Individual vs Company) maps to Account Type picklist. We create Accounts before any Contact or Opportunity import to ensure the parent lookup chain is satisfied at insert time.

OneHash Opportunity records with deal stage, amount, probability, and party linkage map to Dynamics 365 Opportunity. The pipeline stage name from OneHash maps to the target Microsoft Dynamics 365 Sales Process stage value. We build the Sales Process (a Dynamics 365 configuration entity) during the schema phase, mapping each OneHash stage name to an equivalent Dynamics 365 stage with the correct probability percentage. The parent AccountId and OwnerId are resolved at migration time via the lookup queues populated during the Accounts and Users phases.

OneHash Quotation records carry line items linked to Items, with tax templates and terms text. We map Quotation to Dynamics 365 Quote, QuoteLineItem to QuoteDetail, and the terms field to Quote Description. The quotation_to_opportunity linkage is preserved by mapping the parent Opportunity's GUID into Quote's OpportunityId field after Opportunity import completes. OneHash tax templates do not have a direct Dynamics 365 equivalent; we map the net and gross amounts and flag any tax calculation rules that require reconfiguration in Microsoft Dynamics 365 Sales tax settings.

OneHash Sales Order records with delivery and billing status flags map to Microsoft Dynamics 365 Sales Order. Order item rows map to SalesOrderDetail with ProductId and Quantity resolved via the Items mapping. Custom Item fields from OneHash DocTypes that do not exist in Dynamics 365 are flagged as requiring a Dynamics 365 custom field creation step before order line import proceeds. Order status flags (On Hold, Completed, Cancelled) map to the Dynamics 365 Status field with statecode transitions enforced.

OneHash Item records (product/service definitions with pricing, stock data, and custom attributes) map to Dynamics 365 Product2. Standard fields (item_code, item_name, standard_rate, item_group) map directly. OneHash allows extensive custom Item fields specific to the business; we discover all active custom fields during the DocType schema pass and pre-create matching Product2 custom fields (__c suffix) in Dynamics 365 before import. Price list entries map to Dynamics 365 PriceListItem linked to a PriceLevel.

OneHash allows unlimited DocType-level custom fields via ERPNext's Customize Form tool. These do not appear in standard API responses without explicit field inclusion. We run a pre-migration discovery pass that introspects each DocType's custom field definitions via the API, cataloging field names, types (Data, Int, Float, Date, Link, Select, Check), and the parent DocType. Each discovered custom field is either mapped to a typed Dynamics 365 Dataverse column or flagged as requiring a pre-import schema creation step in the target environment.

Documents attached to any OneHash DocType migrate as Dynamics 365 Annotation records (notes with file attachments). We preserve the original file name and the linked parent record's GUID. Large binary attachments may require chunked download and re-upload due to API payload limits on both sides. We flag attachments exceeding 25 MB for manual transfer with a documented file list for the customer's admin.

OneHash Owner records (the users assigned to Lead, Contact, Opportunity, and Quotation) map to Dynamics 365 User by email address. Any OneHash Owner without a matching Dynamics 365 User is held in a reconciliation queue and the customer provisions the User before record import resumes. OwnerId references on all target objects must resolve before import can complete.