Migrate from Kickserv to Microsoft Dynamics 365 Sales

Kickserv Customer maps directly to Dynamics 365 Account. Account carries the company name, address, phone, and industry. Kickserv customers with no address (e.g., individual homeowners) may need to be evaluated for Contact-only records if they will never generate a sales opportunity.

Kickserv Contact maps to Dynamics 365 Contact with a required AccountId lookup. Contacts without a primary customer in Kickserv are flagged and assigned to a placeholder 'Unassigned Customer' Account so the lookup field is never null in Dynamics. This approach ensures referential integrity during migration and allows administrators to later reassign contacts to the correct accounts.

Kickserv Job has no direct Dynamics 365 Sales equivalent — it maps to the Field Service Work Order table (msdyn_workorder) if Dynamics 365 Field Service is licensed. Each work order carries a primary customer (Account), a primary contact, a service territory, a work order type, and status. Kickserv job status maps to msdyn_systemstatus with a value-by-value lookup.

If Dynamics 365 Field Service is not in scope, Kickserv Jobs migrate as Dynamics 365 Cases (incident table). The Case title carries the job name, the Account lookup links to the customer, and a custom Kickserv_Job_ID__c field preserves the source reference. Case origin and priority map from Kickserv job priority pick-list values.

Kickserv Estimate maps to Dynamics 365 Quote. The estimate total maps to EstimatedValue, line items map to Quote Details (quotedetail), and the estimate's status (Draft, Sent, Approved, Declined) maps to the Dynamics quote statecode. Original estimate date and expiry date migrate as custom fields if required for audit continuity.

Kickserv Invoice maps to Dynamics 365 SalesOrder (when open) or Invoice (when posted). The Kickserv invoice total, balance due, and payment status map to corresponding fields. Note that Dynamics 365 Sales does not have a built-in accounting module — teams using QuickBooks in Kickserv must connect Dynamics Sales to Business Central or a third-party accounting connector post-migration.

Kickserv Employees (technicians, dispatchers, admins) resolve by email to Dynamics 365 SystemUser records. Active Kickserv employees map to active Dynamics users; archived employees map to inactive users with a custom Kickserv_Employee_ID__c field for reference. User security roles are assigned based on Kickserv role (Admin, Technician, Office Staff).

Kickserv schedule events (job assignments, time blocks) map to Dynamics 365 Field Service BookableResourceBooking. Each booking links a BookableResource (the technician) to a Work Order (the job) with a start/end time window. If Field Service is not licensed, events migrate as Dynamics 365 Activities (calendar).

Kickserv time entries map to the Time Entry table in Dynamics 365 Field Service (msdyn_timeentry) if Field Service is licensed. Each entry links to a BookableResourceBooking, carries hours, and includes a billable/non-billable flag. Original start/end timestamps and break deductions are preserved.

Kickserv Items (parts, materials, service line items) map to Dynamics 365 Product. Product type (Inventory Item, Service, Non-inventory) maps from the Kickserv item type. Unit price and cost map to Price and StandardCost on the Product. Kickserv item categories map to Product Type or a custom field if finer grouping is needed.

Kickserv notes migrate as Dynamics 365 Annotations (notes) on their parent record (Account, Contact, Work Order, or Case). Rich-text content is preserved in the Annotation.body field. Original note creation date and author (employee email) migrate as custom fields if not automatically carried.

Kickserv charges (line items on jobs or invoices) map to Dynamics SalesOrderDetail. Payments recorded in Kickserv migrate as payment records with a custom reference back to the source Kickserv Payment ID. Since Dynamics 365 Sales lacks a native payments ledger, payment history is preserved in a custom entity for audit purposes.

Kickserv custom fields on Jobs (e.g., custom property inspection types, site access codes) require new custom columns in Dynamics. We create the column using the same data type (picklist, text, number, date) and map each value during migration. Custom field metadata is documented in the pre-migration schema plan so Dynamics admins can add columns before the data load runs.

Kickserv Tags (used for job categorization, service types, or dispatch labels) have no native Dynamics 365 Sales equivalent. Tags migrate as records in a custom msdyn_tag table with a many-to-many relationship to Work Orders and Cases. Tags can also be mapped to Dynamics Territory or a custom pick-list on the work order for simpler filtering.