Migrate from JiBe to Odoo ERP

JiBe Vessels are the primary entity, carrying IMO number, flag state, vessel type, gross tonnage, and fleet parent hierarchy. We map these to Odoo Maintenance Asset records (using the asset model's name, serial_number for IMO, and category for vessel type) or to a custom res_vessel model if the Odoo implementation includes a maritime-specific app. The fleet parent-child grouping migrates as an Asset parent_id hierarchy in Odoo. Active/inetactive status flags transfer directly.

JiBe's fleet grouping above vessels (operator groups, trust structures, ship-management companies) maps to Odoo res.partner records in company mode. The fleet-to-vessel parent-child relationship is preserved by linking each vessel Asset to its fleet partner via a custom field or via a dedicated fleet Asset parent in the asset tree. Commercial operator details (company name, registration, contact) map to standard partner fields.

JiBe PMS locations define the machinery hierarchy on each vessel—engine room, main engine, auxiliary systems—and vary by vessel configuration, meaning the same machinery type may appear at different tree depths across ships. We profile each vessel's PMS structure during discovery, then map to Odoo maintenance.equipment records with parent_equipment_id capturing the hierarchical relationship. Naming conventions are preserved in equipment.name; the JiBe location code maps to a custom field for traceability. Equipment categories map to maintenance.equipment.categ_id.

JiBe maintenance jobs carry status (open, in progress, completed), priority, work order reference, and a link to the PMS location. We map these to Odoo maintenance.request records. The PMS location link resolves to the migrated maintenance.equipment record via parent lookup. Historical completed jobs migrate as read-only requests with a completed state. Open jobs transfer with their current status flags and scheduled date preserved. Job cost data migrates to maintenance.request.employee_id and custom cost fields.

JiBe spare parts inventory links part numbers, stock levels, reorder points, and supplier links to PMS locations and maintenance jobs. We map to Odoo product.product records (for named parts) with stock.quant records for on-hand quantity at each vessel or warehouse location. Supplier links migrate to product.supplierinfo records. Custom part number formats from JiBe are preserved in product.default_code. Stock levels at each vessel map to stock.quant with lot_id for batch tracking if JiBe uses lot-based parts.

JiBe procurement records contain purchase orders and requisitions linking vendors to vessel-level procurement needs. Open POs by status migrate to Odoo purchase.order records. Vendor links resolve via email matching against Odoo res.partner in supplier mode. PO lines map to purchase.order.line with product, quantity, and unit price resolved. Closed and historical POs migrate as read-only records; the JiBe approval workflow status is preserved in a custom field on the PO.

JiBe crew records include personal details, rank, certifications, and payroll associations. We map to Odoo hr.employee records with the crew-to-vessel assignment recorded via hr.employee.vessel_id (custom field) or via the fleet Asset. Certification expiry dates migrate to hr.employee.certificate_ids with expiry dates for compliance continuity. Rank and position data map to hr.job and a custom rank field. Payroll associations link to hr.payroll if the Odoo deployment includes the HR payroll module.

JiBe insurance records per vessel carry coverage types, policy numbers, carrier details, and effective dates. Odoo has no standard insurance object, so we map to a custom insurance.policy model (or a dedicated Odoo app such as agreement or contract management) with policy_number, carrier_partner_id, coverage_type, effective_date, and expiry_date fields. Claims linked to incidents migrate as policy.claim records. The customer selects the target model during scoping based on Odoo module inventory.

JiBe incident reports are linked to specific PMS locations and can trigger maintenance jobs. We map corrective incidents to Odoo maintenance.request records with request_type=corrective, preserving the incident description, reported date, and cost. Incidents linked to safety or environmental regulatory records map to project.task under a safety project. The incident-to-job linkage is preserved as a custom related_request_id field on the maintenance.request record.

JiBe chartering records contain contract terms, counterparty details, commercial voyage data, rate structures, and port itineraries. Odoo does not have a standard chartering object. We map time-charter agreements to sale.subscription records with custom fields for charter_type, counterparty, daily_hire_rate, and delivery/redelivery dates. Voyage-charter records with port itineraries map to project.project with task-based port-of-call legs. The customer selects the mapping during scoping based on Odoo module inventory.