Prophet 21 Data Cleanup Checklist
Years of daily use leave any distribution ERP with duplicate customers, dead items, bad units of measure and forgotten price rules. Cleaning them before an upgrade, migration or reporting project saves you from carrying the mess forward. This checklist covers the data domains that matter most.
0 of 36 items complete
12 critical items still open - these are the highest-risk gaps.
1. Item master
2. Customers and ship-tos
3. Vendors and purchasing
4. Pricing and costs
5. Inventory and open documents
6. Governance
Critical items affect money, compliance or integrations. Fix those first. Keep a log of every mass change, and test bulk updates in a test copy before touching production.
Master data quality scan
Optional: share anonymized exports and we will outline duplicate, stale and inconsistent records for your team to review.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through each master data area, ticking items as you complete them. Start with the critical items because they affect money, tax or integrations. Define your thresholds up front, such as how long without activity makes an item or customer inactive. Run each check as a query or report against a test copy, review the results with the business owner, and only then make changes in production. Export the completed list as evidence for your project file.
Inactivate, do not delete
Deleting records usually breaks history and may not even be allowed once transactions exist. Marking items, customers and vendors inactive removes them from daily screens and lookups while keeping history intact for reporting and audit. Merging duplicates is different: it typically needs a controlled process, a backup, and a clear survivor record. Always keep a cross reference of the old and new identifiers so you can trace past documents.
Data that hurts most
Not all dirty data costs the same. Wrong units of measure and conversion factors misstate inventory and cost. Missing or expired tax exemption certificates create compliance exposure. Duplicate vendors with the same bank details can lead to duplicate payments. Overlapping price rules cause quotes that differ depending on who enters them. Prioritize those before cosmetic fixes like description typos.
- Units of measure and conversions
- Tax and exemption data
- Duplicate vendors and bank details
- Overlapping or expired price rules
- Negative on-hand quantities
Common mistakes
Running mass updates directly in production without a backup is the riskiest. Cleaning once and never again guarantees the problem returns, so put governance in place. Another mistake is cleaning without the business: only the salespeople know which customers are truly dead, and only buyers know which items are seasonal. Finally, do not forget downstream systems, since a fixed item number may still be wrong in your ecommerce or EDI mappings.
Frequently Asked Questions
How do I decide an item is obsolete?
Set a period with the business, such as 18 to 24 months with no sales, purchases or movement, and exclude seasonal and service parts. Flag candidates, have buyers review them, and inactivate rather than delete to preserve history.
Can I merge duplicate customers?
Often, but the process depends on your system and how much history exists. Plan it carefully, take a backup, choose a surviving record, move or reference open documents, and test in a copy first.
How often should I clean data?
Run light data quality checks monthly and a deeper review annually or before major projects. Governance, such as creation standards and restricted access, matters more than one-off cleanups.
Why clean before an upgrade?
Bad data slows testing, creates confusing results, and is expensive to move. Cleaning first reduces what you must test and migrate, and makes problems that remain easier to spot.
If you want duplicate and stale record candidates found automatically in your ERP data, we can build a read-only analysis that produces a review list for your data owners.
Related Tools
Prophet 21 Upgrade Checklist
A phase-by-phase checklist for upgrading Prophet 21: scope, test copy, customizations, integrations, cutover and the first week after go-live.
EpicorProphet 21 Pricing Library Design Worksheet
Plan each price page: who it applies to, which product group, the cost basis and multiplier, and the resulting gross margin, before anyone keys it into the system.
EpicorEclipse ERP Cycle Count Procedure Template
A fill-in cycle count procedure for a distribution branch: scope, ABC frequencies, tolerances, recount and adjustment approval, ready to print or share.
EpicorProphet 21 Inventory Replenishment Calculator
Work out order point, safety stock, EOQ and a max level for a distribution item, then compare against what your P21 replenishment parameters say.
More Epicor tools
See all- Prophet 21 Special Order Request Form Template
- Prophet 21 Vendor Return Authorization Request Template
- P21 Dead Stock Hold vs Liquidate Calculator
- P21 Price Matrix Multiplier and Margin Calculator
- Prophet 21 Inventory by Location SQL Generator
- Prophet 21 Open Order and Backorder SQL Generator
- Prophet 21 Order to Cash Go-Live Test Checklist
- Epicor Kinetic Job Status Reference
- Epicor BAQ Query Template Generator