Migrate from JiBe to Acumatica

JiBe vessel records map to Acumatica Non-Stock Inventory Items because vessels are tracked assets, not inventory for resale. The InventoryItemCD becomes the IMO number. Maritime-specific attributes (flag state, deadweight tonnage, gross tonnage, vessel type, classification society) migrate to Usr-prefixed custom fields defined in the Acumatica Customization Manager and published via a customization project before the migration runs.

JiBe fleet groups map to Acumatica Inventory Item Groups for hierarchical categorization. Each fleet group becomes an Inventory Item Group code, and vessels belonging to that fleet are associated via the Item Group assignment on the Inventory Item record. Fleet-level attributes (region, owner operator, commercial manager) are stored as Usr-prefixed fields on the fleet group inventory item.

JiBe port records map to Acumatica Warehouse records when the port is a physical operations base, or Location records within a warehouse when the port represents a cargo handling node. Port codes (UN/LOCODE) are stored as custom identifiers. Port-specific tariff rates and handling charges migrate as Usr fields. If JiBe uses a separate port tariff table, it maps to Acumatica's separate Price List / Non-Stock Item pricing model.

JiBe voyage records — which track departure/arrival ports, cargo type, cargo quantity, voyage status, and commercial results — map to Acumatica Project Tasks under a Project record representing the voyage as a commercial contract. Voyage legs become separate tasks within the project. Cargo commercial values map to Project Task actual amounts. If Acumatica Project Accounting is not enabled, voyage data maps to a custom journal entry structure. FlitStack sequences voyage migration after port and vessel records so foreign keys resolve correctly.

JiBe crew assignments (which link a CrewMember to a Vessel for a date range, with role, rank, wage rate, and contract type) merge into Acumatica Employee records. The crew member name, nationality, and certificate expiry dates map to Employee fields. The assignment-specific role and wage rate for the current voyage association are stored as Usr-prefixed fields on the Employee record, since Acumatica does not have a native crew-to-voyage assignment table.

JiBe maintenance job cards combine defect description, maintenance type, due date, assigned technician, estimated cost, and parts used into a single record. In Acumatica, the job card description and due date map to a Purchase Order or Work Order depending on whether the maintenance requires procurement (external vendor) or internal labor. Technician assignment maps to the Employee field on the work order. Parts consumed map to inventory item issue transactions against the work order.

JiBe procurement purchase orders (vendor, PO number, line items, quantities, unit costs, status, approval workflow) map directly to Acumatica Purchase Orders. The PO number becomes the ExtRefNbr on the Acumatica PO. JiBe line items map to POLine records with InventoryID, UOM, quantity, and unit cost. Approval states in JiBe do not carry over — Acumatica's approval workflow is reconfigured post-migration using Acumatica's approval map.

JiBe vessel certificates (Flag State Certificate, Safety Certificate, Classification Certificate, Insurance Certificate, P&I Certificate) have expiry dates and issuing authorities but no native equivalent in Acumatica. Each certificate type is stored as a Usr-prefixed custom field on the InventoryItem (vessel) record, and the certificate document is attached using Acumatica's file attachment mechanism. Certificate expiry alert logic must be rebuilt as Acumatica alert rules.

JiBe survey records (PSC inspection, flag state inspection, class society survey) contain inspection date, outcome, deficiencies found, and next due date. These map to Usr-prefixed custom fields on the vessel InventoryItem record for outcome and next-due tracking. Inspection notes and deficiency lists migrate as Note records attached to the vessel, since Acumatica's standard Notes DAC supports rich text.

JiBe bunker fueling records (port, date, fuel type, quantity, supplier, cost per MT, total cost) map to Acumatica inventory receipt transactions for the fuel inventory item. The supplier maps to the VendorID on the receipt. If Acumatica's Fuel Management add-on is active, bunker records map to its specific DAC; otherwise, they use the standard inventory receipt with Usr-prefixed custom fields for fuel grade and delivery terms.

JiBe charter party records (charterer, hire rate, payment terms, redelivery clause, commission) map to an Acumatica Project record with a custom contract template. Hire revenue recognition maps to Project billing rules. Commission tracking uses a Usr-prefixed custom field on the Project. If the charter is a spot voyage, the Project billing rule generates an AR Invoice on completion; for time charters, it generates recurring billing lines.

JiBe allows extended custom objects and attributes on any standard entity (e.g., a custom 'Hull Insurance Policy' object linked to vessels, or a 'Port Agent' object linked to ports). Each custom object maps to a new Acumatica DAC Extension using the Tooling API, or to Usr-prefixed custom fields added to the target DAC via the Customization Manager. N:N custom object relationships between vessels and third parties are handled via Acumatica's Relation table DAC or a custom junction table.

JiBe file attachments (certificates, inspection reports, contracts, bunker delivery notes) attached to any record migrate to Acumatica Note records or Files attached to the corresponding DAC. The attachment is downloaded from JiBe and re-uploaded to Acumatica's file storage linked to the target record. FlitStack preserves the original file name and MIME type. Acumatica's default file storage limit of 25MB per file applies — files exceeding this are flagged before migration.

JiBe owner and operator entities (which may be the same party as the commercial manager or separate) map to Acumatica Customer records if they are revenue-facing (charterers, freight customers), Vendor records if they are supply-facing (bunker suppliers, port agents), or both if the entity plays both roles. JiBe entity codes map to Acumatica AcctCD. Multi-role entities receive both Customer and Vendor records with the same party ID linked.