ERP data cleansing checklist: what to clean and what to keep before migration

What should an ERP data cleansing project leave alone?

A cleansing project should clean master data and leave transaction history intact. Duplicate vendors, dead customer records and inconsistent item codes are worth fixing; closed-year invoices, journal entries, purchase orders and the audit trail behind them are not worth deleting, because that history is the part of an ERP that shows how the business actually ran.

Most cleansing scopes are written as "inactive for N years, flag for deletion." That one rule quietly sweeps up both kinds of records. The checklist below separates them so the migration still gets a tidy chart of vendors and customers while the client keeps years of connected operating history. If the client is a US company with 50+ full-time employees at peak (contractors excluded), that history may also be what makes a SourceX data licensing introduction possible later.

Master data versus transaction history: where is the line?

Master data describes who and what the business deals with. Transaction history records what happened. Cleanse the first; archive the second.

The pre-purge checklist

Run these checks before anyone approves a deletion list. Each item is a question the controller or fractional CFO can answer from the ERP without opening a single record's contents.

Scope and ownership

• The cleansing scope document says which tables are cleaned and which are only migrated.
• A named owner (controller, CFO or IT lead) signs off on every deletion rule.
• The earliest transaction date in each module is written down, with the module name beside it.
• Nobody has scheduled deletion of closed-period data to shorten the migration.

Vendor and customer master cleanup

• Duplicate vendors are merged, not deleted, so historical invoices still point to one vendor ID.
• Inactive customers are flagged inactive rather than removed, so closed orders and credit memos keep their parent.
• A crosswalk of old and new IDs is saved before any merge.
• Free-text fields on master records are left alone unless the cleanup rule names them.

Transaction history and attachments

• Posted journals, subledger detail and closed projects are exported or archived before the old system is switched off.
• Attachments are listed by location and volume, even if they move later.
• Approval trails and exception notes are included in the archive plan.
• Anything under a retention hold from an auditor, lender or tax position is marked and excluded from deletion.

Metadata worth capturing

• Systems feeding the ERP (CRM, payroll, expense tool, ticketing) are listed, with the years each has been connected.
• The retention setting in each system is recorded.
• Someone confirms who can still run a full export from the legacy system after cutover.

What do the checklist results mean?

Count the unchecked boxes and act on the pattern, not just the total.

How does a clean master file connect to a data licensing conversation?

It does not change the client's rights, but it often reveals how long and how connected the records are. A controller who has just mapped the vendor and customer masters can say how many years the ERP covers and which other systems feed it, which are the first two questions in a fit screen.

The data asset register template turns those answers into a metadata-only sheet: system, owner, years held and retention, never record content. If the register shows many systems with long histories, the owner can decide whether to explore a license. Partners never export, upload or describe confidential records, and any redaction or de-identification rules are agreed with the company before work begins.

What to say when the cleansing scope is being drafted

If the project lead pushes back on keeping history, ask for the retention policy that supports deletion. If none exists, the default should be keep.

Common mistakes in ERP cleansing

When this is not worth raising

Skip the licensing angle if the company has fewer than 50 full-time employees at peak, if the ERP was implemented recently with little prior history, or if the records are mostly someone else's data held without consent. Also skip it if no one with authority over the records is reachable. In those cases, the checklist is still good cleansing practice.

Next step

Fractional CFOs and CAS leads who run migrations see systems and histories that most advisers never do. Read the fractional CFO partner overview, see how CAS growth at large firms shapes client conversations, and keep the monthly lender reporting package in view when retention holds apply. Before a handoff, the records handoff checklist and the chart of accounts redesign guide cover the same question from the other side. When a client looks like a fit, register as a partner.

The partner earns 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, up to $100,000 cumulative per referred company, and it becomes payable only after the buyer pays and SourceX receives its fee. Rewards are not guaranteed, and the reward is never deducted from what the company receives.