Migrate from Gripp to HubSpot

Gripp's central asset record maps 1:1 to a HubSpot custom object named Equipment__c. This is the primary migration object. Gripp asset_name, location, operational_status, and qr_code become HubSpot custom properties on this object. The Equipment__c custom object must be created in HubSpot before the migration loads — FlitStack delivers the schema definition as a setup plan.

Gripp stores team members as named user records with role, phone, and language_preference. These map to HubSpot Contacts: name maps to firstname/lastname, role maps to jobtitle, phone maps to phone. The Spanish-language preference field becomes a HubSpot custom contact property (language_preference__c) for teams operating bilingual field crews.

Gripp operational issues (equipment breakdowns, safety alerts, maintenance requests) map directly to HubSpot Tickets. Issue subject becomes ticket subject, issue_type maps to ticket_pipeline and ticket_status, reported_by links to the Contact record, and reported_at preserves the original timestamp. Priority values require value-by-value mapping against HubSpot's ticket_priority pick-list.

Gripp maintenance records are stored as log arrays inside the Equipment record. HubSpot has no native maintenance log object, so FlitStack converts each log entry to a HubSpot Task with Type='Maintenance', Subject containing the service_type, and Description containing the notes. Original performed_by and date are preserved as Task fields linked to the Equipment__c record. This preserves the full service history in HubSpot's activity feed.

Gripp locations (farm sites, field identifiers, depot names) map to HubSpot Companies. location_name becomes Company name, address fields map to the standard address compound field. Teams that track multiple sites per customer account can use HubSpot Company associations or a custom junction object to represent the full location hierarchy.

Gripp's QR-code asset tagging system has no direct equivalent in HubSpot. The qr_code value from each Gripp Equipment record is stored as a custom text property (qr_code__c) on the Equipment__c custom object in HubSpot. This enables teams to search for equipment by scanning the same QR code after migration.

Gripp tracks equipment as 'operational', 'under maintenance', 'retired', or custom status values. HubSpot has no native status field for equipment records. FlitStack creates operational_status__c as a HubSpot custom pick-list property on Equipment__c, mapping Gripp's status values directly to matching HubSpot pick-list options. Unmatched values are flagged for admin review before migration runs.

Gripp assigns multiple team members to each asset record. HubSpot contacts have no native equipment assignment field. FlitStack merges Gripp's N:1 equipment-to-team relationship into a HubSpot custom junction object (Equipment_Assignment__c) linking the Equipment__c custom object to HubSpot Contacts, preserving which team members were assigned to which equipment historically.

Gripp supports equipment hierarchies — parent equipment records with child sub-units or implements. HubSpot's custom objects have no native parent-child relationship mechanism. FlitStack creates a self-referential lookup field (parent_equipment__c) on Equipment__c that points to the parent Equipment__c record, enabling the full equipment hierarchy to be represented in HubSpot.

Gripp stores attachments on equipment records — photos of equipment condition, scanned maintenance documents, inspection certificates. These migrate as HubSpot Files attached to the corresponding Equipment__c record. File size limits of 25MB per file apply. Inline images in maintenance notes are downloaded and rehosted as HubSpot-hosted assets.

Gripp maintenance reminder sequences, inspection triggers, and escalation workflows are Gripp-native automation logic with no HubSpot equivalent. These do not migrate. FlitStack exports Gripp workflow definitions as a structured reference document for the customer's HubSpot admin to rebuild using HubSpot workflows, sequences, or Operations Hub.

Gripp's keyboard-less inspection feature generates structured inspection records with pass/fail fields, notes, and timestamps. For operations that need structured inspection data in HubSpot, FlitStack maps these to a custom Inspection__c custom object linked to Equipment__c. If the operation does not have HubSpot Enterprise entitlements, inspections map to Tasks with custom property fields instead.