Migrate from Dynamics 365 Field Service to Freshsales

D365 Accounts map directly to Freshsales Accounts. Address, phone, industry, employee count, and revenue fields transfer directly. Parent Account hierarchy in D365 maps to Freshsales Parent Account via the same field — circular references are flagged before migration runs. We also map the original owner ID to Owner_Id__c for audit trails and activate duplicate‑detection rules on name and domain to avoid re‑creating records.

D365 Contacts map to Freshsales Contacts with all standard fields: name, email, phone, job title, address. D365 allows multiple primary contacts per account; Freshsales enforces one primary contact per record — we preserve the primary designation and surface secondary contacts as Contact relationship records.

D365 Leads map 1:1 to Freshsales Leads. Lead status, lead score, source, and owner fields migrate directly. D365 lead scoring model values transfer to Freshsales as a custom numeric field since Freshsales scoring is AI-driven on Pro+ plans only. We also migrate custom lead attributes to Freshsales custom fields, preserving data like product interest and region. The original D365 lead creation timestamp is stored as Created_Date__c for historical reference.

D365 Opportunities map to Freshsales Deals. Pipeline, stage, amount, close date, probability, and owner transfer directly. D365 opportunity contact roles map to Freshsales Deal Contact associations. Multiple opportunity product lines flatten into Deal Product entries. We also map opportunity fields to Freshsales Deal fields, preserving deal source. Currency values transfer, and the original D365 opportunity creation date is stored as Created_Date__c. Duplicate detection on deal name and account prevents duplicates.

D365 Work Orders map to Freshsales Deals with a custom Work_Order__c checkbox field marking migrated service records. Work Order status maps to a custom pick-list field (Service_Status__c) preserving D365 values: Scheduled, In Progress, Completed, Cancelled, On Hold. Account and Contact links transfer as Deal associations. Service Territory maps to a custom Territory__c field on the Deal.

D365 Work Order Products (line items specifying which products are used per work order) merge into Freshsales Deal Products. Each D365 product line becomes a Product Catalog entry with pricing pulled from D365 Price List lines. Unit, quantity, cost, and discount fields transfer as line-item attributes.

D365 Bookable Resources (technicians, vehicles, equipment) resolve to Freshsales Users by email match. Resource type (User vs. Contact vs. Equipment) is stored as a custom field Resource_Type__c. Unmatched resources are flagged before migration — your team either creates Freshsales users or assigns records to a default owner.

D365 Customer Assets (installed equipment, serial numbers, warranty records, parent-child hierarchies) have no Freshsales equivalent. We create a custom object Field_Service_Asset__c with fields for Asset Name, Serial Number, Status, Account lookup, Parent Asset lookup, Installation Date, and Warranty Expiry. Hierarchy depth is preserved via self-referential Parent_Asset__c field.

D365 Incident Types define common problem categories with associated tasks, products, and pricing. These become a custom object Incident_Type__c in Freshsales linked to the Product Catalog. Task templates associated with each incident type store as a custom text field for manual rebuild reference.

D365 Service Territories define geographic zones that group Bookable Resources. Freshsales has no native territory object for field service. We create Service_Territory__c with Name, City, State, Zip, and timezone fields. Work Orders reference the territory via Territory__c custom field on the Deal.

D365 Bookable Resource Bookings (technician schedule blocks, travel time, break windows) map to Freshsales Events with Type set to 'Field Visit' or 'Travel'. Original booking start/end times, resource assignment, and location transfer. Overlapping bookings on the same day consolidate into daily Event records for cleanliness.

D365 Service Agreements and Preventative Maintenance contracts store as a custom Agreement__c custom object linked to the Account. Contract start date, end date, billing frequency, and SLA terms transfer as custom fields. Active/expired status maps to an Agreement_Status__c pick-list. We also preserve contract value as Contract_Value__c and map renewal dates to Renewal_Date__c for alerts. The Account lookup is set to D365 account, and hierarchies are flattened with a Parent_Agreement__c reference.