Migrate from Bushel CRM to Microsoft Dynamics 365 Sales

Bushel contacts map directly to Dynamics 365 Contacts. The primary company association becomes AccountId lookup; Bushel's N:N contact-company model collapses to one primary AccountId with additional relationships surfaced via Account Contact Relationships. Owner resolved by email match to D365 users.

Bushel company records map to Dynamics 365 Accounts. Parent-child hierarchies preserved via ParentAccountId lookup. Bushel company domains, industries, and employee counts map to Account.Name, Account.WebSite, Account.Industry, and Account.NumberOfEmployees respectively. Multi-location companies require Address entity population. Additional address fields such as Address1_Line2, City, State, and PostalCode are also populated when available.

Bushel notes logged on customer profiles migrate as Dynamics 365 Annotation records attached to the corresponding Contact or Account. Original created-on timestamps and author assignments preserved as CreatedOn and CreatedBy lookups. Rich-text formatting in Bushel notes converts to HTML in D365 Notes.

Bushel follow-up tasks migrate as Dynamics 365 Task records linked to the parent Contact or Account via RegardingObjectId. Task subject, due date, priority, and status map to Subject, ScheduledEnd, Priority, and StateCode respectively. Completed tasks preserve the actual end timestamp from Bushel.

Bushel quotes and deal records map to Dynamics 365 Opportunities. Bush's custom pipeline stages map to D365 Opportunity Stage values via value mapping. Estimated deal values map to EstimatedRevenue. Close date maps to CloseDate. The Deal Name becomes Opportunity.Name. Additionally, any associated product line items are linked via the Opportunity Product entity to preserve quote details.

Bushel's scale ticket records — capturing grain delivery weights, dates, and test weights — have no native Dynamics 365 equivalent. We create a scale_tickets custom table in Dataverse with fields for ticket_number, delivery_date, gross_weight, tare_weight, net_weight, moisture_pct, and foreign keys to the originating Account and Contact.

Bushel's cash bid and forward-contract records (bid price, contract quantity, delivery period, commodity type) require a custom cash_bids Dataverse table. Fields include bid_price, contract_quantity, commodity_type, delivery_start, delivery_end, status, and lookup to Account. This data is agribusiness-specific and has no standard D365 equivalent.

Bushel's Account Manager field on customer records maps to Dynamics 365 OwnerId. Resolution happens by email match against D365 users — if the Bushel owner email matches a D365 user, OwnerId is set directly; unmatched owners flagged for team assignment before migration commits.

Bushel farm demographics (storage capacity, production acreage, crop rotation history, delivery destinations) have no D365 standard fields. We create custom fields on the Account entity: Storage_Capacity_Bushels__c, Total_Production_Acreage__c, and a delivery_destinations related entity to preserve this data. Additional custom fields may include irrigation_type__c, primary_crop__c, and harvest_month__c to capture detailed farm operational patterns.

Bushel commodity balance tracking (grain inventory by type, prepay balances, booking totals) migrates as custom decimal fields on the Account: Commodity_Balance_Corn__c, Commodity_Balance_Soybeans__c, Prepay_Balance__c. These values represent financial positions and require a custom Dataverse field for each commodity type tracked. If additional commodity types such as wheat or barley are present, corresponding custom fields are added following the same naming convention to ensure consistent reporting across all grain categories.