How long does an Oracle JD Edwards EnterpriseOne to Acumatica migration take?

Most JD Edwards to Acumatica migrations run 4–8 weeks for under 500,000 records across core F-tables (F0101, F0911, F4211, F4101). Environments exceeding 2M records or carrying extensive manufacturing data in F3002/F3003 typically extend to 8–16 weeks. The longest phase is typically the Address Book split planning and the BOM/routing configuration guide — the data migration itself runs within the cutover window once those are resolved.

Will my JD Edwards workflows and UBE batch jobs migrate to Acumatica?

No. JD Edwards workflow definitions stored in Workflow Engine and UBE (Universal Batch Engine) report definitions in Object Librarian do not migrate. These are tied to JD Edwards's execution framework and have no equivalent in Acumatica's architecture. We export your workflow definitions as documentation and your UBE report specifications as reference files so your Acumatica team can rebuild them as Acumatica Generic Inquiries or connect an external reporting tool. This is the standard practice for every JD Edwards to Acumatica migration.

What happens to the JD Edwards Address Book (F0101) in Acumatica?

JD Edwards F0101 is a single table holding customers, vendors, and employees under one AN8 number. Acumatica requires separate Customer, Vendor, and Employee entities. We split each F0101 record by role — using category codes (PE01–PE08), business unit flags, and address type indicators — and load them as separate entities in Acumatica. Any record that serves multiple roles generates separate Customer, Vendor, and/or Employee entries all linked back to the original AN8 for traceability. Conflicts (e.g., different tax IDs per role) are flagged during the sample migration for your team to resolve.

Can I migrate JD Edwards custom UDOs (F9860/F9861 tables) to Acumatica?

Yes. We catalog every User Defined Object in your JD Edwards pathcode — custom tables, custom forms, and custom reports — and map each to an equivalent Acumatica construct. Custom tables become separate database tables in Acumatica linked to standard entities via custom relationships. Custom fields become Acumatica custom fields on the corresponding entity. We deliver a UDO catalog with the mapping for each object so your Acumatica admin can build the equivalent during configuration. Complex custom logic embedded in UDO business functions cannot migrate automatically and requires a rebuild in Acumatica's customization framework.

Does the migration affect my JD Edwards system during the cutover?

No. FlitStack AI uses scoped read access to extract data from JD Edwards — your team continues working in the system throughout the migration. We read via AIS Server REST endpoints where available, or via direct database export from the JD Edwards Oracle/SQL Server instance for tables without API coverage. A delta-pickup window of 24–48 hours after the initial load captures any new or modified records created during the cutover, so Acumatica reflects JD Edwards's final state at go-live.

How are JD Edwards GL account segments mapped to Acumatica's chart of accounts?

JD Edwards stores GL accounts as multiple segments in F0911 (GLR01–GLR11) governed by the account mask defined in D0900160. Acumatica uses a flat AccountCD with configurable segment separators (e.g., '00-1100-0000'). We map each JD Edwards segment to its corresponding Acumatica segment position based on your account mask, concatenating them into the target AccountCD format during the migration. If your JD Edwards chart uses more than four segments, we flag this during the assessment — Acumatica's standard segment model supports up to four by default, and additional segments require a customization plan.

What happens to my JD Edwards BOMs and routings in Acumatica manufacturing?

JD Edwards BOMs (F3002) and routings (F3003) carry revision levels, operation sequences, and work center assignments that Acumatica represents differently. We export all F3002 and F3003 records and generate a BOM/routing setup worksheet — showing each F3002 revision mapped to a separate Acumatica BillOfMaterials revision and each F3003 operation mapped to an Acumatica ManufacturingRouting operation sequence. Your manufacturing team applies this worksheet during Acumatica configuration before production orders run, since Acumatica resolves BOMs by effective date rather than explicit revision selection.

Oracle JD Edwards EnterpriseOne to Acumatica Migration — Field-Level Mapping & Rollback

Object mapping

How Oracle JD Edwards EnterpriseOne objects map to Acumatica

Each row shows how a Oracle JD Edwards EnterpriseOne object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Oracle JD Edwards EnterpriseOne

F0101 Address Book

maps to

Acumatica

Customer / Vendor / Employee

1:many

Fully supported

JD Edwards F0101 holds customers, vendors, and employees in a single table with category codes distinguishing entity types. We split each record into separate Customer, Vendor, and/or Employee entities in Acumatica based on F0101.AN8 category code flags and business unit assignments. Duplicate detection applies where the same entity plays multiple roles.

