Migrate from Gripp to Nutshell

Gripp Asset records (equipment, vehicles, implements, inventory items) map to Nutshell Account records when the asset represents a customer or property account, or to a Custom Object (available on Nutshell Pro and above) when the asset represents a piece of equipment tracked for maintenance. The Gripp asset name becomes Account Name; asset type becomes Industry or a custom field; QR code identifiers have no Nutshell equivalent and are preserved in a custom field asset_qr_id__c as a reference for field lookup. Service history attached to Gripp Assets migrates as Notes linked to the Account or Custom Object.

Gripp Issues (field reports on maintenance problems, damage observations, operational concerns) map to Nutshell Tasks. Issue body migrates as Task description; status (open, resolved, closed) maps to Task status (open, completed); priority maps to Task priority; reporter attribution maps to Task assigned user resolved by email match against Nutshell People. Gripp's issue-to-asset relationship is preserved as a Task linked to the mapped Account or Custom Object representing the asset.

Gripp Inspections (structured maintenance records from routine checks) map to Nutshell Notes attached to the corresponding Account or Custom Object. Inspection results and checklists are preserved as formatted Note body text with a date stamp. Because Nutshell Notes do not support structured checklist fields, we flatten the checklist into a text list within the Note. If the customer requires structured inspection records, we recommend rebuilding them as Custom Objects on Nutshell Pro, but that requires schema design during scoping.

Gripp Service Intervals (recurring maintenance schedules with next-due dates, oil changes, mileage-based service, seasonal checks) have no direct Nutshell equivalent. Nutshell does not have a native recurring-task or service-interval object. We migrate the last-completed date and next-due date as a formatted Note on the Account or Custom Object, and we deliver a written maintenance calendar as a reference document listing every Service Interval with its asset, interval type, last date, and next-due date. The customer's admin rebuilds these as Tasks with reminder dates or uses a third-party scheduling integration.

Gripp team members (organization members and their roles) map to Nutshell People. We migrate name, email, and role assignment. Gripp's language preference (English or Spanish) has no Nutshell equivalent and is preserved in a custom field language_pref__c on the Person record. User-to-asset assignments (which users are responsible for which assets) migrate as Notes on the Account or Custom Object noting the responsible Person.

Gripp Conversations (threaded team messages attached to assets or issues) have no direct Nutshell equivalent. Nutshell does not support threaded conversations on Accounts or Custom Objects. We migrate Conversation message bodies as Notes with timestamp and author attribution. If the thread length is significant, we create one Note per conversation thread rather than per message to avoid overwhelming the activity timeline. The customer's admin may prefer to export significant conversation threads as a PDF and attach it to the Account.

Gripp customizable forms used for in-the-moment field data capture have no Nutshell equivalent. Nutshell uses standard field types for People, Companies, Leads, and Deals rather than custom form builders. We document every Gripp custom form and its fields as part of the migration scope deliverable so the customer's admin can recreate the relevant data-capture fields as Nutshell custom fields (Text, Long Text, Currency, Date, Dropdown, Checkbox) on the appropriate object. This is a manual rebuild step, not a data migration step.

Gripp attachments stored on Assets (manuals, parts lists, receipts, videos) migrate as Nutshell Files attached to the corresponding Account or Custom Object. We download attachments from Gripp via account export or manual download, then upload them to Nutshell linked to the mapped record. Large video files may be migrated as links in Note text rather than as embedded files, depending on Nutshell file size limits.