Migrate from Oracle Manufacturing Cloud to Dolibarr ERP

Oracle Manufacturing Cloud Work Orders map to Dolibarr Manufacturing Workstation orders. We export work order header fields (work order number, status, type, priority), scheduled start and end dates, and quantities. Oracle work order operations (routing steps) map to Dolibarr operation lines within each work order. Note: Dolibarr manufacturing does not support planned costs, actual costs, or variance tracking per operation the way Oracle does; cost data is documented separately for manual entry in Dolibarr.

Oracle Work Definitions define the routing steps for manufacturing an item. We map each operation sequence to a Dolibarr BOM with its associated production line. Oracle work center assignments per operation step map to Dolibarr workstation groups, though Dolibarr does not support step-level resource capacity or alternate work center assignments. Any step-level scrap percentages or queue time values are recorded as notes on the Dolibarr production line.

Oracle Items (the master product record) map to Dolibarr Products. The Oracle item number becomes the Dolibarr ref; the item description and UOM migrate to the product label and unit fields. Oracle's make-or-buy flag maps to Dolibarr product type (product or service). We validate that Dolibarr's product type setting matches the Oracle item status to prevent BOM line resolution failures at import time.

Oracle multi-level BOMs map to Dolibarr BOM structures. We export the full BOM hierarchy including sub-assemblies and map each level to a corresponding Dolibarr BOM with its own production line. Oracle co-products and by-products (defined in mixed-mode production) are flagged as a capability gap because Dolibarr manufacturing does not support co-product or by-product outputs on a single BOM; we document the co-product quantities and assignments in a separate remediation report for the customer's admin.

Oracle Manufacturing Plants define an organizational production unit with calendar associations and plant-level parameters. Dolibarr does not have a plant hierarchy. We split Oracle plant-level data across Dolibarr entities (for multi-company scenarios) and warehouses (for inventory location scoping). Plant-level parameters such as default UOMs, work area definitions, and profile options are mapped to Dolibarr warehouse settings where supported and flagged as unsupported where they are not.

Oracle Work Centers represent production resources (machines, labor pools, departments). We map work center definitions to Dolibarr workstations and group capacity rules into Dolibarr workstation groups. Oracle's work center-level UOM overrides and availability rules are not natively supported in Dolibarr and are documented as configuration steps for the customer's admin to enter manually post-migration.

Oracle Manufacturing Calendars define plant working times, shift patterns, and calendar exceptions. Dolibarr's manufacturing module links holiday dates to workstations rather than maintaining a standalone calendar object. We map Oracle calendar shift definitions to Dolibarr timespan entries on each workstation. Oracle calendar-to-shift assignments are preserved in a supplemental mapping document for manual configuration in Dolibarr.

Oracle Departments represent organizational cost and responsibility centers associated with work centers. We map department definitions to Dolibarr user categories or project cost centers depending on the customer's chosen Dolibarr usage model. Departments must exist in Dolibarr before any work order with a department cost assignment is imported to avoid orphaned cost allocations.

Oracle Cost Scenarios define material, resource, and overhead cost rollups per cost element. We map the cost scenario effective date and element costs to Dolibarr's standard cost field on each Product record. A critical flag: Oracle requires the work definition start date to equal or follow the cost scenario effective date for correct cost rollup; we check every date pair and raise a correction requirement before any cost data loads into Dolibarr.

Oracle Smart Operations Configurations include UOM defaults at plant level, work center UOM overrides, reason codes, operator assignment rules, and target metrics (plan adherence, OEE). Dolibarr manufacturing does not support OEE tracking, plan adherence metrics, or operator assignment rules. We extract and document these configurations in a written remediation report for the customer's admin to evaluate against Dolibarr's third-party module ecosystem or manual tracking alternatives.

Oracle Production Sequences govern the order of operation execution in mixed-mode environments. Dolibarr's work order sequencing is simpler and does not support sequence definitions separate from the work order itself. We map sequence step definitions to Dolibarr operation lines within each work order, and flag any mixed-mode sequence step ordering that requires manual sequencing in Dolibarr's production order list.

Oracle Reason Codes explain production variances and exceptions at workstations. Dolibarr does not have a native reason code object for manufacturing. We map reason code sets to Dolibarr extrafields on the work order object. The reason code definitions and their usage contexts are documented in the supplemental configuration report delivered alongside the migration.

Oracle Application Composer custom objects are environment-specific and do not have a direct Dolibarr equivalent. We export the custom object data and schema, then map custom field definitions to Dolibarr extrafields on the closest standard object (Product, Work Order, or Third Party). Custom objects with complex interdependencies require schema design during discovery and are among the highest-risk migration items for this pair.

Oracle attachments associated with work orders, items, and work definitions are exported from Oracle's document management system. We map file attachments to Dolibarr's document management linked to the corresponding Product or Work Order record. File type and size limits in Dolibarr's document management require validation before import; files exceeding Dolibarr's attachment size threshold are flagged for the customer to store externally.