ERP READINESS GUIDE

ERP readiness checklist: what to prepare before choosing software.

An ERP decision is a business operating-model decision as much as a software decision. Use this checklist to surface process, data, integration and adoption risks before demos turn into a vendor-led project.

Who this is for: business owners, finance and operations leaders, IT teams and transformation sponsors evaluating a first ERP, replacing a legacy platform or expanding an existing system.

Start the transformation navigator →   Run the free business automation assessment

1. Define the business outcomes first

Write down the business problem in plain language before building a feature list. Examples include reducing order-to-cash delays, improving inventory accuracy, consolidating financial reporting, making production planning more reliable or reducing duplicate entry between teams.

• Choose three to five measurable outcomes.
• Record the current baseline and where it came from.
• Set a target range and a date to review it.
• Name the person accountable for each outcome.

Avoid goals such as “modernise everything” unless they are tied to operational results. A software project can go live without improving the business process it was meant to fix.

2. Map the processes that cross team boundaries

Document how work actually moves, including exceptions and workarounds. Start with high-impact flows such as procure-to-pay, order-to-cash, record-to-report, plan-to-produce, hire-to-retire, service-to-resolution or project-to-invoice.

• Identify the trigger, owner, inputs, decisions, outputs and handoffs.
• Mark spreadsheets, email approvals, duplicate entry and manual rekeying.
• Record the most common exceptions, not only the ideal path.
• Separate policy problems from system limitations.

Do not automate a broken approval or unclear ownership model without first deciding whether the process itself should change.

3. Check master data and data ownership

ERP outcomes depend on consistent customer, supplier, product, item, chart-of-accounts, location and employee records. Assess quality before migration planning begins.

• Who owns each important data domain?
• Are duplicates, missing fields and conflicting codes common?
• Which system is authoritative for each record?
• Who will approve cleansing rules and reconcile migrated balances?

Plan representative test migrations and reconciliations. A successful file import is not proof that balances, units of measure, tax treatment, history or relationships are correct.

4. Inventory integrations and reporting needs

List the systems that must exchange information with the ERP: CRM, e-commerce, payroll, banking, warehouse tools, manufacturing systems, tax services, identity management, analytics and customer support. For each connection, note the data exchanged, frequency, owner, failure handling and business impact if it stops.

Also list the reports and operational decisions that depend on current data. Agree on definitions for measures such as revenue, margin, on-time delivery, inventory turns and overdue receivables. Different teams using different definitions can undermine trust in the new platform.

5. Make controls, compliance and security explicit

Identify applicable country, sector and contractual obligations with qualified internal or external advisers. Document retention, audit trails, approval controls, segregation of duties, privacy requirements, access roles, backup and recovery expectations, and any data residency constraints.

Ask vendors to demonstrate relevant controls in the proposed configuration and deployment model. Treat generic claims of “compliance” as a starting point for verification, not as evidence that your specific use case is covered.

6. Test the organisation's readiness to change

• Name an executive sponsor and business process owners.
• Reserve time from subject-matter experts for design, testing and training.
• Identify local workarounds and teams likely to be affected.
• Decide how decisions, scope changes and unresolved risks will be governed.
• Plan role-based training, support and post-launch ownership.

If people cannot participate in design and testing, reduce scope or adjust the timeline rather than assuming the implementation partner can make decisions on their behalf.

7. Build a realistic total-cost view

Compare more than subscription or licence price. Include implementation services, data cleansing and migration, integrations, extensions, testing, training, internal staff time, infrastructure, support, upgrades and the cost of running old and new systems in parallel.

Use low, expected and high scenarios. Record assumptions, confidence and the source for each estimate. Ask which costs recur annually and what happens if the programme takes longer or requires additional customisation.

8. Use a readiness gate before vendor selection

Before shortlisting vendors, confirm that the team can answer these questions:

• Are the target outcomes and baseline measures agreed?
• Are the highest-priority processes mapped, including exceptions?
• Are data owners and cleansing responsibilities named?
• Are required integrations and reports documented?
• Are compliance, security and deployment constraints recorded?
• Is there an accountable sponsor, a realistic team and a change plan?
• Is there a cost range with explicit assumptions and risks?

If several answers are “no”, the next best step may be a focused discovery or process-improvement phase—not an immediate software purchase. If the gaps are understood and owned, use them to shape vendor demonstrations and proof-of-concept scenarios.

Questions to ask during ERP demonstrations

• Can you demonstrate our highest-priority end-to-end process using realistic sample data?
• Which requirements are standard configuration, extensions, integrations or custom code?
• How are failed integrations detected, reconciled and retried?
• How would we test migration accuracy and prove financial reconciliation?
• What recurring costs and upgrade obligations apply to the proposed design?
• Can we speak with customers with a similar operating model and country footprint?

Next step: turn the checklist into a decision brief

Use the Transformation Navigator to organise your business context, current platform, priorities and constraints before evaluating options. You can also start with the free business automation assessment to identify repetitive work worth investigating. Outputs are directional discovery aids; validate requirements, costs, vendor claims and compliance needs with your team before committing.

Editorial note: This checklist is general educational information, not a vendor recommendation, legal opinion, implementation plan or guarantee of savings. The right sequence depends on your business model, risk profile and operating context.