1. Home
  2. Services
  3. ERP implementation services

ERP implementation services, from plan to support

An ERP is the software a company runs its sales, buying, stock and accounts in. Our ERP implementation services cover the whole project: consulting, discovery, process mapping, the build, data migration, training and ongoing support. You can buy one of these services or all of them. Our team has taken SAP, NetSuite, Odoo, Microsoft Dynamics, ERPNext, Xero, QuickBooks, Sage and custom ERPs live.

Go-lives on SAP, NetSuite, Odoo and moreEach service sold alone or end to endTraining and supportVendor rules read first
Go-live plan, distributor
Odoo 20, two warehouses
Plan
Hosting: Odoo.sh, since Odoo Online takes no custom modules Checked
Outside API: Custom plan in the quote Checked
Open orders move the weekend before go-live Planned
Key users trained on a copy with real items Planned
Emailed purchase orders drafted as sales orders once the ERP runs

Illustration with sample data.

What ERP implementation means

ERP implementation is the project that moves a company off spreadsheets and old systems and onto one ERP. Oracle NetSuite's guide says it usually takes 6 to 12 months, in six stages from planning to support.

We sell the work as seven services, each on its own or end to end. Some buyers need advice before they pick a system. Others have a live ERP and need only training, a data move or support. What each project includes is agreed in its contract.

The seven ERP implementation services we sell

Each one is sold on its own or as part of a full project. This list splits the work by what you can buy. The six project stages further down use Oracle's names instead. The scope of yours is agreed per project.

Scroll the table sideways to see every column.

ServiceWhat it usually coversWhat you usually get
ERP consultingWhich system, which plan and which hosting, and what each vendor's limits mean for how you work.A written advice note
DiscoveryHow many orders, bills, users and sites each team handles, and every system the ERP must talk to.A scope with counts and a list of links
Process mappingEach process drawn step by step: who does what, which record it touches and who approves it.Process maps your team checks and signs
Implementation
The build
Settings, custom fields, approvals, reports and the links to your other systems, built in a test copy first.A set-up system, tested with real orders
Data migrationItems, customers, suppliers, prices, opening balances and open orders, cleaned and checked.Loaded data with counts and totals matched to the old system
ERP trainingKey users first, then each role on its own tasks, on a copy loaded with your own data.Sessions per role and short written guides
Ongoing supportFixes, questions, small changes, and tests before each vendor update.A support plan whose terms the contract sets

The first three services can come before anyone buys software. Our ERP consulting page covers them in more depth: discovery, process mapping and choosing a system.

ERP systems our team has taken live

Our team has ERP go-lives on every system below. We name no clients on this site. Each vendor fact below comes from that vendor's own pages.

SAP

SAP's ERP family. For SAP Business One, release 10.0 is in mainstream maintenance until 31 December 2028, a date SAP says may change. SAP offers no extended maintenance for it. See SAP and AI agents.

NetSuite

Oracle's cloud ERP. Oracle upgrades every account twice a year, so each custom script needs a test before each upgrade. See NetSuite implementation.

Odoo

An ERP from Belgium with an open-source core. Odoo 20 came out in September 2026, with standard support planned to September 2029. See Odoo implementation.

Microsoft Dynamics

Microsoft's business systems. Business Central is its ERP for small and mid-sized firms. Changes to it are written in AL, Microsoft's language for it, and added as extensions on top of Microsoft's own objects.

ERPNext

An open-source ERP under the GPL-3.0 license. It is built on Frappe, a framework written in Python and JavaScript, which gives every record type an API.

Xero and QuickBooks

Both are accounting software. Xero's US home page sells it to small businesses. Intuit sells QuickBooks from a free plan up to enterprise plans. See QuickBooks and AI agents.

Sage

Sage's products include Sage Intacct and Sage 200. Sage 200's API reads and writes customers, suppliers, orders and accounts. See Sage and AI agents.

Custom ERPs

A system your company built for itself. We add modules to it, and APIs that let other software read and write its records. See custom ERP development.

The six stages of an ERP implementation

