Migrate from JiBe to Epicor Prophet 21

JiBe Vessel master records (name, IMO number, flag state, vessel type, fleet hierarchy parent) map to Epicor Part records with a custom asset linkage. We create an Epicor Part record per vessel using the vessel's IMO number as the Part Number, vessel name as the Part Description, and vessel type as a UDF. The fleet parent relationship maps to an Epicor Job or BOM structure if the customer uses Epicor's project or contract manufacturing module to represent fleet-level grouping. Vessel-to-fleet groupings require customer confirmation during scoping because Epicor's native asset hierarchy is site-centric rather than fleet-centric.

JiBe PMS location hierarchies define machinery and component structures per vessel. Because JiBe allows custom PMS hierarchies per vessel, the same machinery type may model differently across ships. We profile each vessel's PMS structure during discovery, normalize component names against a shared taxonomy where possible, and create Epicor Part records or BOM components for each unique location node. Vessels with deeply nested custom hierarchies may require multi-level BOM structures in Epicor that the customer's engineering team validates before production migration.

JiBe maintenance jobs (status, priority, work order data, linked PMS location, historical completion records) map to Epicor Work Order Header and Work Order Detail records. Open jobs migrate with current status flags (Open, In Progress, Overdue) mapped to Epicor Job status values. Completed historical jobs migrate as closed Work Orders with the original completion date preserved in the JobHead.JobCompleteDate field. JiBe's incident-to-job linkage migrates as a Work Order character field reference rather than a native Epicor link.

JiBe spare parts (part numbers, stock levels, reorder points, supplier links, custom part number formats) map to Epicor Part and PartBin records. We normalize custom JiBe part number formats into Epicor-standard Part.PartNum during transformation. Stock levels migrate to PartBin.OnhandQty per site and warehouse. Reorder points migrate to PartReplenishment or as a UDF depending on the customer's Epicor inventory configuration. Supplier links map to PartXRefVend records in Epicor, preserving the vendor-to-part linkage across the procurement workflow.

JiBe purchase orders and requisitions (vendor, vessel-level procurement needs, line items, status) map to Epicor PO Header and PO Release records. Open POs migrate by status (Open, Released, Pending) and preserve the vendor-to-part linkage. Closed POs migrate as historical records for audit continuity. JiBe custom fields for rate structures or approval chains become Epicor PO character fields or require a post-migration configuration review with the customer's procurement admin.

JiBe chartering records contain contract terms, counterparty details, voyage data, rate structures, and port itineraries. Epicor ERP does not have a native chartering module. We map chartering agreements to Epicor Quote (for voyage rate quotes) or a custom Contract object built in Epicor's customization framework. Counterparty details map to Epicor Customer or Supplier records depending on charter type. Custom fields for rate structures and itineraries require customer-specific configuration during scoping and may require post-migration admin rebuild for full functional parity.

JiBe crew records (personal details, rank, certifications, payroll associations, vessel assignment, certification expiry dates) map to Epicor Employee records. Rank maps to a Job Role or Department code in Epicor HR. Certifications and expiry dates migrate as custom HR fields or as Employee competency records depending on whether the customer licenses Epicor MES or HR module. Crew-to-vessel assignments migrate as Employee Ship/Asset assignments via a custom field or Epicor's project or work force management module. Certification expiry dates are preserved for compliance continuity.

JiBe insurance records per vessel carry coverage types, policy numbers, carrier details, and in some deployments linked incident claims. Epicor ERP does not have a native insurance policy module. We create a custom InsurancePolicy object in Epicor with fields for policy number, carrier, coverage type, effective dates, and linked asset (vessel Part record). Claims linked to incidents map as separate Claim records linked to the InsurancePolicy custom object. This is a configuration-heavy mapping that requires customer-specific schema design during discovery.

JiBe incident reports link to PMS locations and can trigger maintenance jobs with associated costs. Epicor handles equipment failures through its MES, Maintenance, or Quality modules depending on the Epicor Kinetic edition licensed. We map incidents to Epicor ECO (Engineering Change Order) for defect-driven changes or to a custom Incident object. Incident-to-job linkage migrates as a character field reference. Cost data from incidents migrates to Epicor PartCost or JobOper records where applicable. The customer confirms the destination module during scoping.

JiBe commercial records (freight revenue, voyage settlement, commercial KPIs) map to Epicor Sales Order, Invoice, or AR Invoice records depending on the customer's Epicor financials configuration. Counterparty details migrate to Epicor Customer records. Voyage settlement data maps to Epicor Project or Contract records if the customer licenses Epicor Project Management. Commercial KPIs migrate as numeric UDFs on the relevant document headers. The customer confirms the financial module configuration during discovery.

JiBe fleet hierarchies group vessels under parent fleet structures. Epicor's organizational model uses Sites and Business Units. We map JiBe fleet parents to Epicor Site records or Business Unit codes, with vessel-level records linked to the appropriate Site. Multi-fleet organizations requiring hierarchical reporting above the Site level use Epicor's Company or Division structure if licensed. This mapping requires customer-specific organizational design during scoping.

JiBe BI reports and dashboards are configuration artifacts built from the platform's internal data model. Epicor Kinetic dashboards and BAQ reports must be rebuilt from migrated data. We extract the underlying data—maintenance records, performance metrics, parts consumption, crew hours, commercial KPIs—and deliver it in structured CSV and JSON formats that the customer's Epicor admin uses to rebuild equivalent reports in Epicor BAQ, Kinetic dashboards, or a connected BI tool such as Power BI or Tableau.