Migrate from Ostendo to Dolibarr ERP

Ostendo CUSTOMER MASTER records map directly to Dolibarr ThirdParty with type=Customer. We extract all displayed fields including customer code, name, contact details, billing and delivery addresses, payment terms, and VAT number. The Ostendo customer code becomes the ref (reference) field in Dolibarr and serves as the dedupe key during import. If the customer has both billing and delivery addresses in Ostendo, the delivery address imports as a separate address record linked via the address_id foreign key.

Ostendo ITEMMASTER records map to Dolibarr Product. Standard fields — item code (becomes ref), description (becomes label), unit cost (becomes cost price), and stock levels — migrate directly. The Primary Supplier linkage from ITEMMASTER becomes a Supplier Prepricing record in Dolibarr's ProductSupplierPricing table. Multi-unit-of-measure support in Ostendo (each item can have multiple stocking UOMs) maps to Dolibarr's unit-of-measure fields. Barcode and serial number flag fields transfer to Dolibarr's barcode and lot/serial tracking configuration.

Ostendo supplier records held in the supplier master table map to Dolibarr ThirdParty with type=Supplier. Supplier code, name, contact details, payment terms, and bank information migrate. If the customer has a unified contact record in Ostendo that serves both customer and supplier roles, we split into two ThirdParty records in Dolibarr (one with type=Customer, one with type=Supplier) and link them by the original Ostendo contact identifier.

Ostendo Purchase Orders map to Dolibarr CommandeFournisseur (Supplier Order). Header fields — PO number, supplier reference, order date, expected delivery, status — migrate to the order header. Line items migrate with product reference resolved to the Dolibarr Product ID, ordered quantity, unit price, and line-level discounts. Header status (Draft, Sent, Received, Closed) maps to Dolibarr lined status constants.

Ostendo Sales Orders map to Dolibarr Commande (Customer Order). We extract the full order hierarchy including Order Style (which determines order type), line items, pricing, and status. The Ostendo customer reference maps to the Dolibarr soc_id (ThirdParty link). Line items resolve product references to Dolibarr Product IDs. If Ostendo POS generated orders, these carry the same schema and migrate as standard Customer Orders with a POS flag stored in an extra field.

Ostendo Work Orders are the most complex migration object. Multi-level Bills of Materials (BOMs) require flattening: each sub-assembly in the BOM tree becomes a separate manufacturing order line linked to the parent Work Order. We extract routing, workstation assignments, and operation sequencing from the Work Order scripts and map them to Dolibarr's Manufacturing module (if activated) with Project-level task breakdown. Status, priority, and estimated completion date transfer to the Project record. Multi-level BOM resolution is the primary driver of extended migration timelines for manufacturing-heavy customers.

Ostendo Timesheets linked to Work Orders and Jobs map to Dolibarr ProjectTime records under the corresponding Project (sourced from the Ostendo Work Order). Freeway Mobile time entries — including GPS coordinates, materials issued, and technician ID — migrate as ProjectTime lines with notes capturing the GPS and materials data. If Ostendo records are stored with a date-only format rather than datetime, we normalise to 08:00 as a default start time and compute duration from the recorded hours. Technicians without matching Dolibarr User records enter a reconciliation queue for admin provisioning.

Ostendo stock levels and multi-site inventory migrate to Dolibarr Stock. Serial number tracking per location normalises into Dolibarr's lot/serial number fields. Multi-site records from separate Stock Locations in Ostendo become separate warehouse entries in Dolibarr's entrepot table. We compute stock value using the unit cost from ITEMMASTER at the time of migration and write it into Dolibarr's PMP (weighted average price) field. Stock status flags (blocked, quarantine) transfer to Dolibarr's stock status field.

Ostendo Stock Locations (physical or logical inventory positions) and Service Zones (geographical groupings for field service) both map to Dolibarr Entrepot records. Service Zones carry an address and geographic boundary; these become the Entrepot address fields. If Service Zones contain Assets, we link the migrated Asset records to the corresponding Entrepot via the fk_warehouse foreign key after both objects are loaded.

Ostendo Asset records linked to Service Zones map to Dolibarr Asset. We extract asset master data including asset code, description, meter readings, equipment check history, and current status. Preventive maintenance schedules from Ostendo become Dolibarr Maintenance module entries (if activated) or are documented as a manual rebuild item. Asset location resolves to the corresponding Entrepot record via the Service Zone mapping.

Ostendo users are licensed by concurrent sessions, not named users. During discovery we capture the total user record count in Ostendo's User Security table and calculate the named-user equivalent (typically 2.5-4x the concurrent licence count). Each Ostendo user record — login name, display name, email, role, and module access — maps to a Dolibarr User record. Active status in Ostendo maps to Dolibarr's active flag; inactive Ostendo users become inactive Dolibarr Users. If Ostendo Freeway Mobile users exist without a desktop login, we create Dolibarr Users with a flag in the notes field identifying the mobile-only origin.

Ostendo's Freeway Mobile platform stores user-defined templates per object including checklists, compliance forms, and QA inspection fields. These have no standard export format and no direct Dolibarr equivalent out of the box. We flag every custom template definition during discovery and create explicit Dolibarr ExtraField definitions for each one using Dolibarr's Extrafields module. Fields that cannot be represented as standard Dolibarr field types (e.g., GPS coordinates stored as free text) are stored in a dedicated extra field and documented for the customer's admin to review. This manual mapping step is the primary source of timeline variance for field-service-heavy Ostendo deployments.

Ostendo's SQL-based Report Writer generates saved reports, inquiries, and pivot tables that reference Ostendo-specific table structures and field names. These reports have no direct Dolibarr equivalent because Dolibarr's report module uses a different table naming convention and its reporting builder does not expose raw SQL query editing to end users. We deliver a written inventory of every Ostendo Report Writer query — including the SQL logic, output fields, filters, and sort order — for the customer's admin to rebuild using Dolibarr's report builder or a third-party reporting tool. This inventory is delivered as a structured spreadsheet during the migration handoff.