Migrate from Gripp to HighLevel

Gripp Assets (equipment, vehicles, implements, pivots) require a mapping decision during scoping. If the customer treats equipment as things to track alongside client relationships, we map Assets to GoHighLevel Contacts with a custom field gripp_asset_id__c and a checkbox gripp_is_asset__c. If the customer treats equipment as operational records distinct from clients, we use a Custom Object named Gripp_Asset__c with custom fields for serial number, QR code, asset type, and status. The mapping decision depends on how many Assets have associated client billing or service relationships versus standalone operational records. Assets are imported first so that downstream Issues and Inspections can resolve their asset lookup references.

Gripp Issues are field reports filed against Assets—maintenance problems, damage observations, operational concerns. We map Issues to GoHighLevel Custom Objects named Gripp_Issue__c when the customer needs structured issue tracking, or to Task records when the use case maps to a simple activity log. Custom Object mapping preserves issue body, status (Open, In Progress, Resolved), priority (Low, Medium, High, Critical), and the gripp_asset_id__c lookup reference. Reporter attribution maps to the GoHighLevel User lookup.

Gripp Inspections are structured maintenance records created during routine checks with checklist items, completion dates, and results. We map to a GoHighLevel Custom Object named Gripp_Inspection__c with custom fields for inspection date, result (Pass, Fail, Conditional), inspector name, and a long-text field for checklist summary. If the customer requires checklist-level detail, we store each checklist item as a JSON blob in a long-text field until GoHighLevel's form builder is configured to display structured inspection records. The gripp_asset_id__c lookup connects each inspection to its parent Asset record.

Gripp Service Intervals define recurring maintenance schedules tied to Assets—oil changes, mileage-based service, seasonal checks—with last-completed dates and next-due calculations. We map to a GoHighLevel Custom Object named Gripp_Service_Interval__c with custom fields for interval type, interval value, last_completed_date__c, next_due_date__c, and a calculated reminder_date__c. GoHighLevel Workflows can trigger notifications on next_due_date__c, but the customer should note that the automatic scheduling engine is rebuilt in GoHighLevel rather than migrated as functional code.

Gripp Teams represent organization members and their roles, including language preferences for English and Spanish operations. We map Team members to GoHighLevel Users with role assignments preserved as a custom picklist field gripp_role__c and language preference in a custom text field gripp_language__c. User-to-asset assignments (which team member is responsible for which asset) are preserved as a multi-select lookup field or through a dedicated Gripp_Team_Asset__c custom object if the relationship is many-to-many.

Gripp Conversations are threaded team messages attached to Assets or Issues. GoHighLevel does not have a native threaded conversation model. We map Conversations to Note records linked via ContentDocumentLink to the parent Asset Contact or Issue Custom Object, with the conversation thread preserved in reverse-chronological order in the Note body. Alternatively, for customers requiring full thread structure, we use a Custom Object named Gripp_Conversation__c with fields for asset or issue reference, author, timestamp, and message body. The customer chooses the strategy during scoping.

Gripp Assets include QR-code identifiers used for field identification and asset lookup. We migrate the QR code identifier to a custom text field asset_qr_code__c on the destination Contact or Gripp_Asset__c Custom Object. If the customer uses GoHighLevel's built-in QR-code or barcode scanning features, we configure a Workflow trigger that opens the asset record from a scanned value using this field as the lookup key.

Gripp Issue priority levels (Low, Medium, High, Critical) and status values (Open, In Progress, Resolved, Closed) map to GoHighLevel custom picklist fields on the Gripp_Issue__c Custom Object. We preserve the original Gripp priority and status values as picklist options rather than re-normalizing them, to maintain audit continuity. Status changes are logged as Note records or as Task history entries for audit trail purposes.