Before you purge old ERP data: what to check first

Why do manufacturers purge old ERP data?#

Manufacturers purge old ERP data to speed up a slow system, cut storage or hosting costs, simplify a migration or reduce the personal data they hold. Each goal is legitimate, and each can usually be met by archiving rather than deleting.

The risk is that bulk data tools in many ERPs remove records as easily as they load them. A purge run against closed jobs or old transactions can take quote history, labor tickets and quality records with it, and those are the records that answer warranty claims, customer audits and questions nobody has thought to ask yet.

Archiving vs purging: which do you need?#

Archiving and purging both lighten the live ERP, but only archiving keeps the history available. Most manufacturers end up using both: archive aging history to a store that keeps keys and links intact, then purge from the archive only the records that have passed every check below.

What should the pre-purge checklist cover?#

The pre-purge checklist covers retention, holds, contracts, dependencies, value and documentation. Work through it by record type rather than by year, because a single year holds records with very different obligations.

Retention periods vary by record type, jurisdiction and contract. The next section lists some federal baselines that commonly apply to US manufacturers; state rules, customer contracts and quality certifications can add more, and your accountant and counsel set the final schedule.

• 1Retention: confirm tax, payroll, employment, environmental and quality retention requirements for each record type with your accountant and counsel.
• 2Legal hold: confirm with counsel that no litigation, claim, investigation or audit requires the records to be preserved.
• 3Customer terms: check purchase terms, quality agreements and supply agreements for record retention and audit rights.
• 4Quality system: check what your quality manual and certifications, such as ISO 9001 or AS9100, commit you to keep.
• 5Warranty and product liability: keep traceability for parts still in service or under warranty.
• 6Open dependencies: confirm no open orders, balances, lots or serial numbers reference the records.
• 7Value: assess whether the history is useful for analysis, internal AI projects or licensing before it disappears.
• 8Backups: decide under the same policy whether backups that contain the purged data are kept.
• 9Documentation: record what was purged, the criteria, the approver and the date.

Which federal retention rules commonly apply to manufacturing records?#

Several federal rules commonly set minimum retention periods for records that sit in or next to a manufacturer's ERP. They are baselines rather than a complete schedule, and longer periods may apply in particular situations.

Rev. Proc. 98-25 matters most for a purge, because it treats records held in a taxpayer's automated data processing system as records that must be kept. It also lets a taxpayer ask the IRS for a Record Retention Limitation Agreement that narrows which electronic records must be retained, which is worth raising with your tax adviser before a large deletion.

OSHA logs and exposure records usually sit in safety files rather than the ERP, but a purge of HR or employee tables can reach them, so include them in the review.

Which record types need the most care?#

The record types that need the most care are the ones that link a plan to an outcome, because they are both the hardest to rebuild and the most useful later. Records that hold mostly personal data, such as payroll, HR and some contact tables, are the strongest candidates for deletion once retention ends.

What makes an archive worth keeping?#

An archive is worth keeping when someone can still answer a question from it years later without the original ERP. That means preserving the database keys that tie quotes, orders, jobs and quality records together, plus a data dictionary that explains tables and fields in plain words.

Common formats include a read-only copy of the database, structured flat files such as CSV with a dictionary, or an archive module offered by the ERP vendor. Whichever you choose, index attached documents so they can be found by job or order number, restrict access to the people who need it, and test a restore before decommissioning anything.

Keep personal tables separate inside the archive. HR, payroll and contact records can then be deleted on their own schedule without touching production history.

Who should sign off on a purge?#

A purge should be signed off by the CFO or controller for financial records, the quality lead for quality records, counsel for holds and contracts, and IT for the technical method. A single IT ticket approving deletion by date range is a common gap in smaller companies, and it leaves nobody accountable for the decision.

Run the purge against a test copy first and compare record counts and key reports before and after. Confirm that the tool removes only the intended tables and does not cascade into linked records you meant to keep, such as lot history attached to a closed job.

Illustrative: an industrial pump maker pauses a purge#

Illustrative: a fictional maker of industrial pumps plans to purge closed jobs before a set cutoff year ahead of a hosting move. The IT director has the purge utility configured and the cutoff agreed with the controller.

During the checklist review, the quality manager points out that serial-number traceability on long-life pumps reaches back well past the cutoff, and counsel confirms that an open warranty dispute involves a pump built in one of the years marked for deletion. The company archives all closed jobs with their routers, labor and NCR links into a read-only database, places the disputed records under hold, and purges only payroll detail whose retention period has ended.

With the job history safe in the archive, the CFO asks for a metadata-only assessment of whether that history could support a licensing package.

How SourceX approaches pre-purge decisions#

SourceX does not advise on retention schedules or legal holds; those belong with your accountant and counsel. SourceX helps with the value line of the checklist through a metadata-only fit check on whether archived quotes, jobs, quality and maintenance records could form a licensable package, using the SourceX Enterprise Data Value Framework.

If a package proceeds, the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery) runs with your approval at each step, and large datasets stay in your own storage or ship on encrypted drives. Personal data you planned to delete is removed during preparation, not shipped.