How to choose an ERP integrator in the UK

Choosing an ERP integrator is, for most small and mid-sized businesses, the most consequential decision in the whole project. The software matters, but the firm that configures it, migrates your data and trains your people matters more. A well-chosen integrator can make a modest product work beautifully; a poorly chosen one can make an excellent product fail.

This guide is written for managing directors, finance directors and IT leads in the UK who are about to approach integrators for the first time or who want to sharpen an existing shortlist. It sets out what the role covers, how an integrator differs from a software vendor, how to read certification claims, what to ask, what to watch for and how to structure the contract.

What an ERP integrator actually does

An ERP integrator is an independent firm that selects, implements and supports business software on behalf of its customers. You may also hear the terms ERP implementation partner, ERP consultancy, reseller or value-added reseller. The labels vary, and some firms are small specialist consultancies while others are large practices, but the underlying job is the same: to make the system fit your business rather than forcing your business to fit the system.

Seen from the customer side, the role breaks down into several distinct activities. A competent integrator should be able to explain how it handles each one.

Advice and scoping

The work begins before any software is configured. A good integrator helps you describe your processes, challenge your assumptions and decide what the system must do on day one and what can wait. This is where an ERP consultant earns their fee: by turning a vague ambition into a scope that can be priced, planned and tested. If you have not yet written down your needs, our ERP requirements template gives you a structure to work from before any conversation starts.

Configuration and set-up

Most of the project is configuration: chart of accounts, VAT codes, units of measure, price lists, approval workflows, warehouses, user roles and reporting. This is not glamorous, but it is where the system is made to reflect how you trade. Poor configuration is behind a surprising share of disappointing projects, because it is invisible until real transactions begin to flow.

Development and integration

Few businesses run on a standard system alone. You may need a connection to your online shop, your bank feeds, your payroll provider, a carrier, a customer portal or a specialist piece of equipment. Some processes may also need a bespoke extension. An integrator should be honest about when to configure, when to extend and when to leave a requirement alone, because every customisation has a lasting maintenance cost.

Data migration

Moving customers, suppliers, products, opening balances and open orders from old systems is a project in itself. The integrator should have a clear method for extracting, cleaning, mapping, loading and reconciling data, with rehearsals before go-live. Our guide to ERP migration explains the main risks in more detail.

Training and change support

Users adopt a system when they understand why it works the way it does. Good integrators train in the context of your own processes, not just in generic screens, and they help you appoint internal champions who will carry knowledge after the project team leaves.

Go-live and ongoing support

The weeks around go-live are intense. After that, you will need a support arrangement for questions, defects, upgrades and new requirements. Ask who answers the phone, how issues are logged and prioritised, and whether support is delivered by the same people who built your system.

ERP vendor versus ERP integrator

New buyers often assume that the software publisher will implement the product. In most cases it will not. Understanding the split of responsibilities helps you ask the right party the right question.

The practical consequence is that you buy two things, and each has its own risks. The software choice is covered in our guide to how to choose an ERP. The integrator choice, which is the subject of this page, determines whether the chosen software is used well.

Neutrality is worth thinking about too. Many integrators specialise in one or two products, which is a strength: depth in a single platform usually beats shallow breadth. But a firm that sells only one product will naturally recommend it. If you have not settled on software, either ask for an integrator that works with several, or run a short, independent selection phase first. This site is not tied to any vendor, and the integrators we introduce are independent firms that carry out the project themselves.

Reading certification and partner claims

Most vendors run partner programmes with several levels, and integrators like to display their badge. These credentials are a useful starting point, but they need interpretation.

• What a partner level usually signals. Training has been completed, a certain number of consultants have passed exams, and the firm meets the vendor's requirements for sales and support. It tells you the firm is recognised by the publisher.
• What it does not signal. It does not tell you that the firm understands your sector, that the people who passed the exams are the ones who will work on your project, or that customers are satisfied.
• Why the wording matters. Be wary of vague partnership claims that do not state a level. Ask which products and which levels apply, and which individuals hold which qualifications.

In short, treat certification as an entry ticket rather than a differentiator. Two firms at the same partner level can deliver very different projects, and a smaller firm with deep sector experience may outperform a larger one with a more impressive badge.

