Migrate from Oracle Field Service Cloud to monday CRM

Oracle FSC Activity maps directly to a Monday CRM Item on a dedicated Service Board. The activity identifier (activity_id) is stored as a custom text column (Source_Activity_ID__c) for traceability and delta-run de-duplication. Activity status (scheduled, in progress, completed, cancelled) maps to Monday's Status Column values, and the original activity type label (Installation, Repair, Maintenance, Inspection) maps to a Label Group or secondary Status Column.

Oracle FSC Activity Type is a configured pick-list set by the administrator on the Activity Type configuration screen. Each value (Installation, Repair, Maintenance, Inspection, Survey) maps to a Monday CRM Label within a Label Group called 'Activity Type'. If your Oracle FSC instance has more than 30 activity type values, we create a second Label Group to avoid Monday's per-column label limit.

Oracle FSC Resources — technicians and vehicles — map to Items on a Technicians Board in Monday CRM. The resource's name, email address, and work zone assignment become Item name, Email Column, and Location Column respectively. Skills and certifications stored on the Resource record map to Tag Groups on the Item, enabling filtering by technician specialty in Monday.

Oracle FSC Locations (service sites with address, coordinates, and customer link) map to Items on a Locations Board in Monday CRM. The street address, city, state, and postal code become Address Column fields in Monday. GPS coordinates are stored as a custom Number Column pair (Latitude, Longitude) for map-view display. The customer account reference maps to a Connect Column linking back to the Customer Board.

Oracle FSC Customer records — the billing or contracting entity — map to Monday CRM Items on a Customers Board. Company name becomes the Item name, the primary contact's email becomes an Email Column, and the customer classification or industry maps to a Label Column. Multi-site customers with multiple Oracle FSC Location records will have one Customer Item linked to multiple Location Items via Connect Columns.

Oracle FSC Parts (inventory items with part number, description, cost, and stock quantity) map to Monday CRM Items on a Parts Board. The part number becomes the Item name, cost becomes a Number Column, and serialized/non-serialized flag becomes a Label. If Oracle FSC tracks bin locations, that data maps to a Text Column in Monday. Note that Monday does not enforce inventory minimums or reorder triggers — those rules require a manual rebuild in Monday Automations.

Oracle FSC Capacity buckets and quota groups (the PATCH /quota endpoint structure with ratio values per time interval) have no native Monday CRM equivalent. We migrate capacity data as a separate Capacity Board where each Resource Item has a Number Column for each quota window. The capacity calculation logic — how Oracle FSC computes available slots — does not transfer and must be rebuilt as Monday Automations or an external scheduling tool.

Oracle FSC Skills attached to Resources are extracted as a separate Skills Board. Each skill (HVAC Certified, Licensed Electrician, Safety Trained) becomes a Skill Item. On the Technicians Board, Resource skills are stored as Tags linked to the Skill Items, enabling Monday's Tag aggregation view. If Oracle FSC uses skill level ratings (Level 1, Level 2, Master), those values map to a Number Column on the Skill Item.

Oracle FSC Debrief labor entries — billing type (Commute, Diagnose, Repair), billing item, start time, end time, and fractional hours — map to Monday CRM Subitems on the corresponding Activity Item. The billing type becomes the Subitem name, start/end times become Time Tracking Columns, and hours calculate automatically via a Formula Column. Debrief expenses (parking, tolls, parts used) become separate Subitems with a Number Column for Amount and a Text Column for expense type.

Oracle FSC Route configurations (routing plan setup, prioritize earlier start of most important activities, bulk routing parameters) are exportable via the Daily Extract from the Applications page, but the routing logic itself — the optimization algorithm that assigns activities to route slots — does not translate to Monday's board model. We migrate the route name, assigned resources, and activity count as Items on a Route Board for reference. The actual scheduling decisions must be rebuilt manually in Monday.

Oracle FSC file attachments on activities (photos, signatures, work completion images) are re-uploaded to Monday CRM's built-in file storage attached to the corresponding Item. Oracle FSC's 25MB per-file limit applies; Monday's per-plan storage limits (5GB on Basic, 20GB on Standard, 100GB on Pro) govern the total upload budget. We re-host inline images from debrief notes as separate file attachments on the Subitem.

Oracle FSC allows custom field definitions via the Field Mapping custom object (O_INT_FieldMapping) with FusionFieldName, FusionFieldValue, RemoteFieldID, and RemoteSystemID parameters. Any Oracle FSC custom field not covered by our standard mapping is flagged as requiring a Monday custom column (Text, Number, Date, Dropdown, or Formula). We include the custom field schema from O_INT_FieldMapping in the pre-migration audit so Monday column types are defined before ingestion.