Migrate from Gripp to Microsoft Dynamics 365 Sales

Gripp Assets do not map directly to any standard Microsoft Dynamics 365 Sales entity. We pre-create a custom entity equipment__c in the destination Microsoft Dynamics 365 Sales org using the Dataverse API. The custom entity includes fields for asset name, serial number, QR code value, location, operational status, and equipment category. Gripp asset-to-issue relationships migrate as lookup fields on the custom entity pointing to the migrated Case records.

Gripp Issues map to Microsoft Dynamics 365 Sales Case records. The issue title becomes Case Title, the issue body migrates to Case Description, status and priority map to Case Status and Priority respectively, and the reporter attribution maps to CreatedBy User lookup. We preserve the asset-to-issue relationship by setting the CustomerAssetId lookup on the Case to the migrated equipment__c record.

Inspections in Gripp are structured maintenance records tied to specific assets. We create a custom inspection__c entity with fields for inspection date, result status, checklist completion, and asset lookup. Gripp inspection checklist items with pass/fail values migrate as a JSON-serialized string in a custom notes field or as child custom entity records (inspection_item__c) with a lookup to the parent inspection__c record. The customer admin decides on checklist representation during scoping.

Service Intervals define recurring maintenance schedules tied to Gripp assets. We create a custom service_interval__c entity with fields for interval type (time-based or mileage-based), interval value, last completed date, next due date, and asset lookup. We compute next due dates from the last completed date and interval value during migration so that the calendar data is immediately actionable in Dynamics. Note that recurring reminder automation does not migrate as a Power Automate flow; we document the recommended trigger logic for the customer admin to rebuild.

Gripp Team members map to Microsoft Dynamics 365 Sales User records by email match. Role assignments from Gripp (Admin, Manager, Technician, Viewer) migrate to Dynamics Security Roles assigned during migration. Language preferences (English and Spanish) are noted for the customer's admin to configure in the User record settings post-migration. Inactive Gripp users map to inactive Dynamics Users to preserve historical attribution without creating unnecessary seat licenses.

Gripp Conversations are threaded messages attached to assets or issues. We map message bodies to Microsoft Dynamics 365 Sales Note records, timestamps to CreatedOn, and author attribution to CreatedBy User lookup. Notes attach to the parent record via the Regarding (objecttypecode) lookup, pointing to either the equipment__c custom entity (for asset conversations) or the Case record (for issue conversations). Gripp does not support rich-text messages; plain-text migration preserves content fidelity.

Gripp assets store location data as address fields and GPS coordinates. We map address components to the composite Address fields on the equipment__c custom entity. If Gripp stores GPS latitude and longitude separately, these migrate to custom Decimal fields on the equipment__c record. Microsoft Dynamics 365 Sales does not have native geolocation mapping; Power Apps integration is the path for map visualization, which we flag as a post-migration configuration item.

Gripp tracks service history as a chronological log attached to assets. We represent service history in Microsoft Dynamics 365 Sales as a custom related entity service_record__c linked to equipment__c. Each service record captures date, service type, technician, and description. This approach preserves the chronological service timeline while keeping it queryable within Dynamics without requiring a separate data warehouse.