Migrate from Bushel CRM to HighLevel

Bushel contacts map directly to HighLevel contacts. Every standard field — first name, last name, email, phone, address — has a native HighLevel equivalent. Bushel's owner field resolves by email against HighLevel users before migration. Contacts without a primary company in Bushel land as standalone HighLevel contacts; we flag any contact missing both a company link and an email for manual review before the full run commits.

Bushel companies map to HighLevel companies. Bushel's parent-company hierarchy (if used) translates to HighLevel's parent-company lookup field. Industry classification from Bushel maps to a HighLevel custom pick-list field when Bushel's industry values are non-standard. We flag any company without a name and apply a placeholder so the HighLevel record is valid.

Bushel deals become HighLevel Opportunities. Bushel's deal name, amount, stage, close date, and owner all translate directly. Bushel's quote-specific fields — commodity-quantity, delivery-schedule dates, Bushel deal type — migrate as HighLevel custom fields. We map each Bushel deal pipeline to a HighLevel pipeline so stage history and forecasting continuity are preserved.

Bushel tasks map to HighLevel tasks. Subject, due date, status, assigned owner, and any task-level notes all land in the corresponding HighLevel task fields. Tasks are loaded after contacts so the owner lookup resolves correctly — tasks without a resolvable owner receive a migration-system fallback owner that your team reassigns post-migration.

Bushel notes map to HighLevel notes. The note body, subject line, create timestamp, and owning contact or company link are preserved. If a Bushel note contains an embedded file reference, we store the reference URL as a note attachment link in HighLevel rather than re-uploading the file, since Bushel's file-attachment API does not expose raw binary for re-hosting.

Bushel users (account managers) resolve by email against HighLevel users. Bushel's account-manager-to-contact and account-manager-to-company assignments become HighLevel contact-owner and company-owner lookups. HighLevel's location model (used for agencies managing multiple client sub-accounts) maps to the Bushel account structure when present, with location-level permissions applied based on your Bushel account's team configuration.

Bushel custom properties with no native HighLevel equivalent — including grain commodity types, on-farm storage capacity, delivery-destination addresses, and ERP-linked balance fields — create HighLevel custom fields at migration time. Each custom property name in Bushel becomes one custom field in HighLevel; pick-list values are mapped value-by-value. We deliver a custom-field manifest before migration so your HighLevel admin can review and rename fields before data lands.

Bushel file attachments associated with contacts, companies, or deals do not have a direct HighLevel equivalent in the standard migration model. We extract attachment metadata (file name, size, linked record, upload date) and store it as a HighLevel note on the related record so your team knows which files existed and can re-upload them manually from your Bushel export.

Each Bushel deal pipeline maps to one HighLevel pipeline. Bushel pipeline stages translate to HighLevel stage names in the corresponding pipeline. If Bushel uses multiple pipelines (e.g., one for grain origination and one for service contracts), we create a matching number of HighLevel pipelines and map stage values per pipeline so reporting continuity holds after cutover.

Bushel activity log entries (call summaries, email log notes, meeting records) migrate as HighLevel notes on the related contact or company record, preserving the original timestamp and owner. HighLevel does not expose a native activity-timeline API for bulk writes, so activities land as time-stamped notes rather than a structured activity stream — this is the closest equivalent available without a custom API integration.