Migrate from Bushel CRM to Twenty CRM

Bushel contacts map 1:1 to Twenty People. The primary company association in Bushel translates to the companyId relation in Twenty. Email, phone, job title, and address fields map directly. Original create timestamps preserved as a custom datetime field since Twenty sets CreatedAt at import time.

Bushel company records map to Twenty Companies. Company name, domain, industry, number of employees, and annual revenue fields translate directly. Parent-child company hierarchies in Bushel map to the parentId field in Twenty. Multi-contact companies maintain all linked People records in the migration.

Bushel deals map to Twenty Opportunities. Deal name becomes Opportunity name, deal amount maps to amount, close date maps to expectedCloseDate, and stage names map to Twenty stage pick-list values. Stage entered timestamps preserved as custom datetime fields for reporting continuity.

Bushel pipeline stage values map to Twenty Opportunity stage pick-list values on a value-by-value basis. Each Bushel stage name is matched to the closest Twenty stage; if no exact match exists, the stage is created in Twenty before migration runs. Probability values per stage are re-applied on the Twenty side.

Bushel account manager assignments do not map to a native Twenty owner field — Twenty does not have a built-in owner field on People or Companies equivalent to Salesforce's OwnerId. We resolve account manager by email match against Twenty Workspace Members and populate an Account_Manager__c custom field; unmatched managers are flagged before migration.

Bushel tasks map directly to Twenty Tasks. Task title, due date, body, status, and linked record associations migrate with original create timestamps. Status values map to Twenty's boolean completed field: completed tasks become completed=true, open tasks remain false. Linked record references are resolved using the migrated record IDs.

Bushel notes map to Twenty Notes. Note body, author, and linked record associations migrate with original create timestamps. Notes attached to People, Companies, or Opportunities are re-linked using migrated record IDs. Rich-text formatting in Bushel notes is preserved where the source format is compatible.

Bushel farm demographics (production history, on-farm storage capacity, delivery destination references) are agribusiness-specific data that does not have a Twenty standard object equivalent. We migrate this as a Twenty custom object. The custom object and its fields must be pre-created in Twenty Settings → Data Model before the migration runs, using the Bushel field definitions as a specification.

Bushel delivery destinations (linked to contracts and scale tickets) migrate as a Twenty custom object. The custom object schema — including address fields, linked company references, and contract associations — is documented in the migration plan. N:1 relationships to Companies use Twenty's relation field type.

Bushel file attachments (contracts, scale tickets, signed documents) do not migrate into Twenty's native file storage. We download files from Bushel, upload to Twenty's supported storage layer via their SDK, and store the resulting file URLs as a custom URL field on the relevant record. If Twenty's Organization plan (with expanded storage) is not available, a note directs users to the external storage location.

Bushel workflow definitions and task automation rules do not have a Twenty equivalent and cannot be migrated. We export the Bushel workflow configuration as a JSON specification that the Twenty admin can use as a reference when rebuilding automations in Twenty's workflow builder. Workflow rebuild is outside the data migration scope.

Bushel's native ERP integration (pulling in scale tickets, contract data, cash bids from the agribusiness ERP) does not exist in Twenty. Mapped ERP field values that exist as data in Bushel migrate as custom fields; the actual integration must be rebuilt separately using Twenty's API or a middleware tool.