CRM migration

Migrate from Service Toolz to Microsoft Dynamics 365 Sales

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 logo

Service Toolz

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

14 of 14

objects map 1:1 between Service Toolz and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Service Toolz logo

Service Toolz

What's pushing teams away

  • Pricing is not published, so teams cannot benchmark Service Toolz against Jobber, Housecall Pro, FieldPulse, or ServiceTitan without sales engagement.
  • Smaller public review and integration footprint than market-leading FSM tools — fewer reference deployments to draw confidence from.
  • No marketplace of third-party apps; integrations are limited to QuickBooks Online, Twilio, and Google Calendar advertised on the product site, so connectivity to CRMs, payroll, or BI requires custom work.
  • Mobile field-tech experience is functional but not as polished as the leading vertical platforms (Workiz, FieldPulse, Housecall Pro) which compete hard on UX.
  • Reporting is descriptive (live KPI dashboards) rather than configurable BI — teams wanting cross-business analytics or finance forecasting outgrow it quickly.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Service Toolz objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Service 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)

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Service 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

maps to

Microsoft Dynamics 365 Sales

Opportunity (or custom WorkOrder table)

1:1
Fully supported

Work 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

maps to

Microsoft Dynamics 365 Sales

Opportunity StageName or custom Status field

1:1
Fully supported

Service 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

maps to

Microsoft Dynamics 365 Sales

Opportunity Product (opportunityproduct)

1:1
Fully supported

Each 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

maps to

Microsoft Dynamics 365 Sales

Quote

1:1
Fully supported

Service 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

maps to

Microsoft Dynamics 365 Sales

Invoice

1:1
Fully supported

Service 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

maps to

Microsoft Dynamics 365 Sales

Product

1:1
Fully supported

Service 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

maps to

Microsoft Dynamics 365 Sales

SystemUser

1:1
Fully supported

Service 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)

maps to

Microsoft Dynamics 365 Sales

Custom field (new_CustomPropertyName) on Account

1:1
Fully supported

Service 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)

maps to

Microsoft Dynamics 365 Sales

Custom field (new_CustomPropertyName) on Opportunity or custom WorkOrder table

1:1
Fully supported

Custom 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

maps to

Microsoft Dynamics 365 Sales

Note (annotation) or SharePoint Document Location

1:1
Fully supported

Files 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

maps to

Microsoft Dynamics 365 Sales

Appointment (appointment) entity

1:1
Fully supported

Service 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

maps to

Microsoft Dynamics 365 Sales

Invoice (Payment Terms) or custom Payment table

1:1
Fully supported

Service 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.

Gotchas + challenges

What specifically takes care here

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 logo

Service Toolz gotchas

High

No public API means migration relies on report exports

Medium

Quote-to-Work Order ID linkage requires manual mapping

Low

Inventory quantities are point-in-time and may drift

Low

Add-on modules gate feature data

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Dataverse API rate limits can throttle large-volume migrations

    Dynamics 365 Sales runs on the Dataverse Web API with a default limit of 6,000 requests per user per 5-minute window. A large Service Toolz migration with 200,000+ records can exceed this limit during the bulk ingestion phase. FlitStack AI implements request pacing and exponential backoff to stay within limits, and we use the Dataverse Bulk API (batch requests of up to 200 records per operation) for larger loads to reduce the per-request overhead. We monitor the X-ResourceUsage header in API responses and throttle ingestion speed dynamically during the migration run.

  • Work orders without direct Opportunity equivalents require a custom Dataverse table

    Service Toolz work orders carry multi-phase stage data, technician assignments, scheduling windows, and line-item diagnostics that do not fit cleanly into the standard Dynamics 365 Sales Opportunity entity. Dynamics 365 Sales Opportunity does not have native fields for estimated hours, service type, or technician assignment. We create a custom WorkOrder table in Dataverse (prefixed with new_) with the exact fields your Service Toolz work orders use, and then map Opportunity-level fields (name, amount, close date) from the work order header. This avoids data loss but requires your admin to pre-approve the custom table in the target environment before migration.

  • Custom property fields must be pre-created in Dataverse with exact schema before migration

    Service Toolz allows arbitrary custom properties on any record type with no enforced schema. Dynamics 365 Sales requires every custom field to be registered in the Dataverse schema with a defined data type (nvarchar, decimal, datetime, etc.) before data can be written to it. If your Service Toolz instance has custom properties with inconsistent data types (e.g., a field that sometimes holds a number and sometimes free text), we flag each one during the discovery phase and provide a type-resolution recommendation. Custom fields that remain unresolved are written as text with a [REVIEW] prefix for your admin to convert post-migration.

  • Service Toolz scheduling data has no native D365 equivalent — calendar events map to Appointments only

    Service Toolz stores technician schedules, dispatch assignments, and time blocks. Dynamics 365 Sales does not have a native scheduling or dispatch entity — the closest construct is the Appointment entity for calendar-level events. We extract scheduling records from Service Toolz and create Appointment records in Dynamics 365 Sales for each scheduled work order, preserving the technician (resolved by email), start/end time, and regardingobjectid pointing to the migrated work order or Opportunity. The dispatch board and resource scheduling views from Service Toolz do not transfer — your team uses Dynamics 365 Field Service or Power Automate to rebuild those.

  • Invoice payment history does not migrate as financial transactions

    Service Toolz stores payment records linked to invoices. Dynamics 365 Sales Invoice records do not have a native payment sub-grid for individual payment transactions — invoices track total amount and payment terms, not granular payment history. We preserve payment record dates and amounts as a custom Payment_History__c composite field on the Invoice or in a related custom Payment History table in Dataverse. Your finance team reconciles these records against Dynamics 365 Business Central after go-live if accounting-grade accuracy is required.

Migration approach

Six steps for a successful Service Toolz to Microsoft Dynamics 365 Sales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Service Toolz logo

Service Toolz

Source

Strengths

  • Wide vertical coverage including HVAC, plumbing, flooring, pool service, handyman, window cleaning, and telecoms.
  • Bundled CRM, quoting, work order, scheduling, inventory, invoicing, payments, and timesheet modules.
  • Native QuickBooks Online, Twilio (SMS), and Google Calendar integrations.
  • Mobile field-tech app removes paper work orders.
  • Live operational reports including job profit/loss, estimated vs actual hours, and completion percentage.

Weaknesses

  • Pricing not published; quote-only.
  • Small public review footprint vs Jobber, Housecall Pro, or ServiceTitan.
  • Limited third-party integration ecosystem (QuickBooks, Twilio, Google Calendar only).
  • Mobile UX less polished than category-leading FSM apps.
  • Reporting is dashboard-style rather than configurable BI.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Service Toolz and Microsoft Dynamics 365 Sales .

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Service Toolz: Not publicly documented.

  • Data volume sensitivity

    B

    Service Toolz doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Service Toolz to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Service Toolz to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Service Toolz to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Service Toolz to Dynamics 365 Sales migrations complete in 48–72 hours of clock time for under 50,000 records. Larger setups with 200,000+ records, multi-phase work orders, or custom Dataverse tables extend to 7–14 days. The longest planning step is resolving user accounts and pre-creating custom fields in Dataverse before data can be written to them. Discovery, schema mapping, and environment validation typically consume the first 3–5 business days of the project timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Service Toolz.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day