What Internal Resources Are Needed for ERP Implementation
A successful ERP implementation doesn’t depend only on the software provider.
The business itself has an equally important role to play.
An implementation team can configure the system, guide the project and provide training, but it cannot make every operational decision on behalf of the customer. The people inside the business understand how orders move, how stock is handled, how purchasing decisions are made and where existing processes create problems.
That knowledge is essential.
A strong ERP implementation team brings together internal operational experience and external implementation expertise. The objective is not to involve everyone in every detail. It is to make sure the right people are available at the right stages of the project.
Why internal involvement matters
ERP affects more than one department.
It may connect sales, stock, purchasing, warehouse activity, invoicing, finance and reporting in one system. Decisions made during implementation can therefore affect several teams at once.
If internal users are not involved early enough, important requirements may only appear during testing or after go-live. That creates rework and can extend the implementation timeline.
Internal involvement also improves adoption.
People are more likely to support a new process when they understand why it is changing and have had an opportunity to contribute practical knowledge. That does not mean every preference should become a system requirement. It means the project should reflect how the business actually operates.
This is why ERP project planning needs input from the people who perform the work, not only senior management or IT.
Start with an internal project leader
The most important internal resource is usually the project leader – also called a Super User or Champion.
This person acts as the main connection between the business and the implementation team. They help organise internal input, coordinate decisions and keep the project moving when questions arise.
The project leader doesn’t necessarily need to be the CEO, CFO or most senior person in the organisation.
In many cases, the best choice is someone who:
- understands the business across several departments
- has enough authority to coordinate decisions
- can communicate clearly with management and users
- is comfortable learning new systems
- has sufficient time to support the project
- can keep track of actions and deadlines
Availability matters as much as seniority.
A highly experienced manager who cannot dedicate time to the project may be less effective than someone with strong operational knowledge and direct access to decision-makers.
The project leader also needs the support of senior management. If an issue requires a quick decision, they should not have to wait several weeks for approval.
Senior management must remain involved
ERP implementation cannot be delegated completely.
Senior management may not need to attend every workshop or testing session, but they should remain visible and engaged throughout the project.
Their responsibilities usually include:
- confirming project objectives
- approving scope and priorities
- allocating staff time
- resolving conflicts between departments
- making timely decisions
- reinforcing the importance of the project
This involvement matters because ERP projects often require changes to established ways of working.
If senior management treats the implementation as a side project, other employees are likely to do the same. If leaders communicate its importance and make time available, the project is more likely to maintain momentum.
Senior management should also agree what success looks like before the configuration begins.
The objective may be to improve stock visibility, reduce manual entry, simplify reporting or connect departments more effectively. Clear priorities help the implementation team make better decisions when several options are available.
Department representatives bring operational knowledge
The project leader cannot represent every business process alone.
Relevant departments should therefore nominate people who understand the work in detail. These representatives do not have to become full-time project members, but they need to be available for workshops, process reviews and testing.
Typical representatives may come from:
- finance
- purchasing
- sales and customer service
- stock control
- warehouse operations
- production or manufacturing
- dispatch and delivery
- management reporting
Their role is to explain how work happens now and identify what the new process needs to achieve.
For example, warehouse users may understand stock movements that are not visible to finance. Purchasing may know why certain supplier processes require exceptions. Customer service may understand where delays occur between order entry and fulfilment.
Bringing that knowledge together helps the business create a more connected operating model.
It also supports a clearer understanding of how an ERP system connects purchasing, stock, sales and reporting.
Internal teams need time, not just responsibility
One of the most common ERP project planning mistakes is assigning people to the project without adjusting their normal workload.
Employees are expected to attend workshops, prepare data, test processes and complete their usual responsibilities at the same time. When day-to-day work becomes busy, implementation tasks are pushed aside.
That creates delays.
Businesses should decide in advance how much time key users can realistically give to the project. Some phases require more involvement than others.
Planning workshops may need several hours from department representatives. Data preparation can require concentrated work over a longer period. Testing often needs users to complete full business scenarios rather than quickly checking individual screens.
The implementation timeline should recognise those demands.
A realistic plan is usually more effective than an ambitious schedule that assumes unlimited internal availability. The same principle applies across the wider ERP implementation timeline and project phases.
Data owners are essential
Data migration is not only a technical task.
The implementation team can provide import templates, tools and guidance, but the business must decide which information is accurate, relevant and ready to move.
That requires internal data owners.
A data owner is someone who understands a particular group of records and can confirm whether the information is correct. Different people may take responsibility for:
- customer accounts
- supplier records
- product and stock data
- pricing
- opening balances
- financial structures
- user accounts and permissions
This stage often takes longer than expected because old systems contain duplicates, inconsistent naming and inactive records.
Moving everything without review simply carries those problems into the new system.
Internal teams should therefore use implementation as an opportunity to improve data quality. Clean product catalogues, accurate supplier information and consistent customer records make the new system easier to trust from the beginning.
Process owners help prevent unclear decisions
A process owner is responsible for how a particular workflow should operate.
This is different from knowing how the process works today.
For example, several people may understand purchasing, but one person should have authority to confirm the future purchasing process. Without that clarity, implementation discussions can become circular.
One department may want one approach while another wants something different. The implementation team can explain the consequences of each option, but the business still needs to make the decision.
Clear process ownership helps resolve questions around:
- approval rules
- stock procedures
- purchasing controls
- customer account processes
- reporting structures
- user permissions
- exception handling
It also prevents the new ERP from reproducing every historical workaround.
Some existing processes may have developed because the old system could not support a better approach. ERP implementation is an opportunity to review those methods rather than automatically rebuilding them.
Key users are central to testing
Testing should not be left entirely to the project leader or implementation consultants.
The people who perform the work every day are often the best at identifying missing steps, unusual scenarios and practical issues.
Key users should test complete processes using realistic examples.
That might include:
- creating a purchase order
- receiving a partial delivery
- moving goods into stock
- entering a customer order
- allocating inventory
- dispatching products
- raising an invoice
- reviewing the financial result
Testing complete workflows helps confirm that departments remain connected throughout the process.
It also gives users practical experience before go-live.
Issues found during testing are usually easier to resolve than issues discovered after the business has started relying on the new system.
Training requires internal preparation
Training is not something that happens only at the end of implementation.
The business should identify early who needs training, what each group needs to learn and when sessions can take place.
Different roles require different knowledge.
Warehouse employees may need focused training on stock movements and picking. Finance teams need deeper knowledge of ledgers, reconciliation and reporting. Managers may need dashboards and approval processes rather than detailed transaction entry.
Training should be based on realistic workflows wherever possible.
It is also useful to identify internal key users who can support colleagues after go-live. These people do not replace ongoing external support, but they can answer simple process questions and help reinforce agreed ways of working.
Strong user preparation is particularly important because resistance to change and inadequate training are common ERP implementation challenges.
Communication is an internal responsibility
Even a technically strong implementation can struggle if communication is weak.
Employees need to understand:
- why the business is changing systems
- how the implementation may affect them
- what the expected benefits are
- when training will happen
- who they should contact with questions
- what is expected during testing and go-live
Silence creates uncertainty. And that kills a successful implementation.
People may assume the new system is being introduced to reduce roles or monitor activity more closely. Clear communication helps prevent those concerns from growing.
Updates do not need to be long or overly formal. Short, regular communication is often more effective than a large announcement followed by several months of silence.
The aim is to keep people informed and give them a clear route for raising practical concerns.
Internal IT support may be needed
The amount of internal IT involvement depends on the organisation and deployment model.
Some businesses have a dedicated IT team. Others rely on an external IT provider. Either way, technical support may be needed for areas such as:
- devices and workstations
- network access
- printers and scanners
- user accounts
- system permissions
- security requirements
- integrations
- hosting or local infrastructure
These requirements should be identified during planning rather than close to go-live.
A business does not necessarily need a large internal IT department to implement ERP successfully. It does need clarity about who will handle technical decisions and coordinate with the implementation team when required.
What a practical internal project structure looks like
The exact structure will vary, but many businesses need the following roles:
Executive sponsor
Provides senior support, approves priorities and resolves major decisions.
Internal project leader
Coordinates the project, manages actions and acts as the main internal contact.
Department representatives
Provide detailed operational knowledge from finance, sales, purchasing, stock and other relevant areas.
Process owners
Make decisions about how key workflows should operate.
Data owners
Review, clean and approve information for migration.
Key users
Test realistic processes and support adoption within their departments.
IT contact
Coordinates infrastructure, access, hardware, security and technical requirements.
One person may hold more than one role, particularly in a smaller organisation.
The important point is not the number of people involved. It is whether responsibilities are clear.
The business doesn’t need to manage everything alone
Internal involvement is essential, but the business should not be expected to design and deliver the full project without guidance.
Our role is to bring implementation experience, process knowledge, system expertise and structure to the project. The customer brings knowledge of its own operation, priorities and people.
The strongest implementations combine both.
We help translate business requirements into a workable ERP structure, challenge unnecessary complexity and guide teams through configuration, testing, training and go-live. Internal users help ensure those decisions reflect operational reality.
That partnership reduces the risk of building a system that looks correct in theory but does not work properly in day-to-day use.
Preparation matters more than team size
A business does not need a large project office to implement ERP successfully.
It needs the right people, enough time and clear responsibility.
A smaller, engaged team will often achieve more than a large group with unclear ownership. The project needs someone who can coordinate decisions, representatives who understand the work and senior managers who support the change.
When those resources are available, implementation becomes easier to plan and less likely to stall.
When responsibilities are unclear, even simple decisions can become delays.
The purpose of the internal team is not to manage software configuration. It is to make sure the new system reflects the business, that the data can be trusted and that users are ready to work confidently after go-live.
FAQ
1. Who should be part of an ERP implementation team?
An ERP implementation team should normally include an executive sponsor, internal project leader, department representatives, process owners, data owners, key users and an IT contact where required.
2. How much time should internal staff dedicate to ERP project planning?
The time required varies by project phase. Key users should be available for workshops, data preparation, testing and training, with workloads adjusted so implementation tasks are not continually postponed.
3. Does a business need an internal IT department for ERP implementation?
Not necessarily. However, it should have a clear internal or external IT contact who can coordinate infrastructure, security, access, devices and technical requirements.
4. What are the most important ERP internal resources?
The most important resources are an available project leader, engaged process owners, accurate data owners, realistic staff time and visible support from senior management.
