Migrate from Service In Sync to Microsoft Dynamics 365 Sales

Service In Sync job model has no native Dynamics 365 equivalent

Service In Sync structures its core workflow around Jobs, Appointments, and Estimates. Dynamics 365 Sales has no Job or Work Order object at the CRM tier—only Opportunities, Quotes, and Activities. Revenue-generating service jobs map to Opportunities, but ongoing service work that has not closed as a deal must land in a custom Service_Job__c Dataverse table. If your Dynamics 365 Sales Professional license is active, the 15-table cap may be hit quickly when combining custom job, payment, review, and recurring-schedule tables. We flag table counts in the schema review and recommend Enterprise licensing if the cap is exceeded before migration runs.

N:N client-to-job associations collapse to a single primary link

Service In Sync allows a single job to be associated with multiple clients, and a client to have multiple jobs. Dynamics 365 Contact links to a primary Account with one AccountId, and additional Account relationships require Account Contact Relationships. We resolve the primary client per job by most-recently-modified date or a rule you specify, then surface remaining client associations as related Contact records linked to the job record. If your business relies heavily on multi-client job billing, we create a custom Job_Clients__c junction table so no association is lost.

Recurring job templates expand into individual records with no native recurrence model

Service In Sync supports recurring job templates (weekly maintenance, monthly service contracts). Dynamics 365 Sales has no native recurrence model for Opportunities or custom job records—Series/Recurrence is available only on Appointments and only with the Field Service add-on. We expand recurring templates into individual job records with a SIS_Recurring_Group__c custom field linking the series. This preserves the schedule history and each instance's outcome while making it clear the records originated from a template. Your admin can use Power Automate to re-establish recurring job generation post-migration.

Payment and deposit data has no native Dynamics 365 object

Service In Sync tracks payments, partial deposits, and payment status per job. Dynamics 365 Sales has no native payment or deposit record—the closest built-in object is Invoice, which is part of the Order-to-Cash flow and requires Sales Enterprise or Business Central integration. We create a custom Payment__c table linked to each Opportunity or Service_Job__c record. The table stores amount, method, date, and status so payment history is visible on the job record. If you later implement Business Central, the Payment__c table can be replaced by native Invoice records.

Review-booster and follow-up records require a custom table

Service In Sync includes an automated review-request feature that directs happy customers to leave Google, Yelp, or Facebook reviews after job completion. This is a service-business-specific feature with no equivalent in Dynamics 365 Sales. We create a custom Review__c table linked to the Contact or Account, storing the review platform, star rating (if captured), date, and a URL to the external review. Post-migration, you can use Power Automate to trigger review requests from Dynamics 365 based on job completion.