# SAP Data Migration Object Worksheet > Source: https://netray.co/tools/sap-data-migration-object-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable register of S/4HANA migration objects with record counts, cleansing progress, load method and mock load effort. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP data migration lead - SAP program manager - Master data manager ## Tool **Kind:** worksheet **Mode:** editable **Currency:** $ **Columns:** #### Migration object **Key:** object **Type:** text #### Source system or file **Key:** source **Type:** text #### Data owner **Key:** owner **Type:** text #### Records **Key:** records **Type:** number **Format:** integer #### Cleansed **Key:** cleansed **Type:** number **Format:** percent **Help:** Percent of records ready to load #### Load method **Key:** method **Type:** select **Options:** - Migration cockpit file - Migration cockpit staging - BAPI or IDoc - Custom program - Manual entry #### Planned mock loads **Key:** cycles **Type:** number **Format:** integer #### Hours per load **Key:** hours **Type:** number **Format:** decimal #### Total load hours **Key:** mock_hours **Type:** number **Expr:** cycles * hours **Format:** decimal #### Records ready **Key:** ready **Type:** number **Expr:** records * cleansed / 100 **Format:** integer **Rows:** **Object:** Business partner (customer) **Source:** ECC KNA1 **Owner:** Sales ops **Records:** 18500 **Cleansed:** 72 **Method:** Migration cockpit staging **Cycles:** 3 **Hours:** 2.5 **Object:** Business partner (supplier) **Source:** ECC LFA1 **Owner:** Procurement **Records:** 6200 **Cleansed:** 65 **Method:** Migration cockpit staging **Cycles:** 3 **Hours:** 1.5 **Object:** Material master **Source:** ECC MARA **Owner:** Engineering **Records:** 94000 **Cleansed:** 58 **Method:** Migration cockpit staging **Cycles:** 3 **Hours:** 6 **Object:** Bill of material **Source:** ECC STKO **Owner:** Engineering **Records:** 21000 **Cleansed:** 80 **Method:** Migration cockpit file **Cycles:** 2 **Hours:** 3 **Object:** Open purchase orders **Source:** ECC EKKO **Owner:** Procurement **Records:** 3400 **Cleansed:** 90 **Method:** Migration cockpit file **Cycles:** 3 **Hours:** 1 **Object:** GL balances **Source:** ECC FAGLFLEXT **Owner:** Finance **Records:** 12000 **Cleansed:** 95 **Method:** Migration cockpit file **Cycles:** 3 **Hours:** 0.5 **Object:** Fixed assets **Source:** ECC ANLA **Owner:** Finance **Records:** 8800 **Cleansed:** 70 **Method:** Migration cockpit file **Cycles:** 2 **Hours:** 2 **Totals:** #### Total records **Key:** records **Agg:** sum **Format:** integer #### Total mock load hours **Key:** mock_hours **Agg:** sum **Format:** decimal #### Total records ready **Key:** ready **Agg:** sum **Format:** integer **Summary:** #### Overall ready share **Key:** overall_ready **Expr:** if(gt(sum_records, 0), sum_ready / sum_records * 100, 0) **Format:** percent #### Average load hours per object **Key:** avg_cycle **Expr:** sum_mock_hours / count **Format:** decimal **Notes:** Sample volumes and source tables are illustrative. Replace with your own scope, and confirm available migration objects and load options for your S/4HANA release in the migration cockpit. Measure real load hours in the first mock load. ## Content **Intro:** In S/4HANA programs, data migration is usually where schedules are won or lost. This worksheet gives data migration leads a single register of every object to be moved, who owns it, how clean it is and how long each trial load takes. **Sections:** #### How to use the worksheet **Body:** List each migration object as a row, using the object names from the SAP S/4HANA migration cockpit where possible. Add the source, a named business data owner, the record count, and the share already cleansed. Choose the load method and enter how many mock loads you plan and how long a single load takes. The sheet calculates total load hours and the number of ready records, and the summary shows the overall ready percentage. Update it weekly and use it in the data workstream status meeting. **Bullets:** - One named business owner per object - Update cleansed percent weekly - Replace estimated hours with measured ones after mock 1 - Add dependencies in the object name or notes #### Why object-level tracking works **Body:** Migration objects have dependencies: business partners and materials must exist before open orders or inventory can load. Tracking per object exposes bottlenecks, such as a high-volume material master that takes six hours per load, which then drives cutover duration. Mock loads are rehearsals of the real thing; each one finds mapping errors, missing values and performance limits. Counting planned loads and hours makes the effort visible when the plan is under pressure. #### Reading the results **Body:** The overall ready share tells you how much of the data is load-quality today. Anything below about eighty percent for master data objects a few months before go-live is a warning. Total load hours indicate how much of the cutover window the loads will take, once you account for dependency order and parallel loading. Watch the objects with the largest record count and the lowest cleansed percentage: those are your critical path. #### Common mistakes **Body:** Programs often leave out secondary objects, such as open contracts, batch characteristics or customer-material info records, then discover them in testing. Another error is cleansing in the source without a governed rule set, so new duplicates appear. Finally, using only the first mock to estimate cutover timing is risky, since volumes and indexes change. Use the last full-volume rehearsal as the basis. **Cta:** If you need help profiling source data or automating validation reports for migration objects, we can talk through options. The worksheet works on its own. **Faq:** #### What are migration objects in SAP? **Answer:** A migration object is a predefined structure in the SAP S/4HANA migration cockpit that describes how a business entity, such as a material, a business partner or a purchase order, is mapped and loaded. Each has source structures, mapping rules and a target load method. #### How many mock loads should we plan? **Answer:** Three is a common baseline for major objects: an early functional mock, a full-volume mock, and a final dress rehearsal. High-risk objects such as materials and open financial items often need more. #### Does a brownfield conversion need this? **Answer:** Less so, because existing data is converted in place. You may still need to migrate or cleanse some objects, for example when consolidating systems or changing the chart of accounts. The worksheet is mainly useful for greenfield and selective data transitions. #### How do I measure cleansing percent? **Answer:** Define rules per object, such as mandatory fields complete and duplicates removed, and count the records that pass. Report the passing share. Agree the rule set with the data owner, so the number reflects load-quality, not opinion. ## Search terms sap data migration object list, s4hana migration cockpit object worksheet, sap data migration plan template excel, sap legacy data migration tracker, s4hana data migration scope template, sap data cleansing tracker --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json