Migrate your Oracle Field Service Cloud data

Activities are the core operational record in OFSC. Each activity carries Customer, Asset, Resource, time window, status, and custom properties. We map activities 1:1 including status transitions and preserve activity-level service histories when the destination schema supports them.

Resources represent field workers, vehicles, or crews. OFSC tracks capacity, skills, certifications, and working hours per resource. We migrate Resources with their skill tags and availability rules intact, mapping Owner/User assignments to the destination's corresponding user object.

Skills are tag-based competencies assigned to Resources and required by Activities. Certifications carry expiry dates. We preserve skill-to-resource mappings and flag any expired certifications that may affect routing eligibility post-migration.

Buckets are scheduling pools that group activities by type (Installation, Repair, etc.). Bucket definitions and their associated business rules vary by implementation. We map bucket names and rules but recommend a manual review of bucket-to-activity assignments after migration to confirm scheduling logic holds.

Territories define geographic dispatch zones and assign Resources to coverage areas. Territory boundaries in OFSC use complex polygon and postal-code definitions. We extract territory structures and map them to the destination's location hierarchy, noting that geofencing triggers may need reconfiguration.

Work Orders originate in Oracle Fusion Service and synchronize to OFSC Activities via Oracle Integration. Where Fusion Work Orders exist independently, we handle them as separate records and map them to Activities with a reference link preserved. Custom Work Order fields require explicit value mapping.

Customers in OFSC are service-location entities linked to Activities and Assets. We migrate customer records with address, contact details, and service preferences. Customer hierarchies (parent/child accounts) are mapped to the destination's company or account object structure.

Assets represent equipment installed at customer locations. OFSC assets carry maintenance history, installed parts, and linked service contracts. Asset-to-customer linkage is preserved during migration, but detailed service histories may require chunked export due to volume.

Parts inventory tracks items available on vehicles or at depots. OFSC inventory levels are transactionally linked to Activity completion records. We map inventory quantities and par levels, noting that real-time inventory sync to Fusion requires Oracle Integration to be active post-migration.

Forms capture structured data during Activity execution (inspections, safety checklists, signatures). Form definitions and captured responses are custom per implementation. We migrate form data as structured key-value pairs, mapping to the destination's equivalent custom fields or notes objects.

Workflows guide technicians through structured steps during an Activity. Step completion status and audit trails are stored per activity. We map step sequences and completion timestamps, noting that step-level branching logic may not translate directly to non-OFSC platforms.

Activity-level service histories aggregate all interactions with a specific Customer or Asset over time. These are derived records in OFSC. We generate service history summaries during migration rather than migrating the aggregate itself, preserving the narrative record at the destination.