The short answer

A small-business ERP implementation usually runs through seven stages: map how you work today, decide what the system must do, choose the system, clean and move your data, set it up and connect your other tools, test it with real examples, then train your team and go live. The software is rarely the hard part. Getting the processes and the data right is.

1. Map how the business works today

Follow a typical order from enquiry to payment, and a typical purchase from supplier to shelf. Note every spreadsheet, form and email involved, and where things are retyped or go wrong. This becomes the brief for everything that follows.

2. Decide what the system must do

Turn that map into a short list of requirements, split into “must have” and “nice to have”. Include UK essentials such as VAT handling, and keeping digital records that work with Making Tax Digital for VAT if you are VAT-registered. Agree who in the business owns each area, such as sales, stock and finance.

3. Choose the system

Shortlist two or three options that cover your must-haves, then ask each to demonstrate your order and purchase examples, not a generic demo. Check how data gets in and out, which of your existing tools it connects to, who supports it in UK hours, and what happens to your data if you leave.

4. Clean and move your data

Customer, supplier and product records are usually spread across spreadsheets with duplicates and gaps. Clean them before moving them: one record per customer, consistent product codes, opening stock counted and checked. Decide how much history you really need to bring across; often open orders, balances and a year or two of history is enough.

5. Set it up and connect your tools

Configure the system to match your agreed processes, set user roles so people only see what they need, and connect the tools you are keeping, such as your website shop, email or reporting dashboards. Change the process before you customise the software: every customisation is something to maintain later.

6. Test with real examples

Run real scenarios end to end: a normal order, a part delivery, a return, a supplier credit, month-end. The people who will use the system day to day should do this testing, not only the project team. Fix what fails, then test again.

7. Train, go live and support

Train people on their own tasks rather than every screen. Pick a quiet period to go live, often the start of a month or quarter, and decide whether to switch everything at once or one area at a time. Keep extra support in place for the first weeks, when most questions come up.

Common reasons ERP projects struggle

  • Copying every old workaround into the new system.
  • Moving messy data and hoping to tidy it later.
  • Testing only the “happy path” orders.
  • No one in the business owning decisions, so the project stalls.
  • Going live in the busiest month of the year.

Getting help

New to ERP? Start with what an ERP system is and whether you need one. When you are ready, see ERP implementation for UK businesses. Every job gets a fixed, itemised quote after a free call, so you know the cost before any work starts.