Migrate from Oracle Field Service Cloud to Microsoft Dynamics 365 Sales

Oracle Activities are work orders with status, priority, time entries, parts consumed, and technician assignments. Dynamics Cases (Incidents) hold problem descriptions, priority, status, and resolution notes. FlitStack maps Activity.description to Case.title, Activity.status to Case.statuscode, Activity.priority to Case.priority, Activity.createdDate to Case.createdon (preserved as Original_Created_Date__c), and Activity.startDate/endDate to Case fields. Parts used and time entries migrate as Case notes or custom sub-entities.

Oracle Resources are technicians with skill profiles, territories, certifications, and capacity calendars. Dynamics 365 Sales has no native Resource object — technicians are System Users who may be assigned Cases but carry no skill or certification data. FlitStack creates a custom Resource__c entity in the Dynamics solution to hold skill labels, service territories, certification dates, and capacity type. The Resource's email maps to a Dynamics User for owner assignment on migrated Cases.

Oracle Locations represent service addresses with street, city, state, postal code, country, and geo-coordinates. Dynamics Accounts hold address fields (address1_line1, address1_city, address1_stateorprovince, address1_postalcode, address1_country). FlitStack maps Location.street to Account.address1_line1, Location.city to address1_city, and so on. Locations without a parent Organization link to a default Account or require Account pre-creation.

Oracle Assets represent installed equipment at a customer location with name, model, serial number, installation date, warranty expiration, and customer link. Dynamics 365 Sales includes a native Asset table (msdyn_asset) with the same purpose. FlitStack maps Asset.name to msdyn_asset.name, Asset.serialNumber to msdyn_asset.msdyn_serialnumber, Asset.installDate to msdyn_asset.msdyn_installeddate, and the customer link to msdyn_asset.msdyn_customer (Account lookup). Custom Asset properties migrate as custom fields on msdyn_asset.

Oracle Organizations represent the business entities (customers) that receive service. These map directly to Dynamics Accounts — the primary company record in a sales CRM. Organization.name maps to Account.name, Organization.address to Account address fields, and Organization.phone to Account.telephone1. Additional Oracle fields such as industry classification, annual revenue, and number of employees transfer to corresponding Dynamics fields when present in the source schema. The original Oracle Organization identifier is stored in a custom field on the Account for traceability back to the source system.

Oracle Activity notes and file attachments migrate to Dynamics Case annotations (notes) and SharePoint-attached files. FlitStack preserves original timestamps on notes, re-uploads attachments to the linked Case's SharePoint document location, and maintains the original file name. Large attachments (>25MB per Dynamics limit) are flagged for chunked upload.

Oracle Buckets are organizational containers for grouping Activities (work orders) by type, region, or business unit. Dynamics Cases have no native bucket concept. FlitStack creates a custom pick-list field (Bucket__c) on the Case entity and maps Oracle Bucket names to values in that field so the organizational grouping survives the migration.

Oracle Inventory Items (parts, materials consumed on work orders) map to Dynamics Products. The item name, SKU, and unit of measure transfer as Product.name, Product.productnumber, and a custom unit field. Dynamics Products are price-list items, not inventory tracking — parts-consumed records on Oracle Activities migrate as Case notes or a custom Parts_Used__c sub-entity rather than inventory transactions.

Oracle Field Service Cloud supports custom objects created via Oracle CX configuration (following the O_INT_* naming pattern visible in Oracle's API). These custom objects, including any custom fields and relationships defined on them, map to custom tables in the Dynamics Dataverse environment. FlitStack reads the custom object's field schema from the Oracle metadata API and creates corresponding custom columns in Dynamics before data transfer.

Oracle Routes are optimized dispatch sequences generated by Oracle's routing engine — they are execution artifacts, not durable data records. Dynamics 365 Sales has no routing or scheduling capability. Routes are not migrated. If your team relies on historical route data for analytics, FlitStack can export Route-to-Activity linkage as a reference CSV for Power BI analysis outside Dynamics.