# ERP Master Data Load Order Reference for Data Migration Planning > Source: https://netray.co/tools/erp-master-data-load-order-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A vendor-neutral load sequence for ERP data migration: what has to exist before each object can be loaded. ## Category erp-migration ## Audience - Data migration lead - ERP project manager - Functional consultant ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Seq **Key:** seq **Type:** number #### Data object **Key:** object **Type:** text #### Type **Key:** type **Type:** text #### Must exist first **Key:** depends **Type:** text #### Why this order **Key:** why **Type:** text **Rows:** **Seq:** 1 **Object:** Company, legal entity, plant and site structure **Type:** Organization **Depends:** None **Why:** Every other object is assigned to an organizational unit. **Seq:** 2 **Object:** Currencies and exchange rates **Type:** Configuration **Depends:** Legal entities **Why:** Needed for pricing, open items and valuation. **Seq:** 3 **Object:** Units of measure and conversions **Type:** Configuration **Depends:** None **Why:** Items, BOMs and purchasing reference units. **Seq:** 4 **Object:** Chart of accounts **Type:** Finance **Depends:** Legal entities **Why:** Postings, open items and opening balances need accounts. **Seq:** 5 **Object:** Cost centers, departments and dimensions **Type:** Finance **Depends:** Chart of accounts **Why:** Employees, work centers and assets point to them. **Seq:** 6 **Object:** Payment terms and tax codes **Type:** Configuration **Depends:** Chart of accounts **Why:** Required on customers, vendors and open documents. **Seq:** 7 **Object:** Item or material master **Type:** Master **Depends:** Units of measure, plants **Why:** BOMs, routings, stock and orders all reference items. **Seq:** 8 **Object:** Customer master **Type:** Master **Depends:** Payment terms, tax codes **Why:** Sales orders, AR open items and pricing reference customers. **Seq:** 9 **Object:** Vendor or supplier master **Type:** Master **Depends:** Payment terms, tax codes **Why:** Purchase orders, AP open items and approved supplier lists. **Seq:** 10 **Object:** Work centers and resources **Type:** Master **Depends:** Cost centers, plants **Why:** Routings need capacity and rate data. **Seq:** 11 **Object:** Bills of material **Type:** Engineering **Depends:** Item master **Why:** Components must already exist as items. **Seq:** 12 **Object:** Routings and operations **Type:** Engineering **Depends:** Work centers, item master **Why:** Operations reference work centers and parent items. **Seq:** 13 **Object:** Approved vendor and purchasing info records **Type:** Master **Depends:** Vendors, items **Why:** Link sourcing prices to item and vendor pairs. **Seq:** 14 **Object:** Price lists and discount structures **Type:** Master **Depends:** Customers, items, currencies **Why:** Prices attach to item and customer groups. **Seq:** 15 **Object:** Inventory locations and bins **Type:** Configuration **Depends:** Plants **Why:** On-hand balances need locations to land in. **Seq:** 16 **Object:** Fixed assets register **Type:** Finance **Depends:** Chart of accounts, cost centers **Why:** Assets need accounts and responsible cost centers. **Seq:** 17 **Object:** Opening inventory balances **Type:** Balance **Depends:** Items, locations **Why:** Load at cutover after a physical count or freeze. **Seq:** 18 **Object:** Open purchase orders **Type:** Transaction **Depends:** Vendors, items, tax codes **Why:** Receipts after go-live must match to an existing PO. **Seq:** 19 **Object:** Open sales orders **Type:** Transaction **Depends:** Customers, items, prices **Why:** Shipments and invoices after go-live need an order. **Seq:** 20 **Object:** Open production or work orders **Type:** Transaction **Depends:** BOMs, routings, items **Why:** Shop floor reporting continues against live orders. **Seq:** 21 **Object:** Open AR invoices **Type:** Open item **Depends:** Customers, chart of accounts **Why:** Cash application needs open items. **Seq:** 22 **Object:** Open AP invoices **Type:** Open item **Depends:** Vendors, chart of accounts **Why:** Payment runs after go-live need them. **Seq:** 23 **Object:** GL opening balances **Type:** Balance **Depends:** Chart of accounts, all subledger loads **Why:** Load last so control accounts reconcile to subledgers. **Seq:** 24 **Object:** Open quality records and lot or serial history **Type:** Transaction **Depends:** Items, locations **Why:** Traceability must carry across the cutover. **Notes:** This is a vendor-neutral sequence. Your ERP may split or reorder objects, so confirm against the object dependency documentation for your product. ## Content **Intro:** Data loads fail most often because something was loaded before the thing it depends on. This reference lists the usual order for a manufacturing ERP migration so you can sequence your load plan and rehearsal runs without discovering dependencies at cutover. **Sections:** #### How to use it **Body:** Filter by type to see only master data, open items or balances. Copy the rows into your migration tracker and add columns for load tool, owner, record count and mock-load result. Keep sequence numbers as your load order in the runbook, and treat any object missing from your own list as a question to answer before the first trial load. #### Why the order matters **Body:** Master data forms a dependency tree. Organization and configuration come first, then finance structures, then item, customer and vendor masters, then engineering data, and only then transactions and balances. Opening balances sit last because they must reconcile to the subledgers you just loaded. **Bullets:** - Configuration before master data - Items before BOMs, routings and stock - Open items before GL control account balances - Cutover-dependent balances loaded after a freeze #### Worked example **Body:** A plant has 12,000 items and 400 open production orders. The items load in a few hours, but production orders fail on first trial because routings reference work centers that were never loaded. Moving work centers to run before routings, and loading orders only after routings pass validation, clears the errors. Document the corrected order in the runbook so the mock cutover repeats it exactly. #### Common mistakes **Body:** Teams often load GL balances too early, then reload subledgers and break reconciliation. Others forget that inactive items can still be referenced by history. Plan an explicit decision about what history to migrate, and rehearse the full sequence at least twice before the real cutover. **Cta:** If you want help turning this into a timed load plan for your ERP, Netray can review the sequence and the extraction queries. **Faq:** #### Is this sequence the same for every ERP? **Answer:** The dependency logic is common, but objects differ. Some systems combine customer and vendor into a business partner, or split item and inventory records. Use the order as a starting point and adjust to your product. #### Should open transactions be migrated at all? **Answer:** Usually open orders and open items are migrated because the business continues working on them. Closed history is more often archived or kept in the legacy system, with only summary balances loaded. #### How many mock loads should we run? **Answer:** Two or three full rehearsals is a typical target: one to find dependency errors, one to prove timings and reconciliation, and a final dress rehearsal with the cutover team. #### Why are GL balances last? **Answer:** Subledger control accounts must match the sum of open items and stock values. Loading subledgers first lets you confirm totals before the final GL balance posting. ## Search terms ERP data migration load sequence, ERP master data load order, data migration dependencies ERP, order of data load ERP, ERP conversion sequence, data migration plan order, master data migration checklist order --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json