The stage names come from Oracle NetSuite's own guide. This is how the stages usually run. Each vendor rule named in a stage comes from that vendor's documents, read on 15 November 2026.

  1. Discovery and planning. We count the orders and bills each team handles, and the sites that will go live. Then the system, the plan and the hosting are settled. First check: Odoo Online takes no custom modules, and Odoo's outside API needs its Custom plan. Either rule can change the quote.
  2. Design. Each process is mapped to the system: who approves what, and which price list fits which customer. First check: in SAP Business One, an order sent in by outside software while approvals are on is saved as a draft, with error -2028. Approvals are designed around that.
  3. Development. Settings and custom fields come first. Reports and the links to your other systems come next. First check: NetSuite wants new links built on REST with OAuth 2.0 (a standard way to give software its own sign-in) from release 2026.1. Links built the older SOAP way stop working at release 2028.2.
  4. Testing. The data the first tasks need goes into a sandbox. That is a copy of the system where tests cannot touch live records. Then last month's real orders and supplier bills run through it, and each result is checked against what the old system produced.
  5. Deployment, also called go-live. Open orders move last, as the data migration steps below explain. Then your team switches over. NetSuite upgrades accounts twice a year, so go-live is usually planned away from your account's upgrade.
  6. Support and updates. Support work fixes the gaps the first weeks turn up. Then it plans each version move before the vendor's end date. The support section below lists those dates.

Data migration services: moving records into the new ERP

Data migration can be bought on its own. It moves the records the new ERP needs, then proves they arrived. It usually runs in five steps.

  1. Choose what moves. Items, customers, suppliers, prices, opening balances and open orders. Oracle's guide warns against moving all history, “lots of which is likely irrelevant.” Old history can stay in the old system or in an export file.
  2. Clean and map. Duplicate customers are merged and dead items retired. Each old field is matched to a field in the new ERP, with a written rule for any value that changes, such as a tax code.
  3. Load into a test copy. In NetSuite, CSV import is the route Oracle calls the most common for small to medium data sets. Odoo imports Excel or CSV files and warns that imports cannot be undone. So first loads go to a copy.
  4. Check counts and totals. Record counts, stock on hand and open balances are compared with the old system. Where a total differs, the lines behind it are checked one by one.
  5. Load open orders last. Oracle's guide says current transactions should move “immediately before going live.” Users switch over once the last load checks out.

Each target system has its own import tools. ERPNext's manual has a section on accounting migration, with a page on moving from QuickBooks. Our team's go-lives include QuickBooks, Xero and Sage as well as full ERPs, so we know the systems on each side of such a move.

ERP training: what it usually covers

ERP training is sold as part of a go-live or on its own, for a system that is already live. A plan usually follows the people who will use the system, one role at a time.

1

Key users first

One or two people per team learn the standard screens before anything is changed. Odoo's own method puts standard training in the kick-off, a phase it sizes at about 5% of project time.

2

Each role on its own tasks

Sales staff practice quotes and orders, and buyers practice purchase orders. The warehouse works through receipts, and finance through bills and payments. Each person uses a copy loaded with your own items and customers.

3

Short written guides

One guide per task, with screens from your own system. New staff can learn from them long after go-live.

4

The vendor's own courses

Odoo Learn lists 102 courses. Microsoft Learn has self-paced paths and classes with an instructor for Business Central. Oracle's SuiteAnswers adds NetSuite training videos.

Five courses from Odoo Learn, with the length and the number of steps Odoo lists for each, read 16 November 2026.

Scroll the table sideways to see every column.

Odoo Learn courseLengthSteps
Getting Started5 h 48 min31
Accounting and Invoicing10 h 4 min40
Inventory4 h 41 min38
MRP, Manufacturing and Shop Floor5 h 56 min42
Purchase1 h 30 min12

A vendor course teaches standard screens; training on your own setup teaches your approvals, your price lists and your reports. New staff, a new module or a new process each need training too. What a training plan covers is agreed per project.

ERP support after go-live

Ongoing ERP support covers what changes after go-live: your team, your processes and the vendor's software. Each contract sets what support covers and for how long.

Fixes in the first weeks

Real orders show gaps that tests missed, such as a missing approval step or a wrong tax code on one kind of sale.

Questions and small changes

A new price list or a new user role. Changes like these keep coming for as long as the business changes.

Tests before vendor updates

Custom scripts and links are tested before each upgrade. In NetSuite, that test runs in a Release Preview account.

Version moves and link changes

Each vendor sets end dates for versions and for old ways of connecting. Support work plans each move before the date.

Scroll the table sideways to see every column.

