Migrate from Notifi to Microsoft Dynamics 365 Sales

Notifi 'Customer' holds company and primary contact fields. We split into D365 Sales Account (company fields) and Contact (person fields) with AccountId lookup. The most-recently-modified company association becomes the primary AccountId for the primary Contact. If multiple contacts exist for the same company, we link each to the Account using the AccountId, preserving the original contact hierarchy from Notifi.

Notifi 'Job' is the core record type — it holds service type, technician, amount, status, and schedule. We map it to D365 Sales Opportunity using standard Opportunity fields (Name, Amount, StageName, CloseDate) plus custom fields Service_Type__c, Technician__c, Scheduled_Date__c, Job_Status__c, and Job_Address__c to preserve Notifi job context.

When a single Notifi job involves multiple customers (e.g., a property management company managing multiple locations), the primary customer maps to Opportunity.AccountId and additional customers are added via AccountContactRole records in D365 Sales. We also preserve the relationship type for each role, such as 'Billing' or 'Site Manager', using the AccountContactRole.Role field to maintain context in the CRM.

Notifi 'Estimate' contains header totals and line items. We map the header to D365 Sales Quote (Name, Amount, StatusCode, EffectiveFrom, EffectiveTo) and line items to QuoteProduct records. Deposit rules and approval flags migrate as custom fields (Deposit_Required__c, Approval_Status__c) since D365 Sales Quotes lack native deposit logic.

Notifi stores calls and SMS with subject, outcome, full message body, and timestamp. We map to D365 Sales Task (Subject, Description, StatusCode, PriorityCode) with a custom field Communication_Type__c to flag 'Call' or 'SMS'. Full message body migrates as Task.Description; outcomes like 'Completed' or 'Missed' map to D365 Sales StatusCode values.

D365 Sales does not have a native payment or invoice record type. We migrate payment amount, payment status, and invoice number as custom fields on the linked Opportunity: Amount_Paid__c, Payment_Status__c, Invoice_Number__c. Full invoice line items are preserved as Notes with a file attachment.

Notifi service types (e.g., 'HVAC Repair', 'Plumbing Maintenance') have no direct D365 Sales equivalent. We create a custom pick-list field Service_Type__c on the Opportunity table and map each Notifi service type value-by-value. During migration, we also populate any existing service-type counts to assist in data validation and ensure the pick-list reflects the full range of values present in Notifi.

Notifi stores a technician assignment on each job. We resolve the technician email against D365 Sales SystemUser records by email match. If the technician is not a D365 Sales user, their name migrates as a text custom field Technician__c. If they are a D365 Sales user, we set Opportunity.OwnerId directly.

Notifi tracks scheduled date, scheduled time, and technician timesheets. D365 Sales has no native scheduling table. We create Scheduled_Date__c (Date), Scheduled_Time__c (Time), and Hours_Logged__c (Number) custom fields on Opportunity to preserve scheduling context for downstream dispatch rebuild. These fields can be used to generate work‑order reports, calculate technician utilization, and feed Power Automate flows that recreate Notifi's dispatch logic in D365 Sales.

Any Notifi custom properties — e.g., 'Property_Type__c', 'Contract_ID__c', 'Warranty_Expiration__c' — are reviewed during planning. D365 Sales allows custom fields on any table via the Dataverse schema. We create matching fields with the appropriate type (text, number, date, picklist) and map values during migration.

Notifi file attachments on jobs or estimates are downloaded and re-uploaded to D365 Sales as SharePoint document locations attached to the parent Account or Opportunity record. D365 Sales default file size limit is 128MB per file; larger files are chunked or linked.