Migrate from webCRM to Microsoft Dynamics 365 Sales

webCRM Organisations map to Microsoft Dynamics 365 Sales Account records. We extract Organisation ID, name, address fields, industry, website, and any custom fields during the Overviews export. The Organisation name becomes Account Name and we use Organisation ID as a reference anchor during Contact linking. webCRM does not expose a GUID export in Overviews, so we deduplicate by Organisation name and store the original webCRM identifier in a custom field webcrm_organisation_id__c on Account.

webCRM Contacts link to Organisations and map to Microsoft Dynamics 365 Sales Contact records. We export both objects together and match Contacts to Accounts by Organisation name during the import phase. Email address is the primary dedupe key. Mobile, phone, job title, and any custom fields map individually. Contact ownership resolves via the HubSpot Owner email match pattern against Microsoft Dynamics 365 Sales User records.

webCRM Deals represent pipeline opportunities tied to Organisations and Contacts. We map Deal stages to Microsoft Dynamics 365 Sales Opportunity StageName values during scoping. The pipeline assignment in webCRM becomes a Microsoft Dynamics 365 Sales Record Type or Sales Process that we configure before import. Closed-won and closed-lost dates, deal amounts, and probability fields migrate directly. We preserve the original webCRM deal ID in webcrm_deal_id__c for reconciliation.

webCRM pipelines with custom stage names map to Microsoft Dynamics 365 Sales Record Types on Opportunity, each with its own Sales Process that whitelists the relevant StageName values. Stage probability percentages migrate to StageProbability on each stage. We configure these in the destination Sandbox before production migration.

webCRM Deliveries are exported in webCRM Delivery XML format via the Zynk connector. The nested XML structure with parent Delivery records and child line-item detail requires flattening into two Dataverse entities: SalesOrderHeader and SalesOrderDetail (or their equivalent Order and Order Product records depending on the Microsoft Dynamics 365 Sales edition in use). We parse the XML, separate header fields (delivery date, delivery address, Organisation reference) from line-item fields (product, quantity, unit price, tax), and reconstruct them as parent-child relationships in Microsoft Dynamics 365 Sales .

webCRM Product Database records with pricing and inventory fields map to Microsoft Dynamics 365 Sales Product2. Product code, name, description, standard price, and any product-level custom fields migrate directly. Pricebook2 entries are created during import so that Products can be associated with Opportunities and Orders at the line-item level.

webCRM Tasks linked to Organisations or Contacts migrate to Microsoft Dynamics 365 Sales Task records. Task Subject, Description, due date, priority, and status map directly. Status label translation is applied where webCRM status labels differ from Microsoft Dynamics 365 Sales TaskStatus values. Activity timelines are ordered by the original webCRM creation timestamp preserved in the ActivityDate field.

webCRM custom fields on Organisations, Contacts, Deals, Products, and Tasks are extracted during scoping. Each custom field is mapped to a typed Microsoft Dynamics 365 Sales custom field (text, number, picklist, date, boolean) on the corresponding Dataverse entity. We pre-create the custom field schema in the destination Sandbox before any data import to avoid field-not-found errors during load.