Oracle JD Edwards EnterpriseOne

F4211 Sales Order Header

maps to

Acumatica

SalesOrder

1:1

Fully supported

F4211.SD DOCO (document number) and SDCO (company) map to Acumatica SalesOrder.OrderNbr and BranchID respectively. Order dates (F4211.SDDJ) preserve as OrderDate; status codes (F4211.SD DrummondST) map to Acumatica status list values using a value-mapping table built during the assessment phase. Line item taxes and freight charges from F4211 transfer as separate adjustment lines on the SalesOrder.

Oracle JD Edwards EnterpriseOne

F4211 Sales Order Detail

maps to

Acumatica

SOLine

1:1

Fully supported

F4211 line items (F4211.SDLNID for line number, SDUORG for ordered quantity, SDUPRC for unit price) map to Acumatica SOLine with the parent SalesOrder linked via OrderNbr. LOT/serial number references from F4211 carry forward as inventory assignment notes on each SOLine. Extended description fields from F4211.SDLTX translate to Acumatica SOLine details.

Oracle JD Edwards EnterpriseOne

F0911 GL Journal Entry

maps to

Acumatica

GLTransaction

1:1

Fully supported

F0911.GLELCD (ledger type), GLJBCD (batch number), GLDCT (document type), and GLAA (amount) map to Acumatica GLTransaction.LedgerID, BatchNbr, TransactionType, and amount fields respectively. Original JD Edwards account numbers (F0911.GLR01–GLR11 segment structure) map to Acumatica AccountCD segments per your chart of accounts setup plan.

Oracle JD Edwards EnterpriseOne

F03B Accounts Receivable

maps to

Acumatica

ARInvoice / ARPayment

1:1

Fully supported

F03B.RPDOC (document number) and RPKCO (company) map to Acumatica ARInvoice.RefNbr. Open invoices (F03B.RPSTRST = 'D') migrate as ARInvoice with status 'Open'; paid invoices as 'Closed'. Payment applications from F03B13 carry as ARPayment applications against the migrated invoices. Credit memos from F03B11 map to AR Credit Memo documents in Acumatica with proper document type assignment.

Oracle JD Edwards EnterpriseOne

F4311 Purchase Order

maps to

Acumatica

PurchaseOrder / POLine

1:1

Fully supported

F4311.PODOCO (PO number) maps to Acumatica PurchaseOrder.OrderNbr. Vendor key (F4311.POAN8) resolves via the F0101 split to a Vendor entity. Line items F4311.PLLNID map to POLine with item, quantity, and cost fields carried over. Approval workflows from F4311 transfer as PO status tracking notes for the Acumatica purchasing team.

Oracle JD Edwards EnterpriseOne

F4101 Item Master

maps to

Acumatica

InventoryItem

1:1

Fully supported

F4101.IMLITM (item number) and IMDSCD (description) map to Acumatica InventoryItem.InventoryCD and Description. Unit of measure from F4101.IMUOM maps to UOM with UOMClass grouping. Warehouse locations from F4101 transfer as WarehouseID assignments on inventory records. Planning data including min/max levels from F4101.PLDFQ and safety stock quantities map to Acumatica Item Planning settings.

Oracle JD Edwards EnterpriseOne

F1201 Asset Master

maps to

Acumatica

FixedAsset

1:1

Fully supported

F1201.FAAN8 (asset number) maps to Acumatica FixedAsset.AssetCD. Depreciation schedules from F0911 (asset life, depreciation method codes) carry as FixedAsset.DepreciationMethod and UsefulLife. Asset category codes from F1201 map to AssetClassID via a value-mapping table. Acquisition dates and asset locations from F1201 transfer to corresponding Acumatica FixedAsset fields for complete asset tracking.

Oracle JD Edwards EnterpriseOne

F3002 BOM Header

maps to

Acumatica

BillOfMaterials

1:1

Fully supported

F3002 stores BOMs with revision levels (F3002.MMREV) and bill type (F3002.MMTBM). Acumatica BillOfMaterials.BOMType distinguishes between 'Template' and ' production'. Each BOM revision becomes a separate Acumatica BOM revision linked by the same InventoryItemID — master BillOfMaterials holds the parent item reference.

Oracle JD Edwards EnterpriseOne

F3003 Routing

maps to

Acumatica

ManufacturingRouting

1:1

Fully supported

