Migrate from JiBe to Microsoft Dynamics 365 Business Central

JiBe vessel master records (name, IMO number, flag state, vessel type, fleet assignment) map to Dynamics 365 Asset Management assets. We create one Asset per vessel with the vessel name as Asset name, IMO number in a custom field, flag state in a picklist, and vessel type in a classification field. The vessel-to-fleet parent relationship in JiBe maps to the Asset's functional location hierarchy in Dynamics 365 Finance and Operations Asset Management or the location structure in Business Central.

JiBe Preventive Maintenance System locations define the machinery and component hierarchy on each vessel. Dynamics 365 Asset Management uses functional locations with configurable hierarchies to represent equipment structures. We profile each vessel's PMS structure during discovery and create vessel-specific functional location trees in the destination. The naming conventions and depth vary across ships in the same fleet, so we apply per-vessel mapping rules rather than a global schema. This is the highest-risk mapping step because orphaned functional locations cause maintenance jobs to lose their equipment context.

JiBe maintenance jobs (status, priority, work order data, PMS location reference, and completion history) map to Dynamics 365 work orders in Asset Management. Historical completed jobs migrate as read-only records with original completion dates and costs preserved. Open jobs transfer with current status flags into new work orders in a draft state for the operations team to activate. Job priority maps to work order priority, and the PMS location link resolves to the functional location created during the asset setup phase.

JiBe parts inventory (part numbers, stock levels, reorder points, supplier links) maps to Dynamics 365 released products with inventory management enabled. Part numbers migrate as product numbers, and stock levels transfer to warehouse-specific inventory transactions. Supplier links map to vendor records in Accounts Payable. Some JiBe deployments use custom part number formats that require normalization during the transform phase; we flag these during discovery and apply regex or lookup tables to produce standard product codes before import.

JiBe purchase orders and requisitions (vendor references, line items, quantities, delivery dates) map to Dynamics 365 Finance and Operations or Business Central purchase orders. Open POs migrate by status, preserving the vendor-to-part linkage across the procurement workflow. Closed POs migrate as historical records for audit continuity. Purchase agreement lines map to vendor agreements or contract lines depending on the Dynamics 365 edition in scope.

JiBe chartering records (contract terms, counterparty details, voyage data, rate structures, port itineraries) map to Dynamics 365 agreements or contracts. The schema varies by JiBe deployment and may include custom fields for rate structures and voyage legs. We map counterparty to the account, voyage dates to agreement effective and expiration dates, and port itineraries to a custom related-entity or notes section. If the destination is Business Central, contracts are modeled using the Jobs module for voyage-based tracking or using service contracts.

JiBe crew records (personal details, rank, certifications, payroll associations, vessel assignments) map to Dynamics 365 Human Resources workers. Rank maps to a job title or position; certifications migrate as worker credentials with expiry dates preserved for compliance continuity. The crew-to-vessel assignment migrates as a worker assignment linked to the Asset created for the vessel. Payroll associations map to the HR payroll integration or a custom field for the payroll team to resolve. If Dynamics 365 HR is not in scope, crew accounts migrate to custom Contact entities with the same field structure.

JiBe insurance records per vessel (coverage types, policy numbers, carrier details, coverage limits, expiry dates) map to Dynamics 365 agreements with a policy type classification. Some JiBe deployments link insurance claims to incidents or maintenance records; we map those relationships to case records or work order notes in Dynamics 365. Policy expiry dates migrate as renewal reminder fields, and coverage types map to agreement categories.

JiBe incident reports linked to specific PMS locations map to Dynamics 365 service management cases or quality orders. The incident-to-job linkage preserves so that a case can reference the related work order in Asset Management. Associated costs recorded against the incident migrate as financial transactions or notes on the case. Severity and incident type map to case origin, priority, and custom category fields.

JiBe fleet hierarchies group vessels under parent fleet entities. Dynamics 365 Asset Management supports asset hierarchies through the functional location parent-child structure or through organizational hierarchies. We model the fleet as a parent functional location with vessel assets as children, enabling fleet-level reporting and maintenance plan rollup. If the shipping company uses Business Central, we use dimensions or location hierarchies instead.

JiBe commercial records capturing voyage revenue, freight charges, and commercial performance metrics map to Microsoft Dynamics 365 Sales Orders or Project entries depending on whether the shipping company bills per voyage or per contract. Revenue recognition data migrates to the appropriate financial dimension for reporting in the general ledger.

JiBe crew certification records (STCW endorsements, medical certificates, safety training, flag-state documents) map to Dynamics 365 Human Resources worker credentials. Certification type maps to credential category, expiry date to expiration date, and issuing authority to the credential issuer. The credential is linked to the worker record created from the crew account mapping. Expired certifications migrate as historical records; upcoming expirations are flagged for the compliance team to action post-migration.