Migrate from Service Buddy to Microsoft Dynamics 365 Sales

Service Buddy Customer maps to Dynamics 365 Account (company/retail-location record) with Contact sub-record for the primary point of address. Service Buddy stores one contact per customer; we create the Account first, then the Contact linked via AccountId lookup. The Account serves as the parent entity holding company name and address, while the Contact captures individual details and links via parentcustomerid relationship.

Service Buddy customer contact information (email address, phone number, mobile phone) maps directly to Contact.emailaddress1, Contact.telephone1, and Contact.mobilephone in Dynamics 365 Sales. All three phone/email fields migrate with empty transformation. This direct mapping preserves the original contact data without requiring data manipulation or format conversion, ensuring your customer communication channels transfer completely and accurately into the new CRM system.

Service Buddy stores customer address as a structured block. We split this into Account.address1_line1, address1_city, address1_stateorprovince, address1_postalcode, and address1_country. Service Buddy's 'address2' for billing address maps to address2 fields on the Account record. The address components follow the standard Dynamics 365 address schema, enabling geocoding, territory assignment, and map-based visualization.

Service Buddy Quote maps directly to Dynamics 365 Sales Quote entity. Quote number, name, total amount, status (Draft, Sent, Approved, Expired, Lost), and created date migrate. Quote line items map to QuoteDetail records with product reference, quantity, unit price, and discount.

Service Buddy quote line items with flooring products map to Dynamics 365 QuoteDetail records referencing Product records. Product name, SKU, description, and unit price migrate to the Product table. We preserve product categories as a custom picklist field on Product.

Service Buddy Job has no direct Dynamics 365 equivalent. We create a custom sb_Job__c table in Dataverse to store job number, job status, scheduled date, crew assigned, installer names, installation phases, room-level details, and completion notes. The custom entity links to the originating Account and Quote.

Service Buddy job statuses (Scheduled, In Progress, Completed, Cancelled) map to a custom picklist on sb_Job__c. We create the picklist with Service Buddy's exact status values preserved for reporting continuity against historical job records. The picklist maintains the original status terminology without modification, ensuring that historical reports and dashboards continue to display job status information accurately after migration. This approach prevents data interpretation issues and supports uninterrupted operational analytics.

Service Buddy payment records (processed via BuddyPay) map to a custom sb_Payment__c entity in Dynamics 365. Fields include payment ID, amount, date, payment method (card, ACH, Apple Pay), associated Quote/Job reference, and QuickBooks Online sync status. We preserve original transaction timestamps.

Service Buddy inventory products map to Dynamics 365 Product records. Product name, SKU, description, unit price, and quantity on hand migrate. Service Buddy's product categories map to a custom Product_Category__c picklist. Vendor records may require a separate custom entity or Contact-role mapping.

Service Buddy's QR-code label system has no Dynamics 365 equivalent. We store the QR-code identifier as a custom text field (sb_QRCode__c) on the Product record. QR-scan functionality requires a separate Power App or third-party solution post-migration. The QR-code identifier is preserved as a text string, allowing product lookup by scanning if a Power App is built. However, the scanning workflow and label-generation capabilities must be reconstructed using Power Platform tools.

Service Buddy PO and Work Order records require a custom sb_PurchaseOrder__c entity. Fields include PO number, vendor reference, line items, status, expected delivery, and associated inventory items. Dynamics 365 Supply Chain Management handles PO natively, but Sales standalone does not.

Service Buddy team members (owners of jobs, quotes, customers) resolve to Dynamics 365 Sales SystemUser records by email match. Unmatched owners are flagged before migration. Their records can be assigned to a fallback user or invited to Dynamics 365 before the migration runs.

Service Buddy BuddyAI insights (sales performance metrics, daily summaries, AI-generated suggestions) have no Dynamics 365 equivalent. We create custom fields to store the most recent AI summary and performance snapshot as a reference record on the Account for historical continuity.

Service Buddy's QuickBooks Online integration flags payments that have been synced to QBO. We preserve this flag as a custom field (sb_QBOSynced__c) on the payment record to prevent duplicate payment entry if QBO sync is re-established in Dynamics 365. When reconnecting QBO integration, the sync logic references this flag to skip already-reconciled transactions, maintaining accounting accuracy and preventing duplicate entries in both systems.