Migrate from JD Edwards World to Epicor Prophet 21

World F0101 is the central address master with AN8 as the primary key referenced throughout all World tables. We split World addresses into Epicor Kinetic Customer (for AR), Supplier (for AP), Employee (for HR), and Prospect records based on address type codes (AT1) and the presence of related F0301 or F0401 records. AN8 becomes Epicor's Key1 reference for cross-referencing. Contact names, phone numbers, and email addresses map to Epicor Person records linked via Key1.

World's flexible Object.Subsidiary account format (defined per company code) maps to Epicor Kinetic GL Account segments. We design the Epicor Cost Element structure during scoping, typically using Object as the primary segment and Subsidiary as sub-account, then normalize World account numbers to Epicor's segment string format. The customer finance team validates the chart of accounts mapping before production load because incorrect account assignment corrupts financial reporting.

World F0911 stores every journal entry with account, amount, batch, and fiscal period. We extract full posting history for the customer's chosen fiscal year cutoff, transforming account numbers to Epicor GL Account segments, amounts to Epicor's currency precision, and batch references to Epicor Journal Batch records. Records referencing obsolete Cost Codes or Business Units are flagged for customer review before load. Epicor enforces balanced debits and credits on import; unbalanced entries must be corrected before loading.

World F0902 stores period and year-to-date balances. We use these to seed Epicor Kinetic GL Account Balances after the F0911 migration, setting the opening balances for each account at the migration effective date. This requires prior completion of the F0901 account structure migration so that Epicor account codes exist before balance records are inserted.

World open and historical PO records migrate to Epicor Kinetic purchase orders. We extract PO header fields (order number, supplier, terms, status) and line details (item number, quantity, unit cost, delivery date) from F4311, transforming World supplier AN8 references to Epicor Supplier IDs. Receipt routing information (World-specific) is not directly representable in Epicor; we document it as a post-migration configuration step. Closed POs migrate as historical records optionally based on the customer's fiscal year cutoff.

World order header and line records migrate to Epicor Kinetic SalesOrder. The embedded World pricing structure (which may use cascading discounts and UOM conversions not native to Epicor) requires mapping to Epicor Price Lists and Discount codes. We extract line items, taxes, freight, and backorder flags, resolving customer AN8 references to Epicor Customer IDs and item numbers to Epicor Part records. Order hold codes map to Epicor Order Hold records.

World Work Orders with routing steps and material requirements map to Epicor Kinetic Job records. World differentiates shop floor Work Orders from Maintenance Work Orders; both map to Epicor Kinetic Jobs with a JobType distinction. Routing sequences from World F3003 map to Epicor Job Operations with work center assignments; bill of materials from F3002 map to Epicor Job Materials. We perform BOM explosion during migration to pre-populate material requirements on each Job.

World F4101 is the central product catalog controlling inventory, pricing, and procurement. We map item number to Epicor Part.PartNum, description fields, and stocking UOM. World branch-plant overrides in F4102 (on-hand quantities, stocking locations, lot controls) merge into Epicor PartPlant records during migration. Unit of Measure conversions from World UOM tables map to Epicor UOMClass definitions. Parts that are stock items trigger inventory balance seeding from F4111.

World F4111 stores transaction history for receipts, issues, and adjustments. We extract current on-hand balances from the most recent F4111 records and seed Epicor Kinetic PartBin records per warehouse and lot. Transaction history migrates selectively based on the customer's fiscal year cutoff (Epicor's data volume and retention policy) as Epicor PartTran records linked to the originating Part and Warehse records.

World AR customer records are linked to F0101 by AN8 and contain billing, credit, and payment term data. We map F0301 fields (credit limits, payment terms, tax exemption codes) to Epicor Kinetic Customer records, resolving the AN8 reference to the Epicor Customer.Key1. Credit limit and tax exemption enforcement logic is Epicor-configured rather than migrated data.

World AP vendor records link to F0101 by AN8 and include payment terms, 1099 reporting data, and bank account information. We map F0401 fields to Epicor Kinetic Supplier records, including bank account details for ACH setup in the destination system (subject to the customer's security requirements). 1099 category and threshold data maps to Epicor Tax Liability codes.

World HR master records including compensation, job data, and organizational assignment are mapped from F060116 to Epicor Kinetic Employee records. Effective-dated history is preserved as Epicor Employee records with the hire date and any subsequent job changes carried forward. The customer must confirm Epicor HR module is licensed and configured before employee data loads.

World Z-prefixed custom tables (e.g., F55Z100) handle industry-specific or company-unique processes outside standard World. These are not part of the standard migration scope. We document Z-file structures and field definitions in the discovery phase and provide a written specification for the customer to recreate equivalent customizations in Epicor Kinetic using its extension framework. If custom tables are integral to business operations, customers budget for manual data entry or custom development post-migration.