F3003 operation sequences (F3003.MMOPC) and work center (F3003.MMWCC) map to Acumatica ManufacturingRouting.OperationSeq and WorkCenterID. Machine and labor hours (F3003.MMEMH, MMLBRH) transfer as RunHours and LaborHours. Since JD Edwards routing operations use a different step-reference model than Acumatica, we generate a setup guide for your Acumatica manufacturing admin to validate operation sequence order before production orders run.

Oracle JD Edwards EnterpriseOne

F3111 Work Order

maps to

Acumatica

ManufacturingOrder

1:1

Fully supported

F3111.WADOCO (work order number) maps to Acumatica ManufacturingOrder.ManufacturingOrderNbr. Status (F3111.WASTRT) value-maps to Acumatica status (Pending, In Process, Completed, Cancelled). The parent item from F3111.WAMMCU links to the BOM via InventoryItem lookup. Material requirements from F3111 lines transfer as ManufacturingOrderMaterialDetails with material IDs resolved through the F4101 inventory item mapping.

Oracle JD Edwards EnterpriseOne

F40041 Pricing Schedule

maps to

Acumatica

PriceList

1:1

Fully supported

F40041 stores customer-specific and volume-based pricing schedules that don't map 1:1 to Acumatica PriceList. We export all pricing schedule records and generate a PriceList setup plan showing which F40041 records map to which Acumatica PriceList and PriceBreak entries. Your Acumatica admin applies the plan during configuration before go-live.

Oracle JD Edwards EnterpriseOne

F9860 Object Librarian

maps to

Acumatica

Custom Field / Extension

1:1

Fully supported

User Defined Objects (UDOs) stored in JD Edwards F9860 and F9861 tables (custom tables, forms, reports) do not migrate directly. We catalog every UDO in your pathcode and map each to an Acumatica custom field definition or extension class. UDOs that represent data (custom tables) become separate screens in Acumatica built as custom DB tables linked to standard entities.

Oracle JD Edwards EnterpriseOne

F98MODAT Media Objects

maps to

Acumatica

Note / Attachment

1:1

Fully supported

JD Edwards stores file attachments in F98MODAT (media objects) linked to records via F00165 keys. We export media objects and re-upload them to Acumatica as Notes or File attachments on the corresponding migrated records. Binary media (images, PDFs) preserve original filenames and MIME types during re-upload.

Oracle JD Edwards EnterpriseOne	Acumatica	Compatibility
F0101 Address Book	Customer / Vendor / Employee1:many	Fully supported
F4211 Sales Order Header	SalesOrder1:1	Fully supported
F4211 Sales Order Detail	SOLine1:1	Fully supported
F0911 GL Journal Entry	GLTransaction1:1	Fully supported
F03B Accounts Receivable	ARInvoice / ARPayment1:1	Fully supported
F4311 Purchase Order	PurchaseOrder / POLine1:1	Fully supported
F4101 Item Master	InventoryItem1:1	Fully supported
F1201 Asset Master	FixedAsset1:1	Fully supported
F3002 BOM Header	BillOfMaterials1:1	Fully supported
F3003 Routing	ManufacturingRouting1:1	Fully supported
F3111 Work Order	ManufacturingOrder1:1	Fully supported
F40041 Pricing Schedule	PriceList1:1	Fully supported
F9860 Object Librarian	Custom Field / Extension1:1	Fully supported
F98MODAT Media Objects	Note / Attachment1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Oracle JD Edwards EnterpriseOne gotchas

High

JDE-to-Cloud version parity is mandatory

High

Media objects must be pre-loaded before export

Medium

User Defined Objects lose their project reservation

Medium

AIS REST API requires token-based authentication on v2 endpoints

Low

Workflow thresholds silently suppress notifications

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Oracle JD Edwards EnterpriseOne gotchas		Acumatica gotchas
Severity	Issue	Severity	Issue
High	JDE-to-Cloud version parity is mandatory	High	API user licenses cap concurrent sessions and request throughput
High	Media objects must be pre-loaded before export	High	Multi-tenant filtering requires CompanyID awareness
Medium	User Defined Objects lose their project reservation	Medium	Custom fields require separate discovery before field mapping
Medium	AIS REST API requires token-based authentication on v2 endpoints	Medium	Notes and attachments use a separate linked table structure
Low	Workflow thresholds silently suppress notifications	Low	Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

F0101 Address Book split creates orphaned contact records if entity resolution fails

