Migrate from Gripp to Twenty CRM

Gripp Assets covering customer equipment or client-managed implements map to Twenty Company records. Internal fleet vehicles, power units, and farm implements with no external customer relationship map to a custom Asset object we pre-create in Twenty under Settings → Data Model before migration. Gripp asset metadata (QR code identifiers, location, service history) migrates as custom fields on the appropriate destination record. If a Gripp Asset is linked to a Gripp Company, we resolve that relationship by matching asset owner names to the corresponding Twenty People record.

Gripp Issues (field reports tied to specific assets) map to Twenty Tasks linked to the parent Asset record (Company or custom Asset object). Issue body migrates as Task description, status maps from Gripp open/closed to Task status values, and priority maps to Task priority. If the Issue has no parent record in Twenty, we attach it to the nearest related Company or People record. Long-form issue narratives with multiple comments migrate as Notes attached to the Task.

Gripp Inspections (structured maintenance records from routine checks) do not have a direct Twenty standard object equivalent. We pre-create an Inspection Custom Object in Twenty via Settings → Data Model before migration, defining fields for inspection date, result (pass/fail/checklist), inspector name, and asset reference. Completed checklists migrate as multi-select or long-text fields. The parent Asset reference links to the corresponding Company or custom Asset record.

Gripp Service Intervals (recurring maintenance schedules tied to assets) require a custom ServiceInterval object in Twenty. We create the object before migration with fields for interval type (time-based, mileage-based, seasonal), frequency, last-completed date, next-due date, and asset reference. Gripp's automated reminder trigger does not migrate; we document each interval definition so your admin can rebuild reminder logic in Twenty using an external scheduling tool or integration.

Gripp Team members map to Twenty People records. We resolve by email address as the primary key. Role assignments migrate as custom fields on the People record. Language preferences (Gripp supports English and Spanish) migrate to the People display name or a custom language field. Owner assignments on Gripp Assets and Issues carry over as Task assignments in Twenty resolved against the People record.

Gripp Conversations (threaded team messages attached to assets or issues) have no direct equivalent in Twenty's current feature set. We migrate conversation bodies as Note records attached to the related Company, custom Asset, or Task parent. Thread structure is not preserved; message order is inferred from timestamp and author attribution. If Gripp Conversations are customer-facing, they map to the related People record instead.

If Gripp has any extended entity types beyond the standard six, they migrate to Twenty Custom Objects created via Settings → Data Model before import. All custom fields, lookup relationships, and picklist options are defined in Twenty first. CSV import creates records only; it does not create fields. We deploy the schema via Twenty's Data Model UI and validate field types before any data load begins.

Gripp Asset and Issue owners resolve by email against the Twenty People table. Any Gripp owner without a matching People record in Twenty goes to a reconciliation queue for your admin to provision before asset and issue import resumes. Owner assignment on migrated records maps to the Task or Note assigned_to field.

Gripp Assets have parent-child hierarchies (e.g., an implement attached to a power unit). We represent these in Twenty as lookup relationships on the custom Asset object. The top-level asset becomes the parent Company record; child assets become custom Asset records with a self-lookup field pointing to the parent. This structure preserves the equipment hierarchy without duplicating records.

Gripp's created_at, last_updated, and service-interval due dates migrate to equivalent date and datetime fields on the respective Twenty records. Asset purchase date and warranty expiry date map to custom date fields on the Asset or Company record. Activity timestamps on Issues and Inspections migrate as Task ActivityDate or custom datetime fields on the Inspection custom object.