Migrate from GorillaDesk to Microsoft Dynamics 365 Sales

GorillaDesk Customer maps to Dynamics 365 Contact. The customer's primary address, email, and phone become standard Contact fields. The primary Company in GorillaDesk becomes AccountId lookup in Dynamics — if no company is set, we create or link to a placeholder Account record for the contact to attach to.

GorillaDesk Company (when present on a Customer record) maps to a Dynamics 365 Account. When a GorillaDesk Customer has an associated company name, we create a corresponding Account and link the Contact to it via AccountId. Customers without a company are attached to a default 'Individual' Account record.

GorillaDesk Job is the core unit of work and translates most directly to Dynamics 365 Opportunity representing service revenue. The job's scheduled date becomes EstimatedCloseDate, the service type becomes the Opportunity name, and the job status (Scheduled, In Progress, Completed) maps to Opportunity StageName values. If GorillaDesk has multiple service types, we use RecordTypeId to differentiate.

In GorillaDesk, a job may contain multiple sub‑tasks, service checklist items, or notes describing materials applied during the visit. These granular items are extracted and written as separate Dynamics 365 Task records, each linked to its parent Opportunity via the RegardingObjectId reference. The original description, completion flags, and timestamps are retained to preserve full operational history for auditing and future scheduling.

GorillaDesk Invoices map to Dynamics 365 SalesOrder records (status = 'Invoiced'). Invoice line items become SalesOrderDetails referencing Product records or write-in products. Paid status, payment method, and payment date are stored on the Dynamics 365 invoice entity. Voided GorillaDesk invoices are migrated as cancelled SalesOrders.

GorillaDesk Users (technicians, dispatchers) resolve to Dynamics 365 SystemUser records by email match. If a user's email matches an existing Dynamics 365 user, their records are assigned to that OwnerId. Unmatched users are flagged before migration — either invite them to Dynamics first or assign their jobs to a fallback owner.

GorillaDesk Notes attached to Customers or Jobs become Dynamics 365 Annotation records (the unified notes/attachments entity in Dataverse). Note body text, created date, and owning user are preserved. If the note includes a file attachment, we upload it to SharePoint and link via the documentlocation entity.

GorillaDesk phone types (e.g., Mobile, Work, Home) are stored as a pick-list in GorillaDesk. Dynamics 365 Contact already has Phone, MobilePhone, and Telephone1–3 fields. If GorillaDesk uses custom phone-type labels beyond these three, we create a custom pick-list field (new_PhoneType__c) and map values by name.

GorillaDesk's materials-tracking feature (chemicals, parts applied per job) stores key-value data on Job records. Dynamics 365 has no native materials tracking on Opportunity. We create a custom text or multi-select field (new_MaterialsUsed__c) and serialize the materials list as JSON or delimited text for reference.

GorillaDesk Estimates map to Dynamics 365 Quote records. Line items become QuoteDetails. Estimate status (Draft, Sent, Accepted, Declined) maps to Quote StateCode values. Accepted quotes can be revised into Orders during migration if the job has started but not yet been invoiced.

GorillaDesk records GPS latitude and longitude on each Job to support route planning and technician navigation. Since Dynamics 365 Sales does not include a native geo‑location attribute on the Account entity, we add two custom decimal fields named new_JobLatitude__c and new_JobLongitude__c to the Account form. The most recent coordinates from a customer's latest completed visit are stored, enabling territory analysis, map visualization, or Power Apps overlays for field‑service management.

All file attachments stored in GorillaDesk on Jobs—including photos, signed forms, and chemical usage reports—are exported, then uploaded to Dynamics 365 via SharePoint document management or as Annotation records linked to the parent Opportunity. The migration enforces the file‑size limit of 128 MB per file; any attachment exceeding this threshold is split, compressed, or flagged for manual handling. Original file names and MIME types are preserved for audit trails and retrieval.

GorillaDesk automations (auto-scheduling rules, SMS notifications on job status change, route-optimization triggers) do not migrate. They must be rebuilt in Power Automate or Azure Logic Apps. We export the GorillaDesk automation definitions as a reference document so your Dynamics admin can reconstruct triggers on the new Opportunity and Task entities.

GorillaDesk's review-generation feature triggers post-job customer review requests. Dynamics 365 Sales has no native review-solicitation mechanism. The feature flag is preserved as a boolean custom field (new_ReviewRequested__c) for reference, but the automation must be rebuilt using Power Automate and an integrated review platform.