JD Edwards F0101 is a single table where one AN8 number can represent a customer, a vendor, and an employee simultaneously — and all three roles can have different addresses, payment terms, and category codes. Acumatica requires separate Customer, Vendor, and Employee records, each with their own entity ID. The migration splits each F0101 row by role (using F0101.PE01–PE08 category codes and business unit flags), but if a record has conflicting role assignments (e.g., a customer-vendor with different tax IDs per role), the split produces orphan relationships that Acumatica's referential integrity rejects. We flag these during the sample migration so you can disambiguate before the full load.
JD Edwards account segments map to Acumatica's flat AccountCD, not multi-segment GL

JD Edwards GL accounts use a configurable mask (typically 6–11 characters split into company, cost center, and account segments stored in F0911.GLR01–GLR11). Acumatica's GL uses a flat AccountCD string with a configurable segment separator (e.g., '00-1100-0000'). The migration must map each JD Edwards segment to its corresponding Acumatica segment position based on the account mask defined in your JD Edwards D0900160 setup. If your JD Edwards chart uses more than four segments, Acumatica's standard segment model may require a customization plan before data lands.
F3002 BOM revisions must be sequenced into Acumatica's BOM revision model

JD Edwards BOMs store multiple revisions per item using F3002.MMREV (revision code) and effective dates — a single parent item can have five active BOM revisions for different product versions. Acumatica BillOfMaterials holds one active BOM per InventoryItemID at a time, with revisions tracked as separate BOMID records. We map each F3002 revision to a distinct Acumatica BOM, but Acumatica's BOM assignment logic on ManufacturingOrder uses the 'effective from date' rather than explicit revision selection — your manufacturing admin must validate that Acumatica resolves the correct BOM at order creation time.
Pricing schedules from F40041 require a manual Acumatica price list rebuild

JD Edwards Advanced Pricing stores complex pricing rules (volume breaks, contract pricing, customer-specific overrides) across F40041 (pricing headers), F4074 (price adjustments), and F4077 (adjustment details). Acumatica PriceList supports price breaks and customer-specific pricing but uses a different data model (PriceBreak rows with FromQuantity and ToQuantity rather than F4077 adjustment detail rows). We export all F40041 records and F4074/F4077 detail rows as a pricing schedule reference file. Your Acumatica admin rebuilds each schedule as an Acumatica PriceList using that reference — automated field mapping cannot capture the conditional logic that JD Edwards pricing rules evaluate at order entry.
UBE batch report definitions and media object binaries do not migrate

JD Edwards UBEs (Universal Batch Engines — reports like R03B505 for AR aging, R09410 for GL posting) store report definitions in the Object Librarian (F9860/F9861) tied to pathcodes. Acumatica has no equivalent to UBE — financial and operational reports must be rebuilt as Generic Inquiries or exported to an external reporting tool. Similarly, F98MODAT stores media object binaries (scanned documents, images, attachments) in the JD Edwards database, and while we re-upload these as Acumatica Notes/Attachments, the original UBE report formats and the metadata linking them to specific records cannot be reconstructed in Acumatica.

Migration approach

Six steps for a successful Oracle JD Edwards EnterpriseOne to Acumatica data migration

Inventory JD Edwards environment: F-tables, UDOs, and pathcode audit

FlitStack connects to your JD Edwards environment via AIS Server REST endpoints (or direct DB export if AIS is unavailable) and produces a complete data inventory: count of records per F-table, list of active UDOs in Object Librarian, count of pricing schedules in F40041, and count of BOM/routing records in F3002/F3003. This audit determines the migration scope, identifies Address Book records requiring multi-role split logic, and surfaces any deprecated tables that need custom export scripts.
Map F-table schema to Acumatica entities and build the Address Book split plan

We generate a field-level mapping document for every active F-table, identifying direct field matches (F0101.AN8 → Customer.AcctCD), value-mapped fields (F0101.AT1 → CustomerClassID), and transformed fields (F0911.GLR01–GLR11 → AccountCD). For the Address Book, we produce a split matrix showing how each AN8 distributes across Customer, Vendor, and Employee entities, with the entity resolution rules your team validates before the migration runs.
Run sample migration with field-level diff on 500–1,000 representative records

A representative slice of data — covering the Address Book split, at least one open sales order, a closed AR invoice, one BOM, and a work order — migrates first. We generate a field-level diff showing the JD Edwards source value and the Acumatica destination value for every mapped field. You verify the Address Book split logic, GL account concatenation, and BOM revision assignment before the full migration proceeds. Any mapping adjustments are captured and applied to the full load script.
Execute full migration with sequenced table loads and delta-pickup window

