Migrate from JiBe to Dolibarr ERP

JiBe vessel master records map to Dolibarr third parties with a custom IMO number field (fk_vehicles_imo) added to the llx_societe_extrafields table. Vessel name becomes the third-party name, flag state maps to a custom country selection, and vessel type (cargo, tanker, container) maps to a custom categorization field. The fleet parent relationship in JiBe maps to Dolibarr category membership using llx_categorie records. Each vessel is created as a customer third party type with the maritime operator as the parent account if a fleet hierarchy is maintained.

JiBe fleet groupings (fleet-to-vessel parent relationships) map to Dolibarr categories under the CATEGORY_SHIP type we create during migration. The category tree in Dolibarr replicates the fleet hierarchy, and we attach vessel third parties to their respective fleet categories using llx_categorie_societe. If JiBe has multiple fleet levels (fleet, sub-fleet, vessel), we create nested categories with the parent_id chain matching the JiBe hierarchy depth.

JiBe PMS location hierarchies (machinery components per vessel) do not have a native Dolibarr equivalent. We create one Dolibarr Project per vessel to serve as the maintenance work order container, then represent the PMS location hierarchy as nested Dolibarr categories under a SHIP_SYSTEM category type. Each PMS location level (engine room, propulsion system, thruster unit) becomes a category with the full path preserved in the category label. Maintenance jobs reference the vessel project and are tagged with the relevant system category.

JiBe maintenance jobs map to Dolibarr project tasks (actioncomm records). Job status (open, in progress, completed) maps to the task status field, priority maps to priority, and the work order description maps to task notes. Completed historical jobs migrate as read-only tasks with the completion date preserved. Open jobs transfer with current status flags. The PMS location reference is preserved as a category tag on the task using llx_actioncomm_categories.

JiBe spare parts inventory maps to Dolibarr product records. Part number from JiBe becomes product reference (ref), part description becomes product label, and current stock level imports into Dolibarr stock (llx_product_stock). Reorder points map to warehouse minimum stock settings. Some JiBe deployments use custom part number formats with embedded vessel or system codes; we normalize these during transformation and optionally preserve the original JiBe part number in a custom field. Supplier links become product supplier price rows in llx_product_fournisseur.

JiBe purchase orders and requisitions map to Dolibarr supplier orders. PO number becomes the order reference, vendor maps to the supplier third party, and line items reference the mapped spare part products. Open POs migrate with status preserved (draft, validated, approved). PO date and expected delivery date map to date_creation and date_livraison. Historical closed POs migrate as read-only records. The vendor-to-part linkage from JiBe is resolved against the product supplier price rows created during spare parts migration.

JiBe chartering agreements map to Dolibarr contracts with significant schema adaptation. Contract type is set to 'Charter' using a custom contract type we configure during migration. Counterparty details map to a supplier or customer third party depending on charter type (time charter vs voyage charter). Contract terms, rate structures, and port itineraries are stored in custom contract extrafields since Dolibarr's standard contract fields are oriented toward service subscriptions. The linked vessel third party is referenced via a custom field on the contract.

JiBe crew records map to Dolibarr user accounts with the Employee module enabled. Rank and certification fields map to custom extrafields on llx_user_extrafields. Certification expiry dates are stored as extrafields with a validation flag we set up during schema configuration. The crew-to-vessel assignment is preserved as a user property: the employee's default assigned vessel becomes a custom user extrafield linking to the vessel third party. Payroll associations are noted as a custom field for the customer's HR team to configure in their payroll integration.

JiBe insurance policies per vessel map to Dolibarr contracts with type set to 'Insurance' and the insurance carrier as the supplier third party. Policy number, coverage type (hull, P&I, cargo), start date, and expiry date are stored in custom contract extrafields. If JiBe links insurance claims to incidents or maintenance records, we preserve those references as contract line items or custom field linkages for the admin to finalize in Dolibarr.

JiBe incident and defect reports map to Dolibarr interventions (intervention records) linked to the vessel project. The incident description becomes the intervention subject, incident date becomes the intervention date, and any associated costs are stored in a custom extrafield. If the incident triggered a maintenance job, we create a linked intervention with a reference back to the mapped maintenance job task, preserving the incident-to-job chain. Open incidents migrate with status flags; closed incidents migrate as read-only records with resolution notes.

JiBe commercial records (voyage financial records, freight revenue, port charges) map to a combination of Dolibarr invoices and expense records depending on the record type. Freight revenue becomes customer invoices (facture client) linked to the chartering contract; port charges and bunker costs become supplier invoices (facture fournisseur) linked to the relevant vessel. Currency handling uses Dolibarr's multi-currency support if JiBe records include non-base currency transactions.

JiBe BI reports and dashboards are configuration artifacts tied to the platform's internal data model and cannot be exported and replayed in Dolibarr. We extract the underlying data tables that feed each report (maintenance performance metrics, parts consumption history, vessel benchmark scores) and deliver them as structured CSV exports alongside the migration. The customer's admin uses these exports to rebuild equivalent reports in Dolibarr's reporting module or in an external BI tool such as Microsoft Power BI or Metabase.

JiBe workflow rules and automation configurations are not migratable data. We audit every active workflow during discovery and deliver a written inventory documenting each rule's trigger, conditions, actions, and applicable vessels or PMS locations. This inventory serves as the reference for the customer's admin to rebuild equivalent automation in Dolibarr's module configuration or via the Dolibarr workflow module if it is enabled in the destination installation.

JiBe deployments frequently include custom fields on vessel records, PMS locations, and maintenance jobs to capture fleet-specific data (flag state exemptions, class survey dates, flag administration contacts). We map each custom field to a Dolibarr extrafield on the corresponding table (llx_societe_extrafields for vessels, llx_projet_extrafields for projects, llx_actioncomm_extrafields for tasks). Field types are matched during schema design: text to varchar, dates to datetime, numeric values to decimal, and multi-select values to enum.