# Master Data Go-Live Cutover Readiness Checklist for ERP Projects > Source: https://netray.co/tools/master-data-go-live-cutover-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist of the master data tasks that must be complete before an ERP cutover, with critical items marked. ## Category erp-migration ## Audience - ERP project manager - Data migration lead - MDM analyst ## Tool **Kind:** checklist **Groups:** #### Scope and ownership **Items:** **Text:** Every master data object in scope is listed with a named business owner **Critical:** true **Text:** Cut-off rules define which records migrate (active, open, or transacted in the last N months) **Critical:** true A data steward is assigned to each object for the cutover window Decisions on obsolete and inactive records are signed off by the owner Legal and retention needs for archived data are agreed **Text:** The cutover calendar shows freeze dates for master data changes **Critical:** true #### Cleansing and standards **Items:** **Text:** Duplicate vendors, customers and items are identified and resolved **Critical:** true **Text:** Mandatory fields are populated in the source for all in-scope records **Critical:** true Country, currency and unit of measure values are mapped to controlled lists Part numbering and naming conventions are applied or crosswalked Addresses, tax IDs and bank details are validated Placeholder values (TBD, N/A) are removed or justified Item classification and product group assignments are reviewed #### Mapping and transformation **Items:** **Text:** Field-level mapping document exists for every object and is approved **Critical:** true **Text:** Value mapping tables (status, type, group codes) are signed off by owners **Critical:** true **Text:** Key mapping from old to new IDs is stored and preserved after go-live **Critical:** true Default values for new mandatory target fields are agreed Unit of measure conversions are tested for every item with more than one unit Transformation rules are documented and version controlled #### Load rehearsals and reconciliation **Items:** **Text:** At least two full mock loads completed with production-scale volumes **Critical:** true **Text:** Load duration measured and fits inside the cutover window **Critical:** true **Text:** Record counts reconcile between source, staging and target for every object **Critical:** true Error logs reviewed and each error type has a fix or an accepted exception Sample records are compared field by field against the source **Text:** BOMs and routings validated, including component and work center references **Critical:** true **Text:** Open balances such as inventory, open POs and open sales orders tie to the ledger **Critical:** true Load order respects dependencies (organisation, items, then BOMs, then transactions) #### Business validation **Items:** **Text:** Key users test real scenarios against migrated data in a test client **Critical:** true **Text:** Procure to pay and order to cash run end to end with migrated masters **Critical:** true Planning run produces plausible results with migrated item and BOM data Reports used for month end return expected figures **Text:** Data owners sign the data readiness certificate **Critical:** true #### Cutover and after go-live **Items:** **Text:** Master data freeze is communicated and enforced in the source system **Critical:** true Delta load procedure is defined for changes made after the last mock load Rollback plan exists and has been walked through Hypercare team covers master data defects for the first weeks **Text:** Governance process and request forms are live in the new ERP **Critical:** true Legacy key cross-reference is available to support and finance **Scoring Note:** Do not go live with any open critical item. Non-critical items may carry a documented risk acceptance signed by the data owner, but each one needs an owner and a date. ## Content **Intro:** Most ERP go-live problems that look like software defects are actually master data defects: a wrong unit of measure, a missing routing, a duplicate vendor paid twice. This checklist covers the master data work that must be finished before cutover, from scope and cleansing to rehearsals and sign-off. **Sections:** #### How to use the checklist **Body:** Work through the groups in order and tick items as they are completed with evidence, such as a signed mapping document or a reconciliation report. Critical items are the ones that, if missed, stop the business on day one, so treat any open critical item as a go-live blocker. Share the list with the data owners, because many items need their signature. Review it at each mock load and again 72 hours before cutover, and export the final status as the readiness record for the steering committee. #### Why rehearsals matter **Body:** A mock load is a full dress rehearsal of extraction, transformation and loading with production volumes. Two rehearsals is a practical minimum: the first finds mapping and data errors, the second proves that fixes work and that the load fits the window. Reconciliation after each load should compare record counts, control totals such as inventory value, and a sample of records field by field. Document every exception and its resolution, since the same pattern will recur in the final load. **Bullets:** - Load in dependency order, from organisational data to items to BOMs - Reconcile counts and values, not counts alone - Time every load step against the cutover window - Keep the old-to-new key map permanently #### Reading your score **Body:** Count completed items against the total, then check critical items separately. A project at 90 percent complete with three open critical items is not ready, while one at 85 percent with all critical items done and risks accepted may be. Use the score to focus the last two weeks: concentrate on mapping approval, reconciliation and business validation, which are the groups that most often slip. Repeat the score weekly so that trend and risk are visible. #### Common mistakes **Body:** Teams often start cleansing too late, treat the mock load as a technical test only, and let master data change freely in the source after the final extract. Another trap is skipping the old-to-new key cross-reference, which finance and support need for months. Do not rely on counts that match but values that do not, for example an inventory quantity that ties while the cost does not. And never skip business validation: users find problems that technical checks cannot. **Cta:** If you would like help profiling and reconciling master data for a cutover, our team can run read-only checks against your source and target systems. **Faq:** #### How many mock loads do I need? **Answer:** Two full mock loads is a practical minimum for most ERP projects, and three is common for complex or regulated environments. The first finds errors, the second confirms fixes, and the third rehearses the real cutover timing. #### Who signs off on master data? **Answer:** The business data owner for each object signs the readiness certificate, for example purchasing for vendors, sales for customers and engineering for BOMs. IT confirms technical reconciliation but does not own the business decision. #### Which records should I migrate? **Answer:** Migrate active records and those with open or recent transactions, usually defined by a cut-off such as 12 to 24 months of activity. Archive the rest. Agree the rule with owners and legal before cleansing begins. #### What is a delta load? **Answer:** A delta load transfers changes made to the source after the last full extract, such as new vendors or updated prices. It lets you freeze less of the business, but it must be rehearsed like any other load. ## Search terms master data cutover checklist, erp data migration go live checklist, data load rehearsal checklist, mock load reconciliation, master data readiness checklist, erp cutover data validation, data migration sign off checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json