The migration runs in dependency order: F0101 (Address Book) first, then F4101 (Items), then F0911 (GL), then F03B/F04 (AR/AP), then F4211/F4311 (Orders), then F3002/F3003/F3111 (Manufacturing). A delta-pickup window of 24–48 hours captures any records created or modified in JD Edwards during the cutover. FlitStack generates an audit log of every record loaded, and one-click rollback reverts the Acumatica environment to its pre-migration state if reconciliation uncovers unexpected data issues.
Deliver Acumatica configuration plan for pricing, BOMs, routings, and UDOs

After data lands, FlitStack delivers a configuration plan for everything that required manual Acumatica-side setup: a price list rebuild guide from the exported F40041/F4074/F4077 data, a BOM and routing setup worksheet from F3002/F3003 records, a UDO catalog mapping each F9860 object to an Acumatica custom field or extension, and an Acumatica User Defined Screen plan for any legacy custom tables. Your Acumatica implementation team executes the plan; FlitStack validates the configuration matches the migration intent before go-live sign-off.

Platform deep dives

Context on both ends of the pair

Oracle JD Edwards EnterpriseOne

Source

Strengths

Cross-platform deployment on Oracle Database, SQL Server, Windows, Unix, and Linux protects existing infrastructure investments.
Continuous delivery with six-month feature pack releases keeps the system modernised without requiring disruptive major-version upgrade projects.
Over 6,000 global customers across manufacturing, distribution, food and beverage, and real estate create a deep third-party consultant and integration ecosystem.
Advanced Pricing supports complex multi-level, multi-currency, and volume-sensitive pricing rules with formula-based and commodity-table pricing.
Modular per-module Named User Plus licensing lets organizations license only the functional areas they actively use.

Weaknesses

Named User Plus licensing scales per-user per-module, making total cost of ownership difficult to predict as organisations grow and adding users across multiple modules multiplies licence fees.
Customisation requires navigating the Object Management Workbench and the development tools layer, which has a steep learning curve compared to modern SaaS configuration approaches.
MRP cascading limitations mean overdue or held sales orders (status 999) do not automatically propagate demand signals down the bill of materials hierarchy.
Annual support fees at approximately 22% of perpetual licence cost represent a recurring expense that becomes a target for cost-reduction reviews during economic downturns.
Integration with modern cloud-native applications requires middleware or connector tooling, as JDE's native AIS REST API is functional but not as developer-friendly as contemporary API platforms.

Acumatica

Destination

Strengths

Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

Steep learning curve and complex initial setup create significant onboarding friction.
Report Designer is widely cited as unintuitive and difficult to use for non-developers.
Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

	Oracle JD Edwards EnterpriseOne Source	Acumatica Destination
Strengths	Cross-platform deployment on Oracle Database, SQL Server, Windows, Unix, and Linux protects existing infrastructure investments. Continuous delivery with six-month feature pack releases keeps the system modernised without requiring disruptive major-version upgrade projects. Over 6,000 global customers across manufacturing, distribution, food and beverage, and real estate create a deep third-party consultant and integration ecosystem. Advanced Pricing supports complex multi-level, multi-currency, and volume-sensitive pricing rules with formula-based and commodity-table pricing. Modular per-module Named User Plus licensing lets organizations license only the functional areas they actively use.	Unlimited named-user licensing eliminates per-seat cost scaling as teams grow. Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally. Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities. Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code. Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.
Weaknesses	Named User Plus licensing scales per-user per-module, making total cost of ownership difficult to predict as organisations grow and adding users across multiple modules multiplies licence fees. Customisation requires navigating the Object Management Workbench and the development tools layer, which has a steep learning curve compared to modern SaaS configuration approaches. MRP cascading limitations mean overdue or held sales orders (status 999) do not automatically propagate demand signals down the bill of materials hierarchy. Annual support fees at approximately 22% of perpetual licence cost represent a recurring expense that becomes a target for cost-reduction reviews during economic downturns. Integration with modern cloud-native applications requires middleware or connector tooling, as JDE's native AIS REST API is functional but not as developer-friendly as contemporary API platforms.	Steep learning curve and complex initial setup create significant onboarding friction. Report Designer is widely cited as unintuitive and difficult to use for non-developers. Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity. Implementation timelines frequently exceed initial estimates, especially for multi-module deployments. API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Oracle JD Edwards EnterpriseOne to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision