Migrate from Jeeves ERP to Epicor Prophet 21

Jeeves stores a hierarchical chart of accounts with account codes, names, types, and currency assignments. We map each account to Epicor's COA structure preserving the hierarchical depth and account type classification. Multi-currency account assignments from Jeeves Expand edition carry over as Epicor account-level currency restrictions. We coordinate with the customer's Epicor admin to ensure the COA is deployed in the target company before any transaction imports begin.

Jeeves Customer records include contact details, billing and shipping addresses, credit limits, and payment terms. We map these to Epicor Customer records preserving credit hold status, payment terms, and multi-currency settings. Address records in Jeeves (which may have multiple per customer) map to Epicor ShipTo and BillTo address records with the primary address flagged.

Jeeves Vendor records mirror the customer structure with supplier-specific fields including bank details and payment terms. We map Vendors to Epicor Vendor records, preserving 1099 flag settings, W-9 status, and multi-currency assignments. Vendor address records map to Epicor's Vendor address structure.

Jeeves Items cover both products and materials with BOMs, routing, cost layers, and unit-of-measure settings. We map Items to Epicor Part records with the Jeeves item type determining Epicor's Part Type (stocked, non-stock, service, special). Cost data migrates as Epicor PartCost records against the default site. UoM conversions from Jeeves map to Epicor's UOMClass and UOM definitions.

Jeeves BOMs define multi-level product structures with component items, quantities per assembly, and operation sequences. We map these to Epicor PartMtl records linked to the parent Part, preserving the BOM revision and effective date. Multi-level BOMs require careful sequencing so that sub-assemblies are migrated before their parent BOMs; we resolve this with a topological sort of the Jeeves BOM tree before Epicor import. Alternate BOMs in Jeeves map to Epicor PartMtl records with alternate method flags.

Jeeves routing definitions assign operations to work centers with labor and machine times. We map Jeeves routings to Epicor PartRev records as Methods of Manufacturing, with each operation mapped to Epicor PartOpr and Resource records. Work center assignments from Jeeves map to Epicor Resource groups. Operation sequences, queue times, and setup times transfer to Epicor PartOpr fields. If the customer uses multiple sites in Epicor, we scope which site receives the routing.

Outstanding Jeeves payables migrate as Epicor APInvoice records with full line-item detail, vendor reference numbers, and due dates. We map the invoice header and detail lines, preserving tax codes and GL account assignments from Jeeves. Closed AP documents remain in Jeeves as historical records and do not migrate. Prepayments and partially paid invoices require careful balance-residual mapping.

Outstanding Jeeves receivables migrate as Epicor ARInvoice records with customer reference, invoice date, due date, and line-item amounts. We map the invoice header and line items preserving tax treatment and GL account assignments. Credit memos and partially collected invoices transfer with their remaining balances. Closed AR documents remain as historical records in Jeeves.

Jeeves Journal Entries carry date, description, debit and credit lines with account assignments, and reversing entry flags. We map each journal entry group to Epicor GLJrnGrp with detail lines in GLJrnLine. Jeeves's journal numbering scheme maps to Epicor's voucher number or auto-generation rule. We flag any journal entries that reference accounts not yet migrated in the COA phase and hold those for the customer's admin to resolve.

Jeeves Fixed Assets include acquisition cost, depreciation schedule, and asset category. We map to Epicor FAsset records with depreciation book values carried into FAssetBook. Depreciation methods vary by country localization and we match Jeeves's depreciation convention to the nearest Epicor book convention. Asset category assignments transfer to the FAssetCategory reference.

Jeeves Projects support time tracking, expense recording, and resource assignments. We map Project records with associated tasks, milestones, and time entries into Epicor's Project management module. WBS elements in Jeeves map to Epicor Project Phases and Tasks. If the customer uses billing and invoicing from Jeeves Projects, those assignments transfer as Epicor Project Billing rules.

Open orders in Jeeves (header and line items with delivery schedules and pricing) migrate as Epicor OrderHed and OrderDtl records. We map the order number, customer reference, order date, and line items including quantity ordered versus quantity shipped. Pricing and discounts transfer from Jeeves. Orders in Jeeves that are fully shipped and invoiced remain as historical records and do not migrate as open documents. Draft or pending orders map as OrderHed with OpenOrder=true.