Migrate from JiBe to Infor CloudSuite Corporate

JiBe vessel master records (name, IMO number, flag state, vessel type) map to either Infor Item records configured as assets or a custom Vessel master object built in the Infor Data Migration Utility. The vessel-to-fleet parent relationship maps to an Infor organizational hierarchy or company structure. We preserve the IMO number as a unique identifier for deduplication. Vessel type codes require a lookup table because JiBe maritime vessel type taxonomies differ from Infor's general equipment classification.

JiBe Preventive Maintenance System locations define machinery and component hierarchies per vessel. These map to Infor Equipment records or a Location hierarchy depending on the CloudSuite edition deployed. JiBe allows custom PMS location hierarchies per vessel, meaning the same machinery type (main engine, propeller, ballast system) may be modeled at different hierarchy depths across ships. We profile each vessel's PMS structure during discovery and apply vessel-specific mapping rules so that maintenance locations resolve to the correct Infor parent node rather than creating orphaned job records.

JiBe maintenance jobs with status, priority, and work order data map to Infor Work Order records. Historical completed jobs migrate as closed Work Orders. Open jobs transfer with current status flags resolved to Infor Work Order status codes. Job-to-PMS location linkage is preserved as a Work Order-to-Equipment reference. JiBe job priority codes (urgent, high, medium, low) map to Infor priority values via a configuration table.

Parts inventory linked to PMS locations and maintenance jobs map to Infor Item records with inventory tracking enabled. We migrate part numbers, stock levels, reorder points, and supplier links. Some JiBe deployments use custom part number formats that require normalization during ingestion. The JiBe part-to-supplier relationship maps to Infor's Item Supplier cross-reference.

JiBe purchase orders and requisitions connect vendors to vessel-level procurement needs. Open POs migrate by status, preserving the vendor-to-part linkage. Infor PO header and line structure must be configured before migration so that line items reference the correct Infor Item records. Closed POs migrate as historical records with a closed status.

JiBe chartering records contain contract terms, counterparty details, and commercial voyage data. The schema varies by deployment and may include custom fields for rate structures and port itineraries. We map chartering agreements to Infor Contract records or Sales Order headers depending on whether the deployment uses Infor's contract management module. Custom rate structure fields map to extended data fields or custom Infor objects.

JiBe crew records include personal details, rank, certifications, and payroll associations. We map crew to Infor Employee records with rank mapped to a Job Title or Department field, and certification expiry dates preserved as date fields for compliance continuity. Crew-to-vessel assignments map to an Infor organizational or cost center relationship. Payroll associations require Infor HRMS or payroll module context; if not present, the payroll fields migrate as reference data for manual assignment.

JiBe insurance records per vessel carry coverage types, policy numbers, carrier details, and expiry dates. We map these to Infor Contract records or a custom Insurance object if the deployment includes Infor's Insurancevertical. Coverage type and carrier map to Infor Contract type and party fields. Some deployments link insurance claims to incidents or maintenance records; we preserve the incident-to-claim linkage as a cross-reference during migration.

JiBe incident reports are linked to specific PMS locations and can trigger maintenance jobs. We preserve the incident-to-job linkage by creating Infor Work Orders with an incident reference field. Associated costs recorded against the incident in JiBe migrate as cost entries on the corresponding Work Order in Infor. Defect records with root cause data map to Infor Quality Nonconformance records if the destination includes Infor's quality management module.

JiBe commercial records capture voyage revenue, freight charges, and bunker consumption data specific to maritime operations. We map these to Infor Sales Order or Revenue Recognition records depending on the Infor CloudSuite edition deployed. Revenue categorization requires a custom mapping table because maritime commercial terminology (lump-sum charter, time charter, voyage charter) differs from Infor's standard sales order revenue types.

JiBe BI reports and dashboards are configuration artifacts built from underlying data rather than data records themselves. These cannot be exported and replayed in Infor CloudSuite. We extract the underlying data—maintenance records, performance metrics, parts consumption, crew utilization—and deliver it in structured CSV and JSON form so that Infor administrators can rebuild equivalent reports in Birst or the native Infor OS analytics layer.