Migrate from Gearbox to Twenty CRM

Gearbox contractor records map directly to Twenty People. Gearbox stores first name, last name, email, phone, job title, and company association. These map 1:1 to Twenty People fields. Contractor status (Active, Inactive) migrates as a custom Select field on People if the field is used to filter pipelines rather than just archive records.

Gearbox organization records map to Twenty Companies. Standard fields — name, domain, industry, employee count, annual revenue, address — map to their Twenty counterparts. Gearbox's parent-company hierarchy maps to Twenty's relation field on Company if Gearbox exposes that relationship in its API export.

Work orders are the core entity in Gearbox's fleet model. FlitStack AI maps Work Order name to Opportunity name, scheduled date to Close Date, and Work Order status to Opportunity Stage via value mapping (Active → Open/Qualification, Completed → Closed Won, Cancelled → Closed Lost). Custom fields like service type, priority, and cost migrate to custom fields on the Opportunity.

Gearbox stage names vary by setup but typically include states like Scheduled, In Progress, Pending Parts, Completed, and Cancelled. Each value is mapped to a Twenty Opportunity Stage. Stage transition timestamps from Gearbox are preserved as custom datetime fields on the Opportunity record.

Gearbox vehicle and asset records have no direct Twenty CRM equivalent — Twenty does not ship a native asset or fleet object. FlitStack AI creates a Vehicle custom object in Twenty via Settings → Data Model, adds fields for registration, make/model, mileage, and last service date, then links each Vehicle record to its parent Company. Work orders reference the Vehicle via a relation field on the custom object.

Gearbox assigns Work Orders to Gearbox workspace users (technicians or contractors). Twenty Opportunities have an assignee field that links to a Workspace Member. FlitStack resolves Gearbox user emails against invited Twenty Workspace Members and maps the assignment. Unresolved users are flagged before migration so the Twenty admin can invite them first.

Gearbox workspace users map to Twenty Workspace Members. Before migration, all Gearbox users who own records should be invited to the Twenty workspace via Settings → Members. FlitStack validates that a Workspace Member exists for each resolved owner before committing the Opportunity import.

Work order notes and inspection comments in Gearbox migrate to Twenty Notes attached to the corresponding Opportunity record. File attachments are re-uploaded to Twenty's file storage and linked to the Opportunity. Original create timestamps and note authors are preserved in custom fields on the Note record.

Gearbox work order line items (parts used, labor hours, external costs) have no native equivalent in Twenty Opportunities. FlitStack preserves this data as a formatted Note attached to the Opportunity, including a plain-text breakdown of parts and costs, so the financial history of the work order is not lost even though it cannot be rendered as structured fields.

Gearbox inventory and parts catalog records may be migrated as a custom Part object in Twenty if the team wants to link parts to work orders. This requires a separate mapping pass and is scoped as optional depending on whether parts linkage drives reporting in Twenty.

Any Gearbox custom fields on Contractor, Company, Work Order, or Vehicle records require pre-creation in Twenty via Settings → Data Model before the CSV import runs. FlitStack delivers a custom field creation plan as part of the pre-migration schema review so the Twenty admin can provision fields before the import begins.

Gearbox role-based permissions (Admin, Technician, Viewer) do not have a direct equivalent in Twenty's permission model. FlitStack does not migrate access-control configurations. The Twenty admin configures Workspace Member roles and object-level permissions after migration based on the organization's desired access map.

If Gearbox tracks which contractor is the primary contact for a work order, FlitStack maps that label to an Opportunity Contact Role in Twenty. Standard labels (Primary Contact, Billing Contact) translate to built-in Twenty contact roles. Non-standard labels are preserved as a custom Select field on the Opportunity's person relation.