What Buyers Ask About Your ERP

An ERP can connect important processes such as orders, inventory and invoicing. A useful review begins with what this particular

Business dashboard displayed on a desktop monitor

An ERP can connect important processes such as orders, inventory and invoicing. A useful review begins with what this particular system does, where it connects to other tools and who understands its behavior.

Buyers do not expect a perfect ERP. They expect answers. What does it do, what does it cost, what happens when it breaks, and what would it take to change it?

The short answer: prepare ERP facts in four areas: version and support, configuration and customization, operating effort and cost, and data quality. Add evidence for each answer and identify anything that has not been checked.

Here is what sits behind each question, and how to be ready.

Version, support status, and who keeps it alive

The first questions are mechanical. What ERP, what version, what modules, hosted where. Then the one that matters: is this version still supported by the vendor, and for how long?

Check the vendor’s current support information for the exact product and version. Save the source and date checked. If support status is unclear, ask the vendor or support partner rather than assuming a familiar product name means the installed version is supported.

Then come the people. Who administers the system? Who can change a report, add a field, restart a failed job? If the honest answer is one person, expect the follow-up: what happens when they leave? Have the answer ready, and if the real answer worries you, it worried you first.

Customization and institutional memory

Customizations and integrations can add testing and maintenance work. Their effect depends on how they were built and maintained. Document the important ones and check their compatibility before assuming an upgrade will be straightforward or impossible.

Be ready to describe what was customized and why. Customizations that encode a genuine business advantage are defensible. Customizations that exist because nobody knew the standard feature was there are technical debt, and buyers have seen both enough times to tell them apart.

The harder question is who understands the customizations. If the knowledge lives with one developer, one consultant, or one long-tenured employee, that is the actual diligence finding. Document the critical ones before you sell: what they do, why they exist, and what breaks without them.

The real cost picture

The license line in the budget is not the cost of the ERP. Buyers build the full number: licenses and subscriptions, annual maintenance, the infrastructure or cloud spend behind it, the integration tools and middleware, the consultants on retainer, and the share of the IT team’s time the system consumes.

Assemble the operating cost picture and label estimates. Include the period covered and the method used to allocate staff time. The purpose is a transparent technical baseline, not a recommendation about transaction pricing.

Data and what migration would take

A reviewer may ask how data could be exported or moved, even when no migration is planned. Treat this as a technical question to investigate, not a reason to start a replacement project.

That turns on data. How clean is the master data – customers, vendors, items, charts of accounts? How many years of history live in the system, and how much of it is consistent enough to move? Have there been prior mergers or system changes whose history was never fully integrated?

Record what you know about data quality and export options. If migration effort has not been assessed, say so. A working export is useful evidence, but it does not prove that a new system can use the data without mapping, cleanup and testing.

An ERP diligence prep sheet

System facts. Product, version, modules, hosting, support status, and the vendor’s published support timeline for your version.

People. Administrators, key users, and the consultants you depend on, with what happens if each leaves.

Customizations. What was changed from standard, why, and who understands each change.

True cost. Licenses, maintenance, infrastructure, integrations, consultants, and internal time.

Data. Master data quality, history depth, and any prior-system history that was never fully integrated.

Roadmap. Upgrades or replacements already planned, with status and budget.

Frequently asked questions

Will buyers make us replace the ERP as a condition of the deal?

There is no universal answer. A technology review can document support status, continuity risks and the work a change would require. It should not predict or prescribe transaction conditions.

Should we upgrade the ERP before selling?

Do not use a sale date alone to choose an upgrade. Assess support status, security, continuity, dependencies and delivery capacity with the responsible technical team. Separate necessary risk reduction from optional modernization and document the tradeoffs.

What if our ERP is heavily customized or partly homegrown?

Then the people, change history and documentation deserve close attention. Identify who can maintain the system, where the code or configuration is stored, and how changes are tested and recovered.

How much history should be ready to show?

Agree the technical evidence scope with the reviewers. Identify available transaction history, master data and prior-system records, including gaps. Do not infer a retention requirement from this article.

The ERP is a proxy for how the company runs

ERP records can help a reviewer understand system ownership, data quality and operating dependencies. Ready answers are useful when they are current, traceable and clear about what remains unknown.

CTO Input helps owners prepare ERP facts, operating costs and documentation for a technology review. If a sale is ahead of you, start by checking what is known, what needs verification and who owns the next step.

Search Leadership Insights

Type a keyword or question to scan our library of CEO-level articles and guides so you can movefaster on your next technology or security decision.

Request Personalized Insights

Share with us the decision, risk, or growth challenge you are facing, and we will use it to shape upcoming articles and, where possible, point you to existing resources that speak directly to your situation.