Migrate from Fieldmagic to Microsoft Dynamics 365 Sales

Fieldmagic Customers map directly to Dynamics 365 Sales Accounts. Customer type (company vs. individual) determines whether Account is Organization or Person. Multi-site customers generate one primary Account record with Site data stored as custom address fields or separate address records.

Fieldmagic Sites represent physical service locations. Each Site maps to Address fields on the Account or a custom Address__c table in Dataverse. Sites linked to a Customer generate parent-Account lookups; standalone sites require an Account record. Site-specific notes and location codes migrate as custom fields.

Fieldmagic Contacts map 1:1 to Dynamics 365 Sales Contacts. The Contact's primary Customer becomes the AccountId lookup. Job-related contacts without a Customer association attach to a default placeholder Account. Email, phone, and job title fields map directly. Additional details such as address and notes are also migrated as custom fields.

Fieldmagic Jobs are the core record. They contain job details, status, assigned technician, site link, asset link, parts, labor, and billing info. In D365 Sales, Jobs do not map to a native entity — FlitStack creates a custom Job__c table in Dataverse and maps Job Status to a custom pick-list. Job financial totals (labor + parts) can also populate Opportunity Amount for pipeline visibility.

Fieldmagic job statuses (e.g., Scheduled, In Progress, On Hold, Completed, Cancelled) map to a custom pick-list on the Job__c table. Status probability and forecast-category assignment requires D365 admin configuration. FlitStack delivers a value-map spec as part of the migration plan.

Fieldmagic Asset Types categorize equipment (e.g., HVAC Unit, Refrigerator, Generator). They map to either a custom AssetType__c table or D365 Sales Products if the asset is sold. Which approach depends on whether the organization needs asset tracking as a service offering or product-catalog management.

Fieldmagic Assets — individual equipment items — migrate to a custom Asset__c table in Dataverse. Each Asset links to its Site (address) and Asset Type (custom lookups). Asset serial number, make/model, and install date migrate as fields. Maintenance history migrates as related Asset Service Records.

Fieldmagic records each service event on an Asset (what was done, when, by whom, and at what cost). These migrate as related records on the Asset__c table or as separate AssetServiceRecord__c entries. Original timestamps and technician assignments are preserved. and provide full service history.

Fieldmagic Quotes contain materials and labor lines, approval status, and conversion to Jobs. They map to D365 Sales Quotes with line items for materials and labor. Quote status (Draft, Sent, Accepted, Lost) maps to D365 Quote Status. If the Quote converted to a Job, the corresponding Job__c record links back to the Opportunity.

Fieldmagic Quote Line Items (materials, labor hours, fixed-price tasks) map to D365 Quote Detail (Opportunity Product) records. Unit price and quantity map directly; line-type flags (material vs. labor) become custom fields on the product line because D365 has no native line-type distinction.

Fieldmagic office users map to Dynamics 365 Sales users. Matching happens by email address. Unmatched users are flagged before migration — your D365 admin creates the user record first, or records reassign to a fallback owner. Mobile-only technicians may not need D365 user licenses if they won't access the CRM directly.

Fieldmagic Invoices (generated from Jobs) map to D365 Sales Invoice records if the D365 Finance module is active, or to a custom Invoice__c table for standalone CRM deployments. Invoice status, total amount, and line items preserve the original values. across the migration.

Fieldmagic custom fields on any object map to custom columns on the corresponding D365 Dataverse table. Data type mapping handles text, number, date, and pick-list fields. Complex custom objects in Fieldmagic map to custom Dataverse tables with appropriate lookups. and relationships.