Migrate from ServiceTitan to Microsoft Dynamics 365 Sales

ServiceTitan customers map to Dynamics 365 accounts via a direct object transformation. For customers with multiple service locations, we create one account record and attach multiple address records or child contact records to represent each location separately. The customer's primary contact person maps to the account's primary contact role, and any additional contacts on the customer record become linked contact records under the same account parent. This preserves the hierarchical relationship between the customer entity and its associated contact persons in the destination CRM.

Customer contact persons map to Dynamics 365 contacts. We resolve the primary contact on the customer record to a contact with email, phone, and mailing address. Additional contacts on the customer record map to additional contact records linked to the same account.

ServiceTitan allows multiple service locations per customer — a key FSM feature with no direct CRM equivalent. We map the primary service location to the account's billing or shipping address. Secondary locations are either added as address records on the account or as child contact records with an address-purpose flag stored in a custom field.

Jobs are the core ServiceTitan record and require deliberate mapping. We map jobs to Dynamics 365 opportunities when the use case is tracking service revenue through a pipeline. Each job maps as one opportunity with the customer account linked, the job amount as estimated value, and job status translated to an opportunity stage via value mapping.

For teams using ServiceTitan primarily as a work-order system rather than a sales-tracking tool, jobs map better to cases in Dynamics 365 Customer Service. We configure the mapping direction based on your primary use case during the planning phase — this is a customer choice, not an automatic decision.

ServiceTitan job statuses (Scheduled, In Progress, On Hold, Completed, Cancelled) map to Dynamics 365 opportunity stage values via value-by-value mapping. We apply the mapping during migration and flag any status that has no direct equivalent in your Dynamics stage set so your admin can pre-create the needed stages.

ServiceTitan invoices map to Dynamics 365 invoices with line items preserved. Invoice details require a product catalog in Dynamics to link line items to the Product table — we deliver a product-import template alongside the migration so your admin can pre-populate the catalog before the invoice records load.

ServiceTitan estimates map directly to Dynamics 365 quotes with full fidelity on the header and line-item levels. Estimate line items map to quote details using the same product-catalog dependency as invoices — the Dynamics Product table must exist before quote line items can link to product records rather than arriving as free-text lines. The ServiceTitan estimate expiration date translates to the quote's Delivery_Expires field in Dynamics, preserving the original validity window so sales representatives know exactly when each quote becomes stale and requires refresh or re-approval before sending to the customer.

ServiceTitan technicians are resource records with schedule and shift data. Dynamics 365 users are license-based. We split the mapping: technicians who need CRM access become Dynamics system users resolved by email match; technicians without CRM access become contact records with the technician name preserved in a custom field on every related job/opportunity.

ServiceTitan pricebook entries do not have a native CRM equivalent in Dynamics 365 Sales. We deliver a CSV product-import template with all ServiceTitan materials, parts, and labor codes so your admin can create product records in Dynamics before the migration runs. Line items on jobs, invoices, and estimates depend on this setup.

ServiceTitan custom fields map to Dynamics 365 custom fields on the target object. Field type compatibility must be verified before migration — free-form ServiceTitan fields that contain mixed data types may need type conversion or splitting into multiple typed fields in Dynamics. We audit all custom fields during the planning phase and flag type mismatches.

ServiceTitan tracks job source (Marketing, Referral, Repeat, etc.) as a standard field. Dynamics 365 has no native job-source field on opportunities. We preserve the value as a custom pick-list field (Job_Source__c) on the opportunity so reporting on revenue by source remains possible in Dynamics.