By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
ERP implementation consulting is paid expertise for the build phase: planning, designing, configuring, integrating, migrating data and launching an ERP. A project that connects to many other systems needs seven roles covered: process lead, integration architect, data migration lead, security reviewer, developer, test lead and project manager. This guide maps each, then gives a 100-day plan.
What ERP consulting expertise do I need for complex system integration projects?
On an integration-heavy project, most problems show up where data passes from one system to another, so the expertise has to cover the data that moves between systems as well as each system. Check that the partner’s proposal names a person for each of these:
| Expertise | What this person owns on an integration-heavy project | Symptom when it is missing |
|---|---|---|
| Process lead (finance or operations) | The future-state process for every flow that crosses systems, and who signs it off | Design gaps found during user testing |
| Integration architect | The list of interfaces, the system of record for each piece of data, timing and direction, error handling and monitoring | Two systems each treated as the source of truth, and records that drift apart |
| Data migration lead | Field mapping, cleansing, mock loads and tie-outs to the old system | Opening balances that do not match, and loads that are repeated |
| Security and controls reviewer | Roles, service accounts for each integration and segregation of duties | An integration that stops when one person’s access changes |
| Developer or technical consultant | Scripts, connectors and any middleware configuration | Custom code with no documentation and no owner |
| Test lead | End-to-end scenarios that run across systems, with named testers | Each system tested alone, and failures found in production |
| Project or program manager | Governance, change control, dependencies on outside vendors | A date that no one can explain |
One person can fill more than one role on a small project. What matters is that someone is accountable for each line.
Define every interface before anyone builds it
For each connection, ask the partner to write down:
- the source and target systems and the direction of the data
- what triggers the transfer and how often it runs
- which system owns each field, so an update in one place has one destination
- the volume, and any limit on how much the target can accept at once
- the credentials used, who owns them and what happens when a person leaves
- what counts as a failure, who is alerted and how the failed record is retried
- the end-to-end test that proves it works
The last four are the ones projects skip. In our own resolved client requests, work that touched an integration or previously delivered custom code took roughly twice as long as a configuration change, so we pin down one owner and any outside dependency before scoping.
On a payroll integration for a commercial truck equipment company, our team took the work from the client’s first mapping of payroll items to GL accounts in June 2025 to final sandbox testing that October. The last step depended on a response from the payroll provider, and the work was re-scoped in August 2026 around a defined target data model, which is why we flag outside dependencies at the start of any payroll project.
Volume limits belong on the list too. A healthcare services company setting up a data-pipeline connector got a question from the connector’s support team about request limits on the NetSuite side. Our team checked the account’s web services concurrency settings and found no SuiteCloud Plus licenses, so the account was on its base limit. Oracle’s SuiteCloud Plus settings documentation describes how that license raises the concurrency limit for web services. Our guide to NetSuite integration service providers covers how to evaluate the firms that build these connections.
What does ERP implementation consulting include?
The services in a proposal usually fall into the groups below. Ask about the right-hand column, because it is where scope disputes start.
| Service | What it includes | Ask whether it is in scope |
|---|---|---|
| Planning and design | Requirements, process mapping, gap analysis and solution design | Workshops with every department, or finance only? |
| Configuration | Setup of modules, roles, workflows, forms and reports | Reports and dashboards, or only the base setup? |
| Integrations | Design, build and testing of each interface | Who builds it, and who owns it after go-live? |
| Data migration | Mapping, cleansing, mock loads and the final load | Who cleans the source data, and how many mock loads? |
| Testing | Test scripts, end-to-end scenarios, user acceptance testing | Who writes the scripts, and who runs them? |
| Training and change | Role-based training, super users, communication | How many sessions, and for how many roles? |
| Go-live and support | Cutover, hypercare and hand-off | For how long, and does it include the first close? |
Our NetSuite ERP implementation guide walks through the phases for a NetSuite project, and the NetSuite implementation cost guide shows how these items affect a quote.
What should a 100-day plan with an ERP implementation partner cover?
The first 100 days of a partner engagement set the scope, the design and the first data loads. Most projects continue well past day 100, so the plan below ends with testing under way and not with go-live.
| Days | Goal | The partner delivers | You decide |
|---|---|---|---|
| 1 to 15 | Mobilize | A project plan, a named team, a communication plan, a change-control process | Sponsor, project owner, protected hours for each department lead, and the target date for the first close |
| 16 to 40 | Define and design | Requirements ranked by priority, process maps, an interface list with owners, a solution design | Which gaps are closed by changing the process, by configuring or by building |
| 41 to 70 | Build and first loads | A configured test environment, a first mock data load with tie-outs, the first interfaces working with test data | Who supplies and confirms each data file, and what history moves |
| 71 to 100 | Test and prepare | End-to-end test scenarios run, a second mock load, a training plan by role, a draft cutover runbook | The go-live approach, the go or no-go criteria, and the support schedule for the first weeks |
Keep the target date for the first close in view throughout. A go-live date that moves month after month is a pattern we hear about. A building products company told us about its own NetSuite project: “We just kept pushing off our go live date month after month until eventually we just ripped the band-aid off.” By the time they called, the person who had led that implementation had left the company. Keep a decision log and written documentation from the first day so the reasons behind each design choice stay with the company.
Legacy systems: what to retire, keep, integrate or archive
An ERP project replaces some legacy systems and connects to others. List every system that holds business data and decide for each one:
- Retire: the ERP takes over its function, and its history is migrated or archived.
- Keep and integrate: it stays in service and exchanges data with the ERP through an interface you specify above.
- Archive: the system is shut down, but the history is kept in a form the auditors and the business can still query.
Decide the archive before the cutover, because the old system’s licenses and access usually end soon after. Plan a parallel period for finance processes if the controller wants to compare results in both systems before relying on the new one. A hybrid model, where your own staff run the system and specialists support complex areas, is a reasonable alternative to a full-time consulting team, provided that someone on your side owns the decisions.
Will the consultant tell you when not to build?
A good consultant gives you a reason when the answer to a request is “not yet”. A pest control company’s accountant spent 30 to 40 minutes a day building the daily deposit journal from its field-service system’s payment batches. Our team scoped two options, an upload script at about 10 to 12 hours or a direct API integration at more than 20, and put them next to a support allocation of about 15 hours a month. Because the daily time involved was small, we recommended holding the work until the client wanted to pursue it, and the ticket is on hold.
Ask a prospective partner for an example of a build it advised against, and what it recommended instead.
How to choose an ERP implementation partner
| Question | A useful answer |
|---|---|
| Who is the integration architect? | A named person who has written interface specifications like the one above |
| Which system owns each field, and who decides when two systems disagree? | A written system-of-record list, with a named decision owner |
| Whose credentials does each integration run under, and what happens when that person leaves? | A dedicated integration account with a named owner and a review schedule |
| How are failed records detected and retried? | Logging, an alert that reaches a named person and a defined retry or manual-fix step |
| How do you check volume and request limits before go-live? | Expected volumes per interface checked against the target system’s limits |
| How do you test across systems? | Scenarios that run through every connected system, in a sandbox, with named testers |
| What would you advise me not to build? | A specific example with the reasoning |
For a wider view of how to compare firms, see our guide to the ERP consulting firm.
How Nuage approaches ERP implementation consulting
On NetSuite projects, our team works through these steps. The details depend on the account.
- Name one owner and any outside dependency for each integration before scoping it. Integration and custom-code work took longer in our resolved requests.
- Define the target data model. The payroll integration was re-scoped around one in August 2026.
- Check volume and request limits at the start. On the data-pipeline connector, that meant checking the account’s web services concurrency.
- Scope two options and compare the hours. On the deposit journal request, an upload script and an API integration were put next to the client’s monthly support allocation.
- Hold work whose cost exceeds its benefit. The deposit journal request is on hold until the client wants to pursue it.
If you want a partner for the build, see how Nuage’s NetSuite experts work.
ERP implementation consulting FAQ
What does ERP implementation consulting include?
It includes planning and design, configuration, integrations, data migration, testing, training and change management, and go-live support. A proposal should say who does each one and for how many hours. The common scope disputes are about who cleans source data, who builds and owns each integration, how many mock loads are included, and whether first-close support is part of the price.
What expertise do I need for a complex ERP integration project?
You need a process lead, an integration architect, a data migration lead, a security and controls reviewer, a developer, a test lead and a project manager. Ask for a named person who defines each interface, its owner and how failures are detected.
What should a 100-day plan with an ERP implementation partner cover?
Cover mobilization in the first 15 days, requirements and design to day 40, build and a first mock data load to day 70, and end-to-end testing with a draft cutover runbook to day 100. At each point, agree what the partner delivers and what you decide. Keep the target date for the first close in view throughout.
How do I plan an ERP modernization from strategy through post-go-live?
Start with a business case built on your own measured numbers, then selection, then the implementation stages, then a support plan with a named owner. Agree on who is accountable at each stage. If one firm covers all of it, ask for the named team at each stage and the hand-off documentation.
Can one firm handle ERP implementation and change management?
A single contract can cover both. Ask that it name, for each stage, the lead, the deliverable and the acceptance test, and that the build team documents what it hands to the change team: the final role list, the process maps as built and the open issues from testing. Without that hand-off, training describes the design and not the system as built.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client work described in this article is our team’s.
