Migrate from Gearbox to HighLevel

Direct field-to-field map for standard fields (name, email, phone, address). Gearbox custom properties that are text, number, currency, date, or phone type migrate as HighLevel custom fields on the Contact object. Gearbox tags are mapped to a custom field formatted as comma-separated text or parsed into HighLevel tag format if the Gearbox export supports structured tag arrays.

Gearbox company records map directly to HighLevel Companies. Company name, website, phone, address, and industry fields migrate to their HighLevel counterparts. Custom company properties become HighLevel custom fields on the Company object. Gearbox company hierarchy (parent/child) maps to HighLevel's parent-company association if supported by the export.

Gearbox deals migrate as HighLevel Opportunities. Deal name, amount, close date, and owner assignment map directly. The Gearbox pipeline and stage assignment determines which HighLevel pipeline and stage status the Opportunity receives. Gearbox custom deal properties become HighLevel custom fields on the Opportunity object.

Gearbox pipelines map to HighLevel Pipelines. Each Gearbox pipeline stage becomes a HighLevel stage within the corresponding pipeline. The Gearbox stage probability values are stored as a custom field on the Opportunity for reporting continuity. Stage-entered timestamps are preserved as custom datetime fields if Gearbox exports that metadata.

Gearbox vehicle records have no direct HighLevel equivalent. We create a HighLevel Custom Object named Vehicle with custom fields for VIN, make, model, year, license plate, current mileage, and service due date. The vehicle-to-driver association migrates as a relationship field linking the Vehicle custom object to the Contact record of the assigned driver.

Gearbox maintenance history is stored as a custom object in HighLevel with fields for service date, service type, parts used, labor hours, cost, and associated vehicle. The maintenance record links to both the Vehicle custom object and the related Contact or Company. Original Gearbox timestamps and service provider notes are preserved as custom text fields.

Gearbox driver records map to HighLevel Contacts with the role distinguished via a custom field (Driver_Role__c). Driver license number and expiration date are stored as custom fields on the Contact. Vehicle assignment is tracked via a custom relationship field or a text field holding the associated vehicle identifier.

Gearbox inspection records (inspection date, score, inspector, deficiencies) become a HighLevel custom object with corresponding custom fields. Each inspection links to the associated Vehicle custom object. Inspection status (Pass/Fail) is stored as a pick-list custom field in HighLevel for filtering and reporting.

Gearbox notes and logged tasks migrate to HighLevel Notes and Tasks respectively. Original create dates are preserved as custom datetime fields since HighLevel sets CreatedDate at import time. Task owners are resolved by email match against HighLevel users. Notes attached to specific records carry their parent-record association forward.

Gearbox automations — triggers, actions, conditions, and time delays — are platform-native logic that cannot export as portable data. They must be rebuilt in HighLevel's Workflow Builder. We document every Gearbox automation in a structured reference sheet (trigger type, conditions, actions, sequence order) so your HighLevel admin or implementation partner can rebuild them using HighLevel's trigger-action canvas.

Gearbox tags migrate to HighLevel tags. If Gearbox exports tags as a comma-separated string per contact, we parse the string and create individual HighLevel tag entries for each value. Tag naming conventions are preserved as-is. Multi-value tags from Gearbox are flattened to individual tags in HighLevel since HighLevel tags are not hierarchical.