Migrate from ServeCircle to Microsoft Dynamics 365 Sales

ServeCircle customers (businesses that bring in devices for service) map directly to Dynamics 365 Accounts. The customer name becomes Account Name. Address, phone, email, and website fields map field-by-field. Custom fields on ServeCircle customers are migrated as custom fields on the Account record. ServeCircle branch assignments are preserved as a custom Branch__c pick-list or lookup field on the Account.

ServeCircle stores contact persons (device owners, requestors) as separate records linked to a Customer. These map to Dynamics 365 Contacts. Each Contact is linked to its parent Account via the AccountId lookup. Multiple contacts per customer are supported natively in Dynamics — no N:N collapse required as in some CRM-to-CRM migrations.

ServeCircle Job Sheets have no native equivalent in Dynamics 365 Sales. We create a custom ServicircleJobSheet__c table in Dynamics to preserve the full job sheet structure — service type, assigned technician, parts used, status history, customer feedback rating, branch, and create/update timestamps. Each job sheet is linked to the originating Account and Contact via lookups. Alternatively, for simpler migrations, job sheets map to Cases with a ServicircleJobSheetId__c custom field for reference.

ServeCircle job sheet statuses (e.g., Registered, In Progress, Awaiting Parts, Completed, Delivered) are mapped to a custom pick-list field ServicircleJobSheetStatus__c on the custom ServicircleJobSheet__c table. Status values are mapped one-by-one. Dynamics 365 does not have a native job sheet status concept, so the custom pick-list preserves the full lifecycle without forcing an unnatural mapping to Case status values.

ServeCircle invoices map to Dynamics 365 Sales Invoices. The invoice number becomes the Invoice Name. Total amount, due date, and status (Paid, Pending, Overdue) are mapped field-by-field. ServeCircle invoice line items — which store item name, quantity, rate, and tax — are mapped to Dynamics Invoice Details (invoiceproduct records) by flattening the ServeCircle line-item structure. Payment status from ServeCircle maps to a custom PaymentStatus__c field on the Dynamics Invoice.

ServeCircle Advanced tier includes Service Accounts — client portal access for customers to view job status. In Dynamics 365, these map to the Account record with the Contact record holding the portal contact's email and credentials. We create the Account if it does not already exist from the Customer object, and link the Service Account contact to it. Portal access is not replicated — a new portal setup using Dynamics 365 portals is required post-migration.

ServeCircle inventory items (spare parts, device models, service kits) map to Dynamics 365 Products. Item code becomes Product Number. Item name becomes Name. Description, unit price, and current stock quantity are mapped as custom fields (DefaultUnit__c, StockQuantity__c) since Dynamics 365 Sales does not natively track inventory — inventory management is handled in Business Central or Field Service. If the team uses stock levels for sales报价, we create a custom inventory tracking table.

ServeCircle supports unlimited branches as a native entity. Dynamics 365 Sales has no branch concept. We create a custom Branch__c table (BranchId, BranchName, BranchCode, Address) and add a Branch__c lookup field to the Account object. Each Account is linked to its branch of record during migration. If the team has fewer than 15 distinct branches, this fits within Sales Professional limits using the Account custom field only. More branches require the full custom table and may push toward Enterprise licensing.

ServeCircle technicians and staff are resolved by email match to Dynamics 365 System Users. Unmatched users are flagged before migration. Each Job Sheet's assigned technician is stored as a custom Technician__c lookup field on the ServicircleJobSheet__c table, pointing to the matched SystemUser. OwnerId on all records is set to the matched SystemUser.

ServeCircle Advanced tier supports quotations and approval workflows. These map to Dynamics 365 Quotes. Quote name, total amount, status, and expiry date map field-by-field. The approval routing that existed in ServeCircle is not preserved — it must be rebuilt in Dynamics 365 using the native quote approval process or Power Automate.

ServeCircle Advanced tier collects customer reviews and feedback ratings. Dynamics 365 Sales has no native review mechanism. We create a custom ServicircleReview__c table (linked to Account and Contact) to store review text, rating, and submission date. Automated review request triggers from ServeCircle cannot migrate — they must be rebuilt using Dynamics 365 Customer Voice or Power Automate.

ServeCircle file attachments (device photos, signed forms, job sheet PDFs) are re-uploaded to SharePoint via Dynamics 365's native SharePoint integration and linked to the relevant Account, Contact, or ServicircleJobSheet__c record. If SharePoint integration is not enabled, files are stored as Notes attachments. File size limits (default 128MB per file in Dynamics) are respected during re-upload.