CRM migration
Field-level mapping, validation, and rollback between Service Toolz and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Service Toolz
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
14 of 14
objects map 1:1 between Service Toolz and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Service Toolz is a field-service-first platform built around work orders, technician dispatch, quoting, and invoicing — its data model centers on customers, work orders, line items, and scheduling. Microsoft Dynamics 365 Sales runs on the Dataverse and organizes data around Accounts, Contacts, Leads, Opportunities, Quotes, Orders, and Activities. The migration carries every standard object from Service Toolz (customers, contacts, work orders, quotes, invoices, products, and custom properties) into the corresponding Dynamics 365 Sales entities. The primary translation challenge is converting Service Toolz work orders into Dynamics 365 Sales Opportunities or custom tables, mapping its flat customer model to Accounts with Contact hierarchies, and resolving Service Toolz users by email match to Dynamics 365 system users. Workflows, scheduling rules, and automation logic do not migrate — we export those definitions as a reference document for your Dynamics admin to rebuild in Power Automate. We use scoped read access against the Service Toolz API for extraction and the Dataverse Web API for ingestion, respecting per-user rate limits throughout.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Service Toolz platform overview
Scorecard, SWOT, gotchas, and pricing for Service Toolz.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Service Toolz object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Service Toolz
Customer
Microsoft Dynamics 365 Sales
Account
1:1Service Toolz customers map directly to Dynamics 365 Sales Accounts. The customer name becomes Account Name, and the primary contact within the account links via the Primary Contact lookup. If the source customer is an individual rather than a business, route it to the Contact entity instead.
Service Toolz
Contact (on Customer)
Microsoft Dynamics 365 Sales
Contact
1:1Service Toolz contact records attached to a customer map to Dynamics 365 Sales Contacts under the corresponding Account. The AccountId lookup is set to the migrated Account record. Multiple contacts per account are preserved as individual Contact records. Each contact inherits the parent's address and communication preferences unless explicitly overridden during migration.
Service Toolz
Work Order
Microsoft Dynamics 365 Sales
Opportunity (or custom WorkOrder table)
1:1Work orders are the core entity in Service Toolz. We map them to Dynamics 365 Sales Opportunities by default, using the work order name as Opportunity Name and the estimated value as Amount. If your work orders contain multi-phase stages, we create a custom WorkOrder table in Dataverse rather than forcing them into the standard Opportunity stage pipeline.
Service Toolz
Work Order Status
Microsoft Dynamics 365 Sales
Opportunity StageName or custom Status field
1:1Service Toolz work order status values (Scheduled, In Progress, Completed, On Hold, Cancelled) map to Dynamics 365 Sales Opportunity StageName values or a custom Status pick-list on the custom WorkOrder table. Each value requires explicit value-by-value mapping before migration. Inactive statuses like Cancelled may be mapped to the Closed Lost state, while active statuses follow the standard opportunity pipeline stages.
Service Toolz
Work Order Line Item / Product
Microsoft Dynamics 365 Sales
Opportunity Product (opportunityproduct)
1:1Each line item on a Service Toolz work order becomes an Opportunity Product record linked to the target Opportunity. The product name, quantity, unit price, and discount fields translate directly. Unmapped products are created as new product records in Dynamics 365 Sales during migration.
Service Toolz
Quote
Microsoft Dynamics 365 Sales
Quote
1:1Service Toolz quotes map to Dynamics 365 Sales Quote records. The Quote is created in Open status and linked to the corresponding Opportunity. Active quotes that are Accepted or Revised map to Closed statuses — we preserve the last known status at migration time.
Service Toolz
Invoice
Microsoft Dynamics 365 Sales
Invoice
1:1Service Toolz invoices migrate to Dynamics 365 Sales Invoice records. Invoices are created in Closed status with the original invoice date, total amount, and line items.发票 numbers from Service Toolz are preserved in the Invoice Number field for audit continuity.
Service Toolz
Product / Inventory Item
Microsoft Dynamics 365 Sales
Product
1:1Service Toolz inventory products map to Dynamics 365 Sales Product records. Unit price, cost, product type (bundles, individual items), and product description migrate. If a product exists in Service Toolz without a price, we create it as a draft product in Dynamics 365 Sales for review.
Service Toolz
Technician / Staff
Microsoft Dynamics 365 Sales
SystemUser
1:1Service Toolz technicians and staff members are resolved by email match against Dynamics 365 Sales system users. Matched users become the OwnerId on migrated records. Technicians without a corresponding Dynamics user are flagged as unresolved and assigned to a fallback owner — your admin invites them to Dynamics 365 before the final run.
Service Toolz
Custom Property (Customer)
Microsoft Dynamics 365 Sales
Custom field (new_CustomPropertyName) on Account
1:1Service Toolz custom properties on customers are created as new_ prefixed custom fields on the Dynamics 365 Sales Account table. Field data type is preserved — text fields become nvarchar, number fields become decimal or integer, date fields become datetime. Your Dynamics admin pre-creates these fields before migration or we create them as part of the migration plan.
Service Toolz
Custom Property (Work Order)
Microsoft Dynamics 365 Sales
Custom field (new_CustomPropertyName) on Opportunity or custom WorkOrder table
1:1Custom properties stored on Service Toolz work orders map to custom fields on the target Dynamics 365 entity. Any custom properties referencing lookup values in Service Toolz require explicit value mapping — pick-list values must be recreated in Dynamics 365 Sales before migration.
Service Toolz
Attachment / File
Microsoft Dynamics 365 Sales
Note (annotation) or SharePoint Document Location
1:1Files attached to Service Toolz work orders and customers are extracted and re-uploaded as Notes (annotation) records in Dynamics 365 Sales. For large attachments or documents intended for collaborative use, we map them to SharePoint Document Locations linked to the target record. File size limits of 25 MB per file in Dataverse apply.
Service Toolz
Scheduling / Calendar Event
Microsoft Dynamics 365 Sales
Appointment (appointment) entity
1:1Service Toolz scheduling entries and calendar events map to the Dynamics 365 Sales Appointment entity with original start and end times, assigned technician (resolved by email), and the linked work order reference preserved in the regardingobjectid field.
Service Toolz
Payment Record
Microsoft Dynamics 365 Sales
Invoice (Payment Terms) or custom Payment table
1:1Service Toolz payment records and transaction history do not have a direct Dynamics 365 Sales equivalent. We migrate payment dates and amounts as read-only fields on the Invoice record or as a custom Payment History table in Dataverse — your finance team reconciles these against Business Central after go-live. This ensures audit continuity while maintaining the integrity of your financial records across systems.
| Service Toolz | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Customer | Account1:1 | Fully supported | |
| Contact (on Customer) | Contact1:1 | Fully supported | |
| Work Order | Opportunity (or custom WorkOrder table)1:1 | Fully supported | |
| Work Order Status | Opportunity StageName or custom Status field1:1 | Fully supported | |
| Work Order Line Item / Product | Opportunity Product (opportunityproduct)1:1 | Fully supported | |
| Quote | Quote1:1 | Fully supported | |
| Invoice | Invoice1:1 | Fully supported | |
| Product / Inventory Item | Product1:1 | Fully supported | |
| Technician / Staff | SystemUser1:1 | Fully supported | |
| Custom Property (Customer) | Custom field (new_CustomPropertyName) on Account1:1 | Fully supported | |
| Custom Property (Work Order) | Custom field (new_CustomPropertyName) on Opportunity or custom WorkOrder table1:1 | Fully supported | |
| Attachment / File | Note (annotation) or SharePoint Document Location1:1 | Fully supported | |
| Scheduling / Calendar Event | Appointment (appointment) entity1:1 | Fully supported | |
| Payment Record | Invoice (Payment Terms) or custom Payment table1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Service Toolz gotchas
No public API means migration relies on report exports
Quote-to-Work Order ID linkage requires manual mapping
Inventory quantities are point-in-time and may drift
Add-on modules gate feature data
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discover Service Toolz data model and Dynamics 365 destination schema
We export a full schema inventory from Service Toolz via its REST API — all record types, custom properties, relationships, and attachment metadata. In parallel, we inspect the target Dynamics 365 Sales environment to identify existing tables, custom fields, and security roles. This produces a delta report: which Service Toolz objects have direct equivalents in D365, which require custom tables, and which custom properties need new Dataverse fields pre-created before data can land.
Resolve users by email and pre-create missing Dataverse fields
Service Toolz technicians and staff are matched to Dynamics 365 Sales system users by email address. Matched users become OwnerId on migrated records. We flag every unresolved technician for your admin to provision a D365 user account. Simultaneously, we deliver a Dataverse field creation manifest — every custom property from Service Toolz that lacks a D365 equivalent, with recommended data type and pick-list values, so your admin (or our team) creates the fields before the migration run.
Run a sample migration with field-level diff
A representative slice of 100–500 records migrates first — spanning customers, contacts, work orders, quotes, and invoices. We generate a field-level diff comparing source values to destination values for every mapped field. You verify that work-order-to-opportunity translation, custom property preservation, and user ownership are correct before the full run commits. This step surfaces any value-mapping gaps and gives your team a chance to adjust the field mapping plan without touching production data.
Execute full migration with delta-pickup window
The full dataset migrates using Dataverse Web API batch operations, with request pacing to stay within the 6,000-request-per-5-minute-per-user limit. A delta-pickup window of 24–48 hours captures any records created or modified in Service Toolz during the cutover. All operations are logged to an audit trail. If reconciliation fails, one-click rollback reverts the destination to its pre-migration state and the delta records are held for re-injection.
Validate record counts, field completeness, and attachment integrity
Post-migration, we run automated validation checks: record count parity between source and destination for each object type, field-population rate (no nulls where values existed in Service Toolz), and attachment hash verification for re-uploaded files. We deliver a validation report within 4 hours of the full run completing. Any gaps are addressed by a targeted re-migration of the affected record batches before your team begins user acceptance testing.
Platform deep dives
Service Toolz
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Service Toolz and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Service Toolz: Not publicly documented.
Data volume sensitivity
Service Toolz doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Service Toolz to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Service Toolz to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Service Toolz
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.