You should also check basic company hygiene: that the firm is properly registered at Companies House, that it carries adequate professional indemnity and cyber insurance, and that it handles personal data in line with UK data protection law. If the firm will touch sensitive systems, ask about its security practices and whether it holds recognised security accreditation such as Cyber Essentials.

Criteria for choosing an ERP integrator

Once you have a shortlist, compare firms on the same criteria. The following list reflects what tends to matter most in practice.

Sector and process experience

An integrator that has already worked with businesses like yours will anticipate your problems. A food manufacturer needs lot tracing and shelf-life logic; a wholesaler needs pricing tiers and stock allocation; a professional services firm needs time capture and project billing. Look at our pages on manufacturing ERP, wholesale and distribution ERP and professional services ERP to see how needs differ by sector, then ask each candidate how they would handle yours.

Product expertise

Does the firm know the product you are considering inside out, including its recent releases and its limits? Whether you are weighing Odoo, Microsoft Dynamics 365 Business Central or SAP Business One, a convincing integrator will describe not only what the product does well but where it would advise caution.

UK compliance knowledge

Your system must support UK VAT, Making Tax Digital obligations, statutory reporting, payroll links and the way HMRC expects records to be kept. The direction of travel on electronic invoicing is also worth discussing; our guide to ERP and e-invoicing covers the principles. An integrator that has never configured a UK ledger will learn at your expense.

Team depth and continuity

Ask how many consultants the firm has, how they are organised, and what happens if your lead consultant leaves mid-project. A very small team can be excellent and responsive, but it concentrates risk. A larger team offers cover but may rotate people. The right answer depends on your size and tolerance, but you should know which situation you are buying into.

Method and governance

Look for a recognisable approach: discovery, design, build, test, migrate, train, go live and stabilise. Ask how decisions are recorded, how changes are controlled, how progress is reported and how you will be involved in testing. Good methods are visible to the customer. Poor ones are a collection of promises.

References you can actually call

Ask for customers of a similar size and sector, and speak to them. Ask what went wrong as well as what went right, how the firm behaved when problems appeared, and whether they would hire it again. A reference list that is only ever positive and never reachable tells you little.

Commercial and cultural fit

You will work with these people for a long time. Pay attention to how they listen, whether they challenge you politely, and whether they talk to your finance and operations people as well as to the person who signed the cheque. Fit is not a soft factor; it often decides whether bad news is delivered early.

Questions to ask every candidate

Put the same questions to each firm so that the answers can be compared. The following are particularly revealing.

1. Which of our processes do you think will be hardest, and why?
2. Who exactly will work on our project, and may we meet them before signing?
3. Which parts of our requirements would you handle through configuration, and which through development?
4. How do you approach data migration, and what rehearsals do you run before go-live?
5. How do you handle changes to scope once the project has begun?
6. What do you expect from our own team, and how much of their time will it take?
7. What does support look like after go-live, and who delivers it?
8. Can you show us a project that went badly, and what you learned from it?
9. How will we get access to our system, documentation and data if we later choose to leave?
10. What would make you advise us not to proceed with this project, or not to choose this product?

The last question is a useful test. A trustworthy integrator can name circumstances in which the project is a poor idea. One that cannot is selling rather than advising.

Warning signs to watch for

Experience shows a handful of patterns that predict trouble. None is conclusive alone, but several together should make you pause.

• A fixed price offered with almost no discovery. A confident number on the basis of a single conversation usually means that risk has been pushed into later change requests.
• Everything is "standard". If every requirement is declared easy, the firm may not have understood it.
• Reluctance to name the team. Senior people sell, junior people deliver, and you only meet the latter after signing.
• No questions about your processes. A firm that does not probe your operations cannot configure them.
• Pressure to sign quickly. Deadlines tied to discounts or "limited availability" are a sales tactic, not a project reality.
• Vague answers on support. If post-go-live arrangements are an afterthought, you will feel it within weeks.
• Dismissive attitude to your staff. If the firm talks about users as an obstacle, adoption will suffer.
• No acknowledgement of your own responsibilities. Projects fail from both sides. An integrator that promises it will handle everything is either naive or not being honest.
• Disparaging every competitor. Confidence is welcome; contempt for the whole market is not.

