Migrate from JD Edwards World to Microsoft Dynamics 365 Business Central

World's F0101 Address Master with AN8 as the primary key maps to Dynamics 365 Business Central Customer and Vendor contact entities. We preserve name formats, mailing and physical addresses, phone numbers, email addresses, and address categories. The AN8 value is stored in an external reference field so cross-references to F0301 (Customer) and F0401 (Vendor) can be resolved during downstream entity loads. Address Book category codes (AR01, VR01) map to Customer and Vendor posting groups in Business Central.

World's F0911 stores every journal entry with account (Object.Subsidiary), amount, batch number, fiscal period, and currency code. We extract full posting history, normalize account numbers against the target Chart of Accounts mapping defined by the finance team, and load into Business Central's G/L Entry table or Finance and Supply Chain Management's LedgerEntry. We flag records that reference obsolete Cost Codes, Business Units, or Subledgers not present in the approved mapping table before loading to avoid validation errors.

World's F0901 defines the Chart of Accounts structure with Object.Subsidiary segments that vary by company. F0902 carries period balances and year-to-date amounts. We normalize each World account to the target Dynamics 365 account code structure, preserve account descriptions and categories, and seed opening balances by fiscal period. Account Balances are loaded before any F0911 entry load so that trial balance reconciliation can be performed before the ledger is posted.

World's F0301 links to F0101 via AN8 and stores billing addresses, payment terms, credit limits, and tax exemption codes. We map payment terms to Business Central Payment Terms codes, tax exemption data to Tax Area assignments, and parent-child customer hierarchies to the Dynamics 365 Contact and Customer hierarchy. Credit limit enforcement logic does not migrate automatically; we document the source values for manual configuration in the destination system.

World's F0401 stores AP vendor records with payment terms, 1099 reporting data, and bank account information for ACH setup. We extract bank account details and remittance addresses subject to PCI scoping, and map 1099 box assignments to the equivalent Dynamics 365 1099 configuration. Vendor payment terms and cash discount codes migrate to Business Central Vendor Payment Terms.

Open and historical PO records migrate from F4311 with line-level detail including Receipt Routing information. We extract open POs for active migration and flag closed POs for optional historical carry-forward based on the customer's fiscal year cutoff preference. PO line prices, quantities, and delivery dates map to Business Central Purchase Line records. Receipt Routing steps in World are documented as warehouse configuration notes for the customer's implementation team rather than loaded as data.

World's F4211 stores order header and detail records with pricing, terms, backorder flags, and embedded pricing structures. We extract line items, taxes, and freight charges. World's embedded pricing may not map 1:1 to Business Central's Sales Price and Discount tables; we extract the pricing values as static line amounts and flag any pricing logic that requires rebuild as a sales price or discount group configuration post-migration.

Manufacturing Work Orders with routing steps and material requirements migrate from F4801. World differentiates between shop floor Work Orders and Maintenance Work Orders; both map to Business Central Production Order records but with separate Order Types. Routing sequences from World are extracted as manufacturing routing configuration notes; bill of material lines are extracted as production BOM component lines. The customer must configure Bill of Materials and Routing templates in the destination system before production order activation.

World's F4101 is the central product catalog controlling inventory, pricing, and procurement. F4102 stores branch-plant-specific overrides (on-hand quantities, replenishment settings, costing methods). We extract F4101 as the base Item and merge F4102 records into Business Central Stockkeeping Units (SKUs) per location so that location-specific pricing and costing are preserved. Unit of Measure conversions migrate as UOM definitions linked to Items.

Transaction history for receipts, issues, and adjustments extracts from F4111. We load on-hand balances as Item Ledger Entry open quantities for immediate seeding, and carry forward selected transaction history based on the customer's fiscal year cutoff. Full historical transaction history beyond twelve months requires additional data volume assessment and may affect load sequencing because of Business Central's entry numbering constraints.

HR master records including compensation, job data, organizational assignment, and effective-dated employment history migrate from F060116. We extract employee addresses, employment status, pay groups, and org unit assignments. Effective-dated history is preserved for compliance reporting. Compensation amounts and benefit enrollment data migrate as HR configuration notes rather than payroll setup, as payroll configuration is typically handled by the Dynamics 365 Human Resources module implementation separately.

World customers frequently create custom table files (Z-prefixed, e.g., F55Z100) for industry-specific or company-unique processes. These are not part of the standard World schema and are explicitly excluded from automated migration scope. We document the Z-file names, record counts, and field structures during discovery and deliver a written specification for each custom table so that the customer's implementation team can recreate the data model in Dynamics 365 and manually enter or import historical records. If custom tables are integral to business processes, customers must budget for manual data entry or custom development.