Migrate from WorkBuddy to Microsoft Dynamics 365 Sales

WorkBuddy contacts and assigned technicians map to Dynamics 365 Contact records. The email field serves as the key for owner resolution against Dynamics users. Phone, mobile, job title, and address fields carry over directly to standard Dynamics fields, though WorkBuddy composite address fields may require splitting into Dynamics address1 component fields to preserve street, city, state, and postal data separately.

WorkBuddy company records representing client businesses map directly to Dynamics 365 Account records. Company name, domain and website URL, industry classification, employee count, and annual revenue all map to their corresponding standard Account fields. Parent-company hierarchies and subsidiary relationships in WorkBuddy translate directly to the Account.ParentId reference field, preserving organisational structures across the migration.

WorkBuddy jobs do not map to any native Dynamics object. We provision a custom Work Order table in Dataverse with fields for job number, title, status, priority, scheduled start and end dates, quoted amount, invoiced amount, and payment status. This custom table becomes the primary carry-over record for preserving the complete job history from WorkBuddy within the Dynamics environment.

Where WorkBuddy jobs represent billable client engagements, they can alternatively map to a Dynamics Opportunity record using a 'Job' record type. This approach is useful when the sales team needs job revenue reflected in the pipeline view. The custom Work Order table remains as the detailed record for line items and job-specific fields, while the Opportunity provides pipeline-stage management and sales-cycle visibility.

WorkBuddy line items representing labour hours, material charges, and subcontractor costs map to a custom Work Order Item table with a lookup relationship to the parent Work Order record. Each line item includes description, quantity, unit price, total amount, and a line-type discriminator field to identify whether the item represents labour, materials, or subcontractor expense.

WorkBuddy asset records representing equipment registered to a site or linked to a job map to a custom Asset Registry table in Dataverse. The table captures asset name, serial number, manufacturer make and model, installation date, warranty expiry, and a lookup relationship to the associated Account and Site location. This structure enables asset tracking across clients and job sites.

WorkBuddy safety checklists, compliance certificates, and SWMS/JSEA document references are exported as structured records in a custom Safety Compliance table linked to the Work Order or Asset. Checklist responses, expiry dates, certification levels, and auditor details are preserved as data fields. The binary checklist form PDFs are exported as document attachments on the related record.

WorkBuddy subcontractor assignments linked to a job and a subcontractor contact map to a custom junction table. Subcontractor contact details carry over as Dynamics Contact records. The assignment record links the subcontractor contact to the Work Order with role, trade specialty, contract rate, and assignment status fields to track which subcontractors are engaged on each job.

WorkBuddy file attachments including photos, PDFs, signed forms, and inspection reports are downloaded and re-uploaded to the associated Dynamics record's document location. Files are stored in the integrated SharePoint library or as Dynamics native attachments based on your environment configuration. Dataverse default file size limit of 32 MB per file is respected throughout the transfer process.

WorkBuddy users and assigned technicians are resolved by email address matching against Dynamics 365 SystemUser records. Unmatched users receive a fallback owner assignment to a designated Dynamics administrator account, ensuring no record lands without an owner. WorkBuddy admin users without a corresponding Dynamics login become inactive user references preserved in a custom text field for audit traceability.

WorkBuddy's native scheduling board, dispatch logic, and technician availability rules have no equivalent in Dynamics 365 Sales. We export all scheduling data as a structured JSON artifact including technician working hours, job time slots, travel buffers, recurring availability patterns, and dispatch rules. This export serves as a rebuild reference for Power Automate flows or Dynamics 365 Field Service Universal Resource Scheduling.

WorkBuddy workflow rules, approval chains, notification triggers, and conditional routing logic are WorkBuddy-native and cannot be transferred programmatically. We export the complete workflow definitions as a structured reference document with trigger conditions, action sequences, and branch logic. A Power Automate rebuild guide accompanies the export, providing step-by-step guidance for recreating equivalent automation in the Dynamics environment.