Migrate from Oracle Field Service Cloud to Pipedrive

Each OFSC Activity maps to a single Pipedrive Deal. The OFSC activity_type, status, scheduled_date, actual_start, actual_end, and resource_id become Pipedrive Deal fields or custom deal fields. Task-level details (subtasks, completion steps) are captured in the Pipedrive Deal's activity-linked notes and activity records.

OFSC activity_type pick-list values (Installation, Repair, Maintenance, Inspection, Delivery) have no native Pipedrive equivalent. We create a Pipedrive deal custom field of type picklist, populate it from the OFSC activity_type value at migration time, and map each value one-to-one into the Pipedrive custom field picklist options.

OFSC activity status values (pending, in_progress, completed, not_done, cancelled) map to Pipedrive deal stage names. The mapping is value-by-value: OFSC completed maps to a closed-won Pipedrive stage, OFSC cancelled maps to a closed-lost Pipedrive stage, and in-flight statuses map to active pipeline stages by your specification.

OFSC Resource records represent field technicians and dispatchers. We match each OFSC resource to a Pipedrive User by email address. Skills, availability_zone, and capacity_method from OFSC are preserved as custom user fields in Pipedrive since there is no native Pipedrive equivalent for technician skills or zone assignments.

OFSC Location records contain site-level data (address, routing_zone, primary_contact) and must be split: the location name, address, city, state, zip, country, latitude, and longitude become a Pipedrive Organization. The primary_contact_id from OFSC becomes a linked Pipedrive Person associated with that Organization. Multiple OFSC locations for the same customer company become multiple Pipedrive Organizations or are merged by your specification rule.

OFSC routing_zone values represent geographic territories assigned to each service location and have no native Pipedrive Organization field. We create a Pipedrive custom field on the Organization object of type varchar and populate it directly from the OFSC location's routing_zone value. This custom field enables territory-based reporting and segmentation within Pipedrive Insights, supporting performance analysis by geographic area post-migration.

OFSC Route records represent daily technician routes with date, start_time, estimated_duration, and assigned_resource. Pipedrive has no native scheduling or route entity. We flatten route attributes as custom fields on the Pipedrive Deal linked to that route's activity, so service-window data is visible on the deal record without requiring a scheduling integration.

OFSC sub-tasks within an Activity (task_name, task_type, task_status, actual_start_time, actual_end_time) map to Pipedrive Activity records linked to the corresponding Deal. The Pipedrive Activity's subject carries the OFSC task name, the type field carries the OFSC task_type, and the completed flag carries the OFSC task_status.

OFSC Inventory items represent parts and materials used during service visits. We map inventory items to Pipedrive Products — name, SKU, unit_cost, quantity_on_hand, and usage_location_id become Pipedrive Product fields. The OFSC usage_quantity from a specific activity is preserved as a custom product field or as an activity note linking the product to the deal.

OFSC Capacity Quota records define technician availability by time interval and capacity area. Pipedrive has no native capacity-management entity. We document the OFSC quota structure (area, date, min_quota, max_available) as a reference export and flag it for rebuild as Pipedrive automations or a third-party scheduling tool integration.

OFSC booking_closing_schedule controls when routes are finalized and no further bookings are accepted. Pipedrive has no native equivalent. We preserve the schedule as a custom note in the migration audit log for your admin to rebuild as a Pipedrive automation or calendar-based reminder.

OFSC collaboration_chats and address_book records provide technician-to-technician messaging and team coordination capabilities within the dispatch platform. Pipedrive is a sales-focused CRM and does not include a native team chat, internal messaging, or shared address-book feature. These records have no equivalent in Pipedrive's object model and are not migrated. Teams should implement a dedicated communication platform such as Slack or Microsoft Teams before go-live to maintain team coordination and messaging capabilities post-migration.