Migrate from Inspection Files to Microsoft Dynamics 365 Sales

Inspection Files sites map directly to Dynamics 365 Accounts. Site address, location coordinates, and compliance classification migrate as custom fields on the Account record. Parent-site hierarchies map to Account.ParentAccountId for multi-location organizations. Primary contact at each site becomes the Account Primary Contact lookup.

Inspector profiles in Inspection Files map to Dynamics 365 Contacts. Email address is used to match against Dynamics 365 user accounts for owner resolution. Inspector certifications, certifications expiry dates, and specializations migrate as custom fields (Certification_Type__c, Certification_Expiry__c) on the Contact record. Active/inactive status maps to Contact.JobTitle or a custom Is_Active_Inspector__c field.

Each completed or scheduled inspection maps to a Dynamics 365 Opportunity representing the compliance engagement. Inspection date range becomes the Opportunity Estimated Close Date. Inspection type (fire safety, environmental, structural) maps to a custom Inspection_Type__c picklist. Total findings count becomes a custom numeric field. The linked Account is set as the Opportunity AccountId.

Findings with severity levels (Critical, Major, Minor, Observation) have no native Dynamics 365 equivalent. We create a custom Inspection_Finding__c table linked to the parent Account or Opportunity via a lookup field. Severity, finding description, due date, and resolution status map to custom fields on this table. This table requires Dataverse schema creation before data loads run.

Inspection templates define checklists and item categories. These migrate as a custom Inspection_Template__c table with a link to the Account for template assignment history. Template items and categories map as lines within the custom table or as a related Inspection_Template_Item__c child table. Template versioning is preserved as a Version__c field.

Photos attached to inspection findings are downloaded from Inspection Files and re-uploaded to SharePoint document libraries linked to the Dynamics 365 Account or Opportunity. We create a SharePoint folder structure mirroring the site-inspection-finding hierarchy. File size limits of 10MB per file apply; larger files are compressed before re-upload.

Inspection Files scheduling rules and recurring inspection assignments do not have a direct Dynamics 365 equivalent. We export the scheduling configuration as a JSON reference file so your Power Automate or Dynamics 365 Field Service admin can rebuild periodic inspection triggers using Microsoft tools. Scheduling logic is not automatically migrated.

Inspection Files issues and NCRs merge multiple data points into a single CRM record. The NCR header maps to the parent Account with custom fields for NCR number, classification, and status. Detailed NCR line items map to the Inspection_Finding__c custom table where they were already routed. This avoids duplicating the account link while preserving NCR detail.

Inspection Files user accounts are matched to Dynamics 365 SystemUser records by email address. Unmatched users are flagged before migration; you can either create their Dynamics 365 accounts first or assign their records to a fallback user. User role mapping (Inspector, Admin, Viewer) translates to Security Roles in Dynamics 365.

Inspection Files custom fields (regulatory codes, compliance flags, jurisdiction codes) migrate to custom columns on the appropriate Dynamics 365 table. Field data types map to Dataverse column types: text fields to Single-Line-of-Text, numeric measurements to Decimal or Whole Number, dates to Date-Time columns. Pick-list values map via value-mapping for categorical custom fields.