# QAD Mock Conversion Load Log Worksheet > Source: https://netray.co/tools/qad-mock-conversion-load-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Editable log of data objects per mock conversion cycle with extracted, loaded and rejected counts and an automatic load percentage. ## Category erp-migration ## Erp QAD ## Audience - QAD migration lead - Data migration analyst - ERP project manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Data object **Key:** object **Type:** text #### Mock cycle **Key:** cycle **Type:** select **Options:** - Mock 1 - Mock 2 - Mock 3 - Dress rehearsal - Cutover #### Owner **Key:** owner **Type:** text #### Records extracted **Key:** extracted **Type:** number **Format:** integer #### Records loaded **Key:** loaded **Type:** number **Format:** integer #### Records rejected **Key:** rejected **Type:** number **Format:** integer #### Load % **Key:** load_pct **Type:** number **Expr:** if(gt(extracted,0), loaded / extracted * 100, 0) **Format:** percent #### Unexplained gap **Key:** unexplained **Type:** number **Expr:** extracted - loaded - rejected **Format:** integer **Help:** Should be zero before sign-off. #### Status **Key:** status **Type:** select **Options:** - Not started - In progress - Reconciled - Blocked **Rows:** **Object:** Item master **Cycle:** Mock 1 **Owner:** Planning lead **Extracted:** 18450 **Loaded:** 18102 **Rejected:** 340 **Status:** In progress **Object:** Customers **Cycle:** Mock 1 **Owner:** Sales ops **Extracted:** 2310 **Loaded:** 2310 **Rejected:** 0 **Status:** Reconciled **Object:** Suppliers **Cycle:** Mock 1 **Owner:** Purchasing **Extracted:** 1480 **Loaded:** 1462 **Rejected:** 18 **Status:** Reconciled **Object:** Product structures **Cycle:** Mock 1 **Owner:** Engineering **Extracted:** 41200 **Loaded:** 39800 **Rejected:** 1100 **Status:** In progress **Object:** Open purchase orders **Cycle:** Mock 1 **Owner:** Purchasing **Extracted:** 960 **Loaded:** 900 **Rejected:** 40 **Status:** Blocked **Object:** Open sales orders **Cycle:** Mock 1 **Owner:** Sales ops **Extracted:** 1275 **Loaded:** 1275 **Rejected:** 0 **Status:** Not started **Totals:** #### Total extracted **Key:** extracted **Agg:** sum **Format:** integer #### Total loaded **Key:** loaded **Agg:** sum **Format:** integer #### Total rejected **Key:** rejected **Agg:** sum **Format:** integer #### Total unexplained gap **Key:** unexplained **Agg:** sum **Format:** integer **Summary:** #### Overall load percentage **Key:** overall **Expr:** if(gt(sum_extracted,0), sum_loaded / sum_extracted * 100, 0) **Format:** percent **Primary:** true **Notes:** Use one row per object per cycle. Duplicate the object rows for each new mock cycle so you keep history. The unexplained gap column is the one to watch: every extracted record must be either loaded or rejected with a reason. ## Content **Intro:** A QAD migration lives or dies on data. This worksheet gives you one row per data object per mock cycle so the extracted, loaded and rejected counts always tie out. It works for QAD Enterprise Edition to Adaptive ERP moves and for any conversion into or out of QAD. **Sections:** #### How to use the log **Body:** List every conversion object you plan to load: item master, customers, suppliers, product structures, routings, open orders, inventory balances and GL balances. For each mock cycle enter the record count taken from the source extract, the count that loaded cleanly, and the count rejected by validation. The load percentage and unexplained gap compute automatically. Export to Excel and circulate it to the data owners after every mock so each person sees their own objects. #### Why the unexplained gap matters **Body:** Most reconciliation failures are not rejected records, they are records that silently disappeared: filtered by a join, dropped by a trailing space in a key, or skipped by a status filter. If extracted minus loaded minus rejected is not zero, someone must explain the difference before the object is signed off. Treat any non-zero gap as a defect, not a rounding issue. **Bullets:** - Compare counts and also control totals such as inventory quantity and value. - Keep the rejection reason list with the log, not in someone's email. - Re-run the same extract logic each cycle so counts are comparable. #### Reading the results across cycles **Body:** Load percentage should climb with every mock. A realistic pattern is a rough first mock, then most objects above the mid 90s by the second, and all objects reconciled by the dress rehearsal. If an object does not improve between mocks, the root cause is usually upstream data quality or a mapping rule, not the load program. Escalate blocked objects early because open orders and balances are loaded last and carry the cutover risk. #### Common mistakes **Body:** Teams track only counts and skip financial and quantity control totals, so a load that is complete by count can still be wrong by value. Others overwrite the previous cycle instead of keeping history, which hides regressions. A third mistake is letting the migration team own all objects: business owners should confirm the loaded data in the target system, not just the project team. **Cta:** If your conversion extracts come from a legacy QAD database, Netray can help build repeatable reconciliation queries so this log fills itself from real counts. **Faq:** #### Is this specific to QAD Adaptive ERP? **Answer:** No. The columns are generic to any ERP data conversion, so it works for QAD EE, QAD Adaptive ERP or any other target. The object names in the sample rows are typical manufacturing objects you would replace with your own list. #### How many mock cycles should I plan? **Answer:** Most manufacturers plan at least three mock loads plus a dress rehearsal before cutover. The right number depends on data volume, complexity and how clean the source data is. Add a cycle when an object is still not reconciled. #### What is an acceptable load percentage? **Answer:** The goal for cutover is every object fully reconciled, with any rejected record explained and either fixed or accepted by the business owner. Earlier mocks can be lower. There is no universal threshold, so agree it with your data owners. #### Can I export it to Excel? **Answer:** Yes. Use the export buttons on the tool to download the worksheet as Excel, CSV or PDF. The computed columns export with their values so recipients do not need formulas. ## Search terms qad data migration template, qad mock conversion log, qad data conversion tracker excel, qad data load reconciliation, erp mock load tracker, qad ee data cleansing checklist, qad migration cutover tracker --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json