Jd edwards migration checklist — 60+ JDE-specific verification items covering tablespace audits, OMW inventory completeness, F-series row counts, AS/400 driver compatibility, support contract review and signed treatment plans. Evidence-driven, not status-driven.
The items that actually derail JDE migrations are not on generic ERP checklists. AS/400 driver compatibility, F0911 orphan rows, R55xxxxx UBE treatment, JDE Tools patch-currency — these are the killers.
Most consultancies hand you a generic 'pre-migration checklist' that could have been written for any source ERP. It asks about scope and timeline and stakeholders and risks. It does not ask whether your AS/400 ODBC driver supports the codepage your DB2/400 source uses, or whether the F9210 Data Dictionary extract has been compared against the OMW catalog to surface custom items missing from one side, or whether your F1202 fixed-asset balances actually reconcile to the depreciation schedule before extract starts.
The jd edwards migration checklist is JDE-specific because the JDE risks are JDE-specific. JDE EnterpriseOne customers carry custom NER and BSFN business functions, custom UBE batch reports prefixed R55xxxxx, custom Form Design Aid forms, custom Data Dictionary items, custom processing-option defaults. JDE World customers add an AS/400 source layer with its own driver and library-list considerations. Both carry F-series tables (F0911, F0411, F03B11, F4111, F4211, F4311, F0901, F0006) with JDE-particular semantics that a generic checklist does not understand.
Use the checklist at three stage-gates. First at the start of assessment (week 1) to surface unknowns before any fixed-price commitment. Second at the end of assessment (week 4) to confirm wave scope is evidence-grounded. Third immediately before parallel-run start (week 10) to confirm every prerequisite for go-live testing is in place. Evidence per item. Signatures per gate. The checklist becomes part of the audit pack at go-live.
From 50+ JDE programmes, the items that most often surface late and cause re-baseline.
JDE World extraction relies on DB2/400 ODBC. Driver version, codepage and library-list must match the source. A 30-year-old EBCDIC codepage will silently mangle string fields if the driver doesn't translate properly.
Custom Data Dictionary items in F9210 must reconcile against the OMW catalog (F9860/F9861/F98711). Items in one and not the other indicate orphaned objects that won't migrate cleanly.
Ledger rows with NULL batch numbers exist on most production JDE instances. They will not pass FBDI Journal Import validation. Catch them before extract, not after FBDI errors.
JDE EnterpriseOne backend has multiple schemas (data + control + system + business-unit-specific). Read-only credentials must work against every schema in scope — not just the data schema everyone defaults to.
Every custom UBE report needs a signed retire/rebuild/extend/sunset disposition. 'TBD' is not a disposition. Unsigned R55xxxxx items are the most common late-surface item.
Per-plant decision whether JDE Manufacturing stays. Must be made before wave scope is locked. Hybrid Fusion-Financials-plus-JDE-Manufacturing is a stable steady-state for years.
The checklist is not a one-time form. It is a living artifact reviewed at each programme stage-gate with signatures captured.
Surface unknowns before fixed-price scope. Run F9860 OMW catalog extract, F0911 row count, F0411 stuck-approval scan, F4111 vs F4101 imbalance scan, AS/400 driver compatibility test for World. Output: discovery risk register driving scope and timeline.
Confirm wave scope is evidence-grounded. R55xxxxx treatment plan signed. COA crosswalk drafted against real F0006/F0901 master data. Plant-level manufacturing decision made. Fusion target pod confirmed. Output: signed migration plan with named business sponsors.
Confirm every prerequisite for parallel run is in place. Read-only credentials tested per schema. FBDI ESS submission tested with sample payload. UAT scripts published. Super-user network trained. Output: signed parallel-run start, go/no-go criteria committed.
Final checklist sweep before cutover. F0902 cent-level reconciliation completed. UAT acceptance signed per business area. Custom UBE replacements validated. Cutover runbook reviewed. Rollback procedure tested. Output: signed go/no-go decision, audit pack assembled.
Confirm hyper-care exit criteria. First two full month-end closes completed in Fusion. Open-tickets reviewed and triaged. Steady-state owners identified per business area. Integration retire-vs-permanent dispositions confirmed. Output: signed steady-state hand-off.
Walk every variance from the original migration plan. Lessons-learned captured. Items fed into the next wave (SCM in wave 2, Manufacturing in wave 3) or the next M&A consolidation. Checklist refined for the next instance.
Six of the 60+ checklist items, illustrating the JDE-specific shape. Each carries a target value, a query and an evidence reference.
Pull row count per fiscal year (PHYR field) and per company (CO field) and per document type (DCT). Output drives extract duration estimate and FBDI Journal volume planning.
Snapshot of F0902 period balances at a named cutoff date. Becomes the source of truth for cent-level reconciliation at Company × Account × Period grain in parallel run.
Voucher count split by status (open / paid / voided / in-process / awaiting approval). Open and approval-pending vouchers drive FBDI AP Invoice Import volume.
Sales order detail count by status code (open / partially shipped / closed / cancelled). Open SOs drive Fusion SCM FBDI volume; closed history drives archive-or-load decision.
Fixed-asset master count plus reconciliation check against F1202 balances. Drift indicates manual journals against asset accounts that never updated F1202.
Address Book count split by search type (V supplier / C customer / E employee / etc). Drives Fusion supplier/customer/worker FBDI volume and the address-book split logic.
The jd edwards migration checklist is a 60+ item structured pre-migration verification covering every JDE-specific risk that can derail a JDE-to-Fusion programme. Use it at three points: at the start of the assessment phase (week 1 of discovery) to surface unknowns before the fixed-price scope is signed, at the end of the assessment phase (around week 4) to confirm the wave scope and timeline have evidence, and again immediately before parallel-run start (around week 10) to confirm every prerequisite is in place. The checklist is not a one-time form; it is a living artifact reviewed at each programme stage-gate. The items themselves are JDE-specific — tablespace audits, OMW inventory completeness, F-series row counts, AS/400 source extract feasibility for World customers, JDE support contract review — not generic ERP checklist items that any migration consultancy could write.
Infrastructure items in the jd edwards migration checklist cover: JDE source database tablespace audit (Oracle DB / SQL Server / DB2 LUW for EnterpriseOne, DB2/400 for World) with current size, growth-rate and free-space confirmed; read-only extract credentials provisioned and tested against every JDE source schema; AS/400 ODBC/JDBC driver compatibility verified for World source customers (driver version, codepage, library list); JDE AIS Server availability and authentication confirmed for any flow that needs business-function context; Oracle Fusion target pod confirmed (production-mirror-of-production or dedicated migration pod, FBDI ESS bandwidth, batch-import scheduling); network connectivity from extract server to JDE source and from staging server to Fusion FBDI endpoint tested with real payload size; secrets management for source-to-target credentials documented and reviewed.
OMW and customization items in the jd edwards migration checklist are critical because customization is the single biggest source of timeline overrun. Items include: F9860/F9861/F98711 OMW catalog extract completed and reviewed; every R55xxxxx UBE batch report classified retire/rebuild/extend/sunset with signed-off treatment; every custom NER (Named Event Rules) business function classified; every custom BSFN (C business function) classified; every custom Form Design Aid form classified; every custom Data Dictionary item in F9210 mapped to a Fusion DFF target or sunset; every custom data structure inventoried; every custom version (R-version overrides) inventoried; every custom processing-option default reviewed; the treatment plan signed off by both business sponsors and IT architecture before crosswalk build begins.
F-series row-count items in the jd edwards migration checklist anchor the timeline and the FBDI volume planning. Items include: F0911 Account Ledger row count by fiscal year (full historical depth confirmed, archive-vs-load decision documented); F0902 Account Balances row count for reconciliation baseline; F0411 AP Voucher row count by status (open, paid, voided, in-process); F03B11 AR Invoice row count by status; F4111 Item Ledger row count by transaction year; F4211 Sales Order Detail row count by status; F4311 Purchase Order Detail row count by status; F1201/F1202 Fixed Asset and Balance row count; F0101 Address Book row count by type (supplier / customer / employee / other); F4101 Item Master row count; F3112/F31122 manufacturing routing and time-transaction row counts; F0011 Batch Header row count for batch reconciliation. Volume drives extract duration, transform compute and FBDI submission planning.
Change-management items in the jd edwards migration checklist cover the human side that determines whether the programme lands. Items include: business sponsors named per business area (AP, AR, GL, FA, Inventory, Procurement, Manufacturing, Plant) with allocated time; super-user network identified (one per area per plant) with training and UAT roles defined; role-based training plan drafted with delivery dates per business area; UAT script library drafted with named scenarios per business area run against converted data (not demo data); communication plan published with weekly stakeholder updates and monthly steering-committee touchpoints; 60-day hyper-care window planned with named on-call resources from Syntra ETL and customer IT; executive sponsor visible in weekly stand-up through go-live; user-population-by-role inventory complete for licence-true-up against Fusion subscription model.
Support-contract items in the jd edwards migration checklist matter because JDE Premier Support runs to 2034 for EnterpriseOne but on different terms for World and for specific older Tools releases. Items include: current JDE support level confirmed (Premier / Extended / Sustaining) and end-date documented; JDE Tools release version inventoried per JDE instance with patch-currency status; JDE module licences inventoried with user counts and named-user-vs-application-user breakdown; Oracle Database / SQL Server / DB2 licence model documented (per-core, per-named-user, capacity); the migration's effect on JDE support and DB licensing modeled (e.g. JDE read-only-archive post-migration may move to Sustaining Support to reduce cost); Fusion subscription model designed with module mix, user roles and user counts; M&A scenarios over the next 3 years modeled for both JDE-side and Fusion-side licence impact.
Data-quality items in the jd edwards migration checklist surface remediation work that should happen before extract, not after FBDI errors. Items include: F0911 orphan-row scan (NULL batch numbers, missing posting status); F0411 stuck-approval scan (vouchers in PE/PA state older than 90 days); F4111 vs F4101 item imbalance scan; F0006 missing-category-code scan; F1202 fixed-asset drift scan against F1201 master; F0101 duplicate-address-book scan (same supplier across multiple ABNs); F0010 multi-instance company-number conflict scan (for M&A-consolidated estates); F0901 unused-account scan (accounts with zero F0902 history across the retention window — candidates for sunset rather than migration). Each scan produces a remediation queue; the queue is worked down inside the programme, not deferred to post-go-live.
Completion of the jd edwards migration checklist is evidence-driven, not status-driven. Every item carries an evidence reference: the OMW catalog extract date and file location, the F-series row counts as of a named cutoff date, the named business sponsor's signature on the treatment plan, the tested ODBC driver version, the proof of read-only credential against every source schema, the proof of FBDI ESS submission test with sample payload, the proof of network bandwidth between extract server and Fusion endpoint, the data-quality remediation queue with rows-cleared counts. The completed checklist becomes part of the audit pack alongside the migration plan, the parallel-run reconciliation, the go/no-go decision and the cutover runbook. Auditors love it; consultants resist it; programmes that ship have it.
Book a working session. We will walk every JDE-specific item against your actual environment — F-series row counts, OMW catalog completeness, AS/400 driver compatibility, F0911 orphan scan, F0411 stuck approvals — and produce the signed evidence pack your steering committee needs.