Migrate from Bushel CRM to Salesforce Sales Cloud

Bushel contact records containing name, email, phone, and title map directly to Salesforce Contact. The company association on a Bushel contact is translated into an AccountId lookup, which requires the corresponding Account record to exist first. Owner resolution by email match is applied, and any contacts with multiple email addresses are flagged for manual review to ensure the correct user is assigned as the Owner.

Bushel company records include address, industry, and revenue fields that map to Salesforce Account. Agribusiness‑specific attributes such as farm name, commodity type, and acreage are stored as custom Account fields (__c) in Salesforce. The industry field is transformed using a value‑mapping table that aligns Bushel pick‑list values with Salesforce’s Industry pick‑list. All address components (street, city, state, postal code, country) are mapped to the corresponding Account billing address fields.

Bushel Deal records consolidate commercial terms (name, amount, close/delivery date) with grain‑logistics data (commodity type, bushels delivered, cash‑bid price). Commercial fields map to Opportunity Name, Amount, and CloseDate; logistics attributes become custom Opportunity fields (__c). OwnerId and AccountId are populated by resolving the deal’s Account Manager email and linking the deal to the related Account record. Stage defaults are set and can be adjusted after migration.

Bushel's Account Manager field assigns responsibility for each customer record and maps to Salesforce OwnerId on Account, Contact, and Opportunity, establishing ownership across the CRM. Resolution matches the Account Manager's email to a Salesforce user; any unmatched email is flagged in a pre‑migration report so your team can either create a new user or assign a fallback owner. If co‑ownership is required, a junction object can be added after migration.

Bushel activity logs capture subject, body, and timestamp for each interaction. These map to Salesforce Task fields (Subject, Description, ActivityDate). Meeting‑type activities are mapped to Salesforce Event, preserving the original start datetime and duration. The owner of each activity is resolved via email match to a Salesforce user, and parent‑record links (AccountId, ContactId) are retained to maintain the relationship hierarchy during migration.

Bushel notes attached to contacts and companies migrate to Salesforce Notes (the Notes object, not the legacy Note). Rich‑text formatting is preserved where the source API exposes it; plain‑text notes retain their content without styling. The Title of each note is set to the original note’s subject or a truncated preview, and the CreatedDate reflects the original creation timestamp. Notes longer than Salesforce’s field limit are split across note records.

Bushel scale tickets (date, gross weight, moisture, test weight, net bushels) have no Salesforce standard equivalent. We create a Scale_Ticket__c custom object with fields for each data point and a lookup to the Account. Your team configures the page layout post-migration.

Bushel cash bid terms (bid price per bushel, delivery period, basis, contract status) require a custom Cash_Bid__c object in Salesforce. We map the linked account, commodity type, bid price, and expiration date. Contract status (filled, open, expired) is included as a pick-list.

Bushel file attachments on records are re‑uploaded to Salesforce Files (ContentDocument/ContentVersion). We map the parent record link so each file attaches to the correct Account, Contact, or Opportunity. Salesforce enforces a 25 MB per‑file limit; larger files are flagged. Confirming that Bushel's API exposes attachment binary data is a pre‑migration step; if it does not, we document the gap and your team can use Bush's download capability to retrieve files separately.

Bushel pre-populates fields like account balances and contract status from live ERP connections. Salesforce has no native equivalent — these feeds must be rebuilt via middleware (MuleSoft, Boomi) or Salesforce Connect after migration. We document the feed structure for your integration team.