Our guide to ERP project mistakes goes into the wider reasons projects fail, many of which begin at exactly this selection stage.

Contract and method: fixed price or time and materials

The commercial structure shapes behaviour throughout the project. There is no universally right choice, so it helps to understand the trade-offs.

In practice, many sensible projects blend the two. A fixed price for a well-understood foundation, such as finance, purchasing and sales, followed by time and materials for later enhancements, gives you certainty where it is possible and flexibility where it is needed. Our guide to ERP cost explains what typically drives the total, without pretending that a single number fits every business.

Terms worth negotiating

Whatever the pricing model, look carefully at the following points.

• Scope and exclusions. The statement of work should say what is in, what is out and what assumptions apply. Exclusions are as important as inclusions.
• Acceptance. Define how each deliverable is judged complete, who signs it off and what happens if it fails testing.
• Change control. Agree how changes are proposed, estimated and approved, so that nobody is surprised by an invoice.
• Named roles. Record the project manager and lead consultants, and what notice applies if they are replaced.
• Milestones and payment. Link payments to delivered outcomes rather than to elapsed time alone.
• Ownership and access. Confirm that you own your data and configuration, that you have administrator access to your system, and that all customisations are documented and, where appropriate, accessible to a successor.
• Support terms. Describe response expectations, hours of cover, escalation routes and how upgrades are handled.
• Liability and insurance. Review limits of liability in proportion to the project's importance, and confirm the insurance the firm holds.
• Exit. Plan for the possibility that the relationship ends, including handover of documentation and reasonable cooperation.

It is sensible to have the contract reviewed by someone with commercial experience. This is not a place to save effort, because the document governs a large and long-lived relationship.

How to run the selection process

A disciplined process reduces risk and makes the final comparison fair.

Define your needs before you speak to anyone

Document your processes, pain points, volumes, integrations and constraints. Decide which requirements are essential, which are desirable and which are simply preferences. This single step improves every conversation that follows, and it is the main protection against being sold a solution to a problem you do not have.

Build a short list

A small number of well-matched firms is more useful than a long list. Include firms that know the product you favour and have experience in your sector. If you are still deciding between products, see our comparisons such as Odoo versus Business Central and the best ERP for small business.

Ask for a structured response

Give each candidate the same brief and the same questions, and request a written proposal. Compare approach and understanding, not just price. A proposal that restates your needs accurately and highlights risks is usually more valuable than a glossy one that promises everything.

Run scripted demonstrations

Rather than allowing a generic demo, ask each firm to demonstrate a handful of your real scenarios. How an integrator copes with your data and your awkward cases reveals more than any brochure.

Check references and meet the team

Speak to customers, and meet the consultants who would work on your project. Ask them to explain a past problem and how it was resolved.

Decide on evidence

Score firms against your criteria, with input from finance, operations and IT. Resist the temptation to let price alone decide; the cheapest proposal is often the one with the most assumptions.

How we help

This site is a free matching service. You describe your project, and we introduce you to an independent ERP integrator suited to your sector, your size and the product you are considering. We are not affiliated with any software vendor, we do not carry out the implementation ourselves, and the integrator is responsible for delivering the project. You remain free to compare, to ask the questions above and to decline. To see how it works, read how the matching works, or compare products on our ERP software overview.

If you are a smaller organisation, our guide to ERP for small business explains what to expect from a lighter project, and the guide to ERP implementation describes the phases you will pass through once you have chosen a firm.

Summary

The integrator you choose shapes the outcome more than almost any other decision. Look for sector experience, product depth, UK compliance knowledge, a visible method, a team you can meet and references you can call. Treat certification as a starting point. Put the same questions to every candidate, notice the warning signs, and negotiate scope, change control, ownership and exit terms with care. Whether you opt for a fixed price, time and materials or a blend, make sure the arrangement rewards honesty and gives you control. A thoughtful selection takes some effort, but it costs far less than recovering from the wrong choice.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.