SystemWhat changesWhenSource
NetSuiteEvery account is upgraded to the new releaseTwice a year, in phasesOracle help, Release Delivery
NetSuiteSOAP integrations stop workingRelease 2028.2Oracle help, SOAP Removal Plans FAQ
OdooOld XML-RPC and JSON-RPC routes are removedOdoo 22, fall 2028Odoo 20 documentation, External API
Odoo 20Standard support, and with it security updates, endsSeptember 2029, plannedOdoo 20 documentation, support dates
SAP Business One 10.0Mainstream maintenance ends, with no extended maintenance31 December 2028, may changeSAP Support, Business One maintenance

How long ERP implementation takes, and what it costs

Published figures from a vendor and from firms that sell this work, with the date of each. They describe the market, not our prices.

Scroll the table sideways to see every column.

ProjectOne-time feeTimeSource
Any ERP
Vendor's view
Not given6 to 12 monthsOracle NetSuite guide, 9 Sep 2025
Odoo, 10 users$15,000 to $35,0006 to 10 weeksOctura Solutions, 18 Apr 2026
Odoo, 25 users$35,000 to $80,00010 to 14 weeksOctura Solutions, 18 Apr 2026
NetSuite, small firm with one entity$25,000 to $75,0008 to 12 weeksBroken Rubik, 5 Nov 2026; Concentrus agrees on the fee
NetSuite, mid-market with integrations$75,000 to $200,00012 to 16 weeksBroken Rubik, 5 Nov 2026
Custom ERP, first version$100,000 to $150,0006 to 12 monthsClockwise Software, 7 Aug 2026

More than a quarter go over budget. Panorama Consulting's 2026 ERP Report found that “more than a quarter of organizations exceeded their project budgets,” with extra technology needs as the leading cause.

Panorama Consulting press release, 4 Mar 2026, read 15 Nov 2026

Every source here sells ERP software or ERP services, so read them as interested parties. The license or subscription is billed on top of each fee. Panorama's full report is gated, so we quote only its public press release.

ERP work our team has done

Beyond the go-lives above, our team has built the work below.

RFQ and RFP automation, both sides

A system of several AI agents that handles RFQs (requests for a quote) and RFPs (requests for a proposal) end to end. A customer's request becomes a draft quote, and RFQs go out to suppliers. See RFQ and RFP automation.

On-demand ERP modules

A module built for one business problem and added to the ERP a company already runs. See how on-demand modules work.

Bookkeeping and order agents

The day's bills and receipts become draft entries for finance to approve. Emailed orders become draft sales orders, and the same pattern drafts purchase orders. See back-office jobs we automate.

Our team has also built AI agents in Salesforce and HubSpot, two CRMs (the systems that track customers and deals). Linking a CRM to the ERP is integration work. Our data and cloud work runs on AWS, Azure, Google Cloud and private VPS hosting (a rented private server), plus data work on Salesforce. See where custom software runs.

AI works on top of the ERP

The vendors' own documents keep the ERP as the record. AI reads it and drafts into it. Checked 15 November 2026.

NetSuite

Oracle: “Agents don't replace NetSuite records, reports, approval workflows, or your review of results.”

SAP Business One

The AI in the web client “cannot read, query, update, create, or delete any SAP Business One data.” Outside agents reach the data through the Service Layer, SAP's API.

Odoo 20

Outside software reaches Odoo through its JSON-2 API, which needs the Custom plan. Odoo suggests dedicated bot users for integrations.

ERPNext

Frappe, the framework under ERPNext, gives every record type a REST API without extra code.

Once the ERP runs, AI jobs can follow, such as the agents in the work section above. Each one drafts records in the ERP for a person to approve. See AI for ERP and AI agent development.

Tell us the ERP you run, or the one you are weighing

Name the system, the stage you need help with and the date you are working to. The first call is free.

Tell us the project

Questions about ERP implementation

What does implementing an ERP system involve?

It means taking an ERP from a signed contract to daily use. Someone has to set the system up for how you work, move your data in, test it with real orders and train your team. Oracle NetSuite's own guide calls it “the process of planning, configuring and deploying an ERP.” The guide splits the work into six stages, from discovery and planning to support. You can buy one piece of the work from us, or all of it.

How long does it take to implement a new ERP system?

Usually 6 to 12 months, says Oracle NetSuite's guide (published 9 September 2025). Small setups can be faster. Firms that sell the work publish 8 to 12 weeks for a small NetSuite company with one entity, and 6 to 10 weeks for a 10-user Odoo project. Each extra company, site, old system and link to another system adds time.

