Migrate from Gearbox to Salesforce Sales Cloud

Gearbox equipment records map 1:1 to Salesforce Asset objects. The Asset Name, SerialNumber, InstallDate, and Status fields map directly. Gearbox equipment category becomes a Salesforce Record Type on Asset so page layouts and pick-list values are scoped per asset class.

Gearbox equipment representing fleet vehicles or repeatable product models merges into Salesforce Product2 for quote and order management tracking. Serialized assets retain Asset linkage while non-serialized equipment records maintain the Asset object only. The Product2 mapping supports parts pricing and service kit configurations.

Gearbox service records map to Salesforce WorkOrder objects when Field Service Lightning is enabled on the org. WorkOrder Subject, Status, Priority, and ServiceDuration map directly. Gearbox service type pick-list values require explicit value-mapping to Salesforce WorkOrder Status values during migration planning.

Gearbox individual maintenance tasks within a service record map to Salesforce WorkOrderLineItem. Each line item inherits the parent WorkOrder's Subject and links to the Asset being serviced. Parts consumed map to Product2 records or custom PricebookEntry entries for accurate cost tracking.

Gearbox technician and driver contacts map directly to Salesforce Contact. Email, phone, mailing address, and title fields transfer without transformation. The Contact is linked to the primary Account representing the driver or technician's organization for hierarchical data integrity.

Gearbox equipment-owner contacts representing business entities map to Salesforce Contact with a parent Account record. The Account holds company-level data including address, industry classification, and fleet size estimate while the Contact holds individual owner information such as name and contact details.

Gearbox custom equipment properties such as Last_Oil_Change_Mileage__c and Tire_Rotation_Interval__c require Salesforce custom fields on the Asset object with the __c suffix per naming conventions. Field-level security is configured per profile and Gearbox field types map to appropriate Salesforce data types including Number, Date, Picklist, and Text.

Gearbox service-record custom fields including Labor_Cost__c and Parts_Source__c migrate to Salesforce WorkOrder custom __c fields. Gearbox numeric and currency fields map to Salesforce Number and Currency data types respectively, ensuring accurate financial reporting within the Work Order object.

Gearbox equipment photos and attached documents re-upload to Salesforce Files linked to the corresponding Asset record. File size limits apply — Salesforce caps individual files at 25MB by default for standard file uploads via the API.

Gearbox preventive maintenance schedules with mileage intervals and calendar reminders have no direct Salesforce standard equivalent. When Field Service Lightning is enabled, FS ScheduledService__c handles recurring service generation; otherwise FlitStack preserves schedule rules as custom datetime fields for Flow-based trigger recreation.

Gearbox user accounts resolve to Salesforce User records via email domain matching. Unmatched Gearbox users require Salesforce user provisioning before OwnerId assignment on WorkOrder and Asset records. Service territory assignments map to Salesforce Territory if Territory Management is active on the org.

Gearbox third-party integrations including telematics providers, parts supplier connections, and DMS systems do not migrate as data. These must be rebuilt as Salesforce-connected apps, AppExchange packages, or custom REST integrations post-migration using the exported endpoint documentation.