Who owns your data before an ERP project?

The first import exposes the real problem

An ERP project may start with thousands of product and supplier records, then reveal duplicate names, inconsistent units, and uncertainty about who may change prices or deactivate a vendor. This is not merely an import-script problem.

Data reflects operating decisions. Confusion about its meaning or approval will move into the new system.

Data ownership is more than edit access

The person entering a record is not always its owner. An owner defines meaning, quality rules, approval for change, and exception handling. Sales might enter customer contacts while finance owns credit rules, with a steward accountable for the master customer record.

Without this distinction, teams maintain competing versions of the truth.

Prioritize the records that drive operations

Do not attempt to clean every spreadsheet at once. Start with customers, suppliers, items, units of measure, accounts, and payment methods. For each group identify an owner, authoritative source, mandatory fields, and change acceptance rules.

Photo source: Pexels.

• One authoritative record for each data type.
• An owner accountable for quality, not just entry.
• A defined path to merge duplicates and correct errors.

Related perspective: CRM Is Not a Contact Book: Design Real Sales Stages

Define a lightweight data-control model

Document critical field definitions, who creates and reviews each record, and who authorizes a change. Keep prior values or a change log where material, then test a representative subset before bulk import.

Agreement on data policy should precede import templates and integration mapping.

Hypothetical example: two units for one item

Imagine a product bought by the carton but sold by the piece. One spreadsheet treats cartons as the base unit and another uses pieces. Importing both without an approved conversion may distort inventory and prices.

Agree a canonical item definition, base unit, and conversion ratio with the data owner first. This example is hypothetical, not a client disclosure.

Define measurable data acceptance

Measure duplicate rate, required-field completeness, unit consistency, unresolved exceptions, and traceability of approval decisions.

• Every critical data group has a named owner.
• A sample import reconciles to the approved source.
• No critical exceptions remain without ownership.

A lightweight master-data ownership register

Start with products, customers, and suppliers. Assign each dataset a business owner, entry steward, and reviewer. Avoid allowing several departments to change reference fields without a documented rule.

Approve a sample, run a controlled test import, and log subsequent source changes before reloading data.

Establish the foundation before ERP configuration

ERP success depends on operating decisions and data governance before modules and migrations. Early ownership reduces rework and makes vendor selection more relevant to actual processes.

Digital Business Foundation can prepare documented ownership, controls and a cleaner baseline for specialist ERP implementation.

• Dataset — Business owner — Pre-import check
• Items and units — Operations / Inventory — Duplicates and conversions
• Customers — Sales / Finance — Unique records and required fields
• Suppliers — Procurement / Finance — Identity and commercial terms