How much does ERP implementation cost?

For a small company, published fees run $15,000 to $35,000 for a 10-user Odoo project and $25,000 to $75,000 for NetSuite. Clockwise Software, a custom ERP builder, puts the first version of a new ERP at $100,000 to $150,000. These are one-time fees from firms that sell the work, read on 15 November 2026. The license or subscription is billed on top. They describe the market, not our prices.

Which ERP systems has your team taken live?

SAP, Oracle NetSuite, Odoo, Microsoft Dynamics, ERPNext, Xero, QuickBooks, Sage and custom ERPs. Those are our team's go-lives, and we name no clients on this site. We also work in two CRMs, the systems that track customers and deals: Salesforce and HubSpot. Our team has built AI agents in both.

Can we hire you for one service only, such as data migration or training?

Yes. Each of the seven services on this page is sold on its own or as part of a full project. An ERP that is already live may need only training for new staff. A project another firm started may need only its data move finished. What each piece of work includes is agreed per project.

What does ERP training include?

Usually it starts with key users and then moves to each role's own tasks. Key users learn the standard screens before anything changes, which is how Odoo's own method starts. Everyone else practices their own work on a copy of the system loaded with your items and customers, and short written guides stay behind for new staff. Vendor libraries add depth: Odoo Learn lists 102 courses, and Microsoft Learn has self-paced paths for Business Central. What a training plan covers is agreed per project.

What does ERP support cover after go-live?

Fixes, questions, small changes and the vendor's own updates. The first weeks show gaps in setup and in training. After that, the vendor keeps changing the system. NetSuite upgrades every account twice a year, and Odoo gives each major version three years of standard support. Support work tests custom code before each change and plans each version move. Each contract sets what support covers and for how long.

What do data migration services cover?

Moving the records your new ERP needs, then proving they arrived. That means items, customers, suppliers, prices, opening balances and open orders. The work runs in steps: choose what moves, clean it, map each field, load it into a test copy, compare counts and totals, then load open orders just before go-live. Oracle's guide warns against moving all your history.

Should we move all our old data into the new ERP?

Usually not. Oracle NetSuite's guide warns against moving all historical data, “lots of which is likely irrelevant.” Move what the first tasks need: items, customers, suppliers, prices and open orders. Keep the old history in the old system or in an export file. The guide also says current transactions should move “immediately before going live,” so open orders move last.

How often do ERP implementations fail?

We found no failure rate we could check at its source, but going over budget is common. Panorama Consulting's 2026 ERP Report found that more than a quarter of organizations went over their project budgets. The leading cause they named was extra technology (press release, 4 March 2026). Panorama's Chris Devault says organizations “often discover fatal misfits late in the project.” That is why we read the vendor's limits in stage 1.

What is an ERP implementation consultant?

The person who runs the project with your team. An ERP implementation consultant maps how you work onto the system, sets it up, plans the data move and the tests, and trains your staff. Our team also builds the links to your other systems, and AI agents that work in the ERP once it runs.

What are the six phases of ERP implementation?

Discovery and planning, design, development, testing, deployment, and support and updates. Those names come from Oracle NetSuite's own guide, and we use them for any ERP. Planning picks the system and the hosting. Design maps each process. Development sets up the system and its links. Testing runs real orders in a copy. Deployment moves open orders and switches users over. Support fixes what the first weeks turn up.

Will ERP be replaced by AI?

Not according to the vendors. Their own documents keep the ERP as the record. Oracle says its NetSuite agents “don't replace NetSuite records, reports, approval workflows, or your review of results.” SAP says the AI in the Business One web client “cannot read, query, update, create, or delete any SAP Business One data.” AI agents read ERP records and draft new ones for a person to approve.

Are you an Oracle, Odoo, SAP or Microsoft partner?

No. We are not a partner of Oracle, Odoo, SAP, Microsoft, Intuit, Xero, Sage or any other ERP vendor, and we do not sell licenses. You buy the software from the vendor or a reseller. We do the consulting, the setup, the data move, the links to your other systems, the training and the support.

Can you add AI to our ERP after it goes live?

Yes, and that is the order we suggest: get the ERP running, then add AI. An AI agent (software that does a task on its own) reads documents and drafts records, so it needs clean item and price data first. Our team has built a multi-agent system for RFQs and RFPs, plus agents for daily bookkeeping and for purchase and sales orders. An agent can save each draft for a person to approve.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.