IBM i ERP Buyer's Guide

Separate the software question from the business question

ERP evaluations on IBM i often begin as a search for better software, but the deeper issue is usually whether current business processes still fit the company. Buyers should start by defining what is actually driving the project: poor visibility, weak integration, usability issues, reporting limits, unsupported code, acquisition growth, or pressure for cloud capabilities.

This framing matters because ERP change affects finance, operations, purchasing, inventory, production, customer service, and IT all at once. If the business problem is vague, the software search becomes vague too, and the loudest demo often wins for the wrong reasons.

Document what the current system really does

Most IBM i ERP environments carry years of custom fields, user exits, reports, scripts, interfaces, and manual workarounds that nobody has fully mapped in one place. Before comparing vendors or modernization paths, buyers should inventory the workflows leadership depends on, the customizations users rely on, and the processes that currently break down.

This step is tedious, but it is what separates an informed decision from a demo-driven one. It also helps the team distinguish between features that are truly strategic and local habits that developed simply because the current system made them necessary.

• Inventory active customizations and who depends on them
• List every system that currently integrates with the ERP
• Identify reporting and downstream spreadsheets that leadership quietly relies on

Define the future-state process goals before the vendor shortlist

Once the current state is documented, buyers should describe the target operating model they want to move toward. That includes how orders flow, how warehouse and production teams work, how finance closes, how approvals are routed, and how much self-service reporting the business expects.

This prevents the evaluation from becoming a search for a prettier version of the current ERP. The goal is not just to replicate old processes in a new interface. It is to determine which processes should be preserved, simplified, automated, or retired.

Weigh modernize, extend, and replace honestly

Full ERP replacement is rarely the only option, and it is often the riskiest one. Buyers should seriously compare three paths: modernize the existing environment, extend it with surrounding applications and integrations, or replace part or all of the ERP platform.

A credible evaluation treats those options equally long enough to test the assumptions behind each. The right answer depends on vendor roadmap health, internal support capacity, user tolerance for change, and whether the current data and process model is still an asset or has become a constraint.

• Modernize when the core transaction model is still sound but usability is weak
• Extend when adjacent functions like CRM, WMS, or analytics can solve the real gap
• Replace when the platform, support path, or process model is blocking the business

Interrogate data migration and integration risk early

ERP projects often succeed or fail on the unglamorous work of data cleanup, interface redesign, and reporting continuity. Buyers should identify which systems exchange data with the ERP today, what master data quality problems already exist, and which historical records must remain accessible after a change.

These questions belong in the early buying stage, not in post-selection implementation planning. A strong product fit can still become a bad project if migration and integration assumptions are unrealistic.

Plan the rollout as a business change program

ERP projects affect habits, roles, and accountability across the organization. Buyers should evaluate training burden, pilot sequencing, site or business-unit rollout order, and what executive sponsorship will be required to keep the project moving when tradeoffs appear.

The best ERP decision is the one the organization can actually absorb. A technically elegant platform that demands more change than the business can sustain is still the wrong choice.