Migrate from ServeManager to Microsoft Dynamics 365 Sales

ServeManager Job maps directly to Dynamics 365 Opportunity. The job's description, due date, and service address become the Opportunity Name, Close Date, and address fields respectively. OpportunityId links to the client's AccountId and the assigned server's ContactId. Job status (Pending, Assigned, Served, etc.) maps via value mapping to Opportunity StageName — each stage name requires a specific mapping entry in the migration configuration.

Each ServeManager Attempt row becomes a Dynamics 365 Task record. The Task's RegardingObjectId (lookup) links back to the parent Opportunity by matching Job ID to Opportunity's Source_Job_ID__c custom field. Attempt status (Successful, Attempted, Not Home, Refused) becomes a custom pick-list field on the Task (new_AttemptStatus__c). Original attempt timestamps are preserved as the Task's ActualEnd datetime field; new_CreatedDate__c stores the ServeManager creation timestamp.

ServeManager saves GPS coordinates with each attempt. Dataverse has no native geolocation field type. We create two custom Decimal Number fields (new_Latitude__c and new_Longitude__c) on the Task table and populate them from the attempt's latitude/longitude values during migration. These fields can be used for map visualizations in Power BI reports post-migration.

ServeManager photos attached to attempts (proof of service images) have no direct Dataverse equivalent. We download the images from ServeManager's file storage, upload them to a SharePoint document library linked to the Opportunity via RegardingObjectId, and create a Note record in Dynamics 365 referencing the SharePoint URL. This preserves the attachment without embedding binary data in Dataverse.

ServeManager captures electronic signatures as part of affidavit completion. Signatures are stored as image files in ServeManager. We download each signature image, upload to SharePoint under the related Opportunity's document library, and store the SharePoint URL in a new text field (new_Signature_URL__c) on the Task. This keeps the signature auditable and accessible from within Dynamics 365.

ServeManager Company records (the law firms and agencies that hire process servers) map to Dynamics 365 Account records. The company's name becomes Account.Name, primary contact name becomes the primary Contact's Full Name, and the billing address maps to Account.Address fields. If the Company has multiple contacts in ServeManager, additional contacts are created as related Contact records with AccountId pointing to the migrated Account.

ServeManager stores contact name, email, and phone on the Company record. These become a Dynamics 365 Contact with the AccountId lookup set to the migrated Account. Additional contacts on the Company record become additional Contact rows with the same AccountId. Email maps to Contact.Email, phone to Contact.Phone, and the contact's role (e.g., Paralegal, Office Manager) is stored in a custom field new_ContactRole__c.

ServeManager Invoice records (created per completed Job) map to Dynamics 365 SalesOrder records. Invoice number becomes SalesOrder.SalesOrderNumber, total amount maps to SalesOrder.TotalAmount, and invoice date becomes SalesOrder.DateFulfilled. The SalesOrder's CustomerId links to the Account from the Job's associated Company. Invoice status (Paid, Pending, Overdue) maps via value mapping to SalesOrder.StatusCode.

ServeManager records Stripe transaction IDs and payment dates against invoices. Dynamics 365 Sales has no native payment transaction table. We create two custom fields on the SalesOrder table: new_PaymentDate__c (Date) and new_StripeTransactionID__c (Text) to store these values. If the firm uses Business Central for accounting, the SalesOrder syncs to a Purchase Invoice there.

ServeManager tracks server compensation per job (default rates, overrides, and payment status). Dynamics 365 Sales has no native payroll table. We create a custom Server_Payables__c table with fields for Server__c (Contact lookup), Job__c (Opportunity lookup), Rate__c (Currency), Amount_Paid__c (Currency), and Payment_Status__c (pick-list). Each serve job's server payable row becomes a record in this table linked to both the Opportunity and the server's Contact.

ServeManager's server agent records (used for assignment tracking and payroll) map to Dynamics 365 Contact records. The server's name, email, phone, and default service rate become Contact fields and custom fields on the Contact record. We flag server Contacts with a custom Boolean field new_IsProcessServer__c so they can be filtered in Dynamics 365 views and reports.

ServeManager lets firms assign affidavit templates per job type. Since affidavit template definitions are not exportable, we store the template name assigned to each job in a custom text field new_AffidavitTemplate__c on the Opportunity. Firms then rebuild affidavit generation using Power Automate and Dynamics 365's document-generation capabilities.