ERP Implementation: A Step-by-Step Plan for Business (2026)

What ERP implementation means, in plain words

ERP implementation is the project after which a company runs orders, inventory, purchasing, production and management finance in one system instead of several spreadsheets, apps and chat threads. It covers a review of your processes, choosing the system, configuring or building modules, migrating data, integrating with accounting, the bank and sales channels, testing, training people and support after go-live.

The gap between "we bought an ERP" and "we implemented an ERP" is huge. A licence can be paid for in a day. Implementing means reaching the point where every operation goes through the system, stock in it matches the shelf, and the owner sees sales, margin and debts without pulling reports together by hand. That road is where most ERP projects stumble, and it is what this guide is about.

If you are still deciding which ERP you need (ready-made, customised or custom-built), start with our guide to custom ERP development: it covers modules, ERP vs CRM vs accounting software and the popular systems. This guide is about rolling the chosen system out in your company without stopping the business.

Is your company ready for an ERP implementation

Needing an ERP is not the same as being ready to implement one. Readiness depends less on budget than on people, processes and data. Check yourself:

A low score is no reason to put the ERP off for years. Preparation (an owner for the project, written processes, a clean product list) takes a few weeks and then saves months of implementation. If you are not sure you need an ERP right now, see when a business needs an ERP, and when it is too early.

Implementation approaches: big bang or phased

There are four main approaches. The choice between them affects your risk more than the choice of the system itself.

Approach	How it works	Pros	Risks	Best for
Big bang	The whole company switches to the new system on one day	Short time living in two systems	If something goes wrong, the whole company stops	Small companies with simple processes
Phased by module	Orders and inventory first, then purchasing, production, finance	Each module delivers results; risk and budget stay under control	Longer overall timeline, temporary links to the old tools are needed	Most small and mid-size businesses
Phased by site	One warehouse, store or branch first, then the rest	Mistakes are caught at a small scale	For a while, sites work differently	Chains and companies with several warehouses or plants
Parallel run	For a few weeks operations are recorded in both the old and the new system, and the numbers are compared	Safe check on real data	Double work, so only for a limited time	Inventory, finance and anything where mistakes are expensive

We almost always recommend a phased rollout with a short parallel run at the start of each module. You pay for a module that already works, see results on your own data and can change the plan before the whole budget is spent.

ERP implementation team and roles

An ERP cannot be handed to a vendor and forgotten. It changes the work of every department, so the project stalls without people on your side. Good ERP project management starts with this minimum team:

Also name someone responsible for master data: products, customers, suppliers, prices and bills of materials. After go-live, this person decides whether duplicates and "the same product under three names" creep back into the system.

ERP implementation phases: a step-by-step plan

The ERP implementation life cycle usually runs through nine phases. In a phased rollout, phases 5 to 9 repeat for every module.

1. Goals and baseline

   Agree on 2-3 numbers that must change: stock accuracy, order processing time, shipping errors, days to close the month. Measure them now, or there will be nothing to compare with later.

2. Process review

   How orders, goods, money and documents move, where data diverges, what is done by hand and who owns what. The output is a map of processes "as is" and "to be".

3. Choosing the system and vendor

   A ready-made ERP, a hybrid with your accounting software or a custom system. Ask for a demo on your scenarios, not a slide deck: "show how this order goes from request to payment".

4. Design and prototype

   Modules, rollout order, roles, reports, a list of data and integrations. Users click through the main screens before configuration or code, because fixing a prototype is cheap and fixing a finished system is not.

5. First module 4-8 weeks

   Usually orders and inventory, because that is where losses are largest. Configuration or development with interim demos, not one big surprise at the end.

6. Data and integrations

   Clean and migrate master data, open orders and balances. Connect accounting, the bank, carriers, the website and marketplaces.

7. Testing and training

   End-to-end scenarios on real data: order, reservation, shipment, payment, documents in accounting. Role-based training and short instructions written for your processes.

8. Go-live

   Stock count, opening balances, a short parallel run and switching off the old way of working. The vendor stays close for the first days.

9. Stabilisation and next modules full system in 3-6 months

   Refine the module based on team feedback, compare numbers with the baseline, and only then start the next one: purchasing, production, finance.

How long ERP implementation takes

The timeline depends on the number of modules, warehouses and integrations, whether there is production, and how ready your data is. Reference points from our work:

Scenario	Typical timeline	What matters most
First module: orders and inventory	4-8 weeks	Number of warehouses, integrations and the state of the product list
Full system for a small or mid-size business	3-6 months, in phases	Number of modules, production, number of roles
Large company with several plants	A year or longer	Number of units, production complexity, reporting requirements

This is how the weeks of a first module usually look:

When	What we do	Result
Weeks 1-2	Process review, process map, goals and metrics	An agreed map and module plan
Week 3	Prototype of the main screens, list of data and integrations	Users see the system before configuration
Weeks 4-6	Configuration or development, master data migration, integrations	The module runs on test data
Week 7	End-to-end testing, role-based training	Key users have walked through their scenarios
Week 8	Stock count, opening balances, go-live	The team works in the new system

A module without production, with one warehouse and one or two integrations, lands closer to 4 weeks. Several warehouses, an accounting integration and marketplaces push it towards 8.

Data migration and integrations

A new ERP with dirty data repeats the old problems, only faster. Here is what usually moves over and where the surprises hide:

Data	What we migrate	What to watch
Products and services	Names, codes, units, attributes, barcodes	Duplicates and several names for one product, the most common problem
Customers and suppliers	Contacts, legal details and terms	One customer entered several times in different tools
Prices and discounts	Price lists, discounts, payment terms	Who changes them today and where, so that after go-live it happens only in the ERP
Bills of materials	Product structure and consumption rates	Whether they match how things are actually produced
Stock	Quantities and cost at the go-live date	Only after a stock count, not copied from accounting "as is"
Open documents	Open orders, receivables and payables	Reconcile with accounting before go-live

Past years of history usually stay in the old tool for reference; the ERP gets only what you work with now. That way migration takes days, not months.

List integrations before you start, because they are what people most often forget to budget for:

• Accounting software. Documents, customers, suppliers, stock. Tax reporting and, where your country requires it, e-invoicing usually stay in the accounting software.
• Bank. Statements and payments through the bank's API or open banking, so each payment finds its order by itself.
• Carriers. DHL, DPD, GLS, UPS or local carriers: labels and delivery statuses without manual entry.
• Sales channels. Your website and marketplaces such as Amazon: orders and stock in both directions.
• CRM. The customer and the order come from the CRM, and the fulfilment status goes back to the salesperson.

Keeping your accounting software: the hybrid approach

Many companies assume an ERP means replacing the accounting software. Often it does not. If bookkeeping is set up and works, it is usually better to keep it and let the ERP handle operations:

• Separate the standard from the unique. Keep accounting and tax as your software does them, and customise only what truly sets your business apart.
• Count the customisations. The fewer changes to a standard system, the easier and cheaper its updates. Write down and justify each one.
• Involve accounting from day one. They are first to notice if documents are generated wrongly, and they are the ones closing the month.
• Plan integrations up front. The CRM, website, carriers and bank belong in the ERP plan, not in a phase after go-live.

Accountants do not need retraining and statutory reporting is not put at risk. We described how this exchange works in practice in our article on integrating a CRM with BAS and 1C.

ERP implementation in manufacturing

Production is the hardest part of an ERP, because it brings in bills of materials, routings, raw materials and cost of goods. What to plan for:

• Bills of materials and consumption rates. Check them on real batches before go-live, or your cost of goods will be wrong from day one.
• Work orders for the shop floor. Who makes what and when is visible on a screen or tablet, not in the supervisor's notebook.
• Raw materials, semi-finished goods and scrap. Consumption is recorded as production happens, not "at the end of the month".
• Batches and expiry dates. For food and cosmetics this is the basis of traceability.
• Planning. From customer orders to raw material requirements and purchasing.
• Cost of goods. Actual cost per batch or order, not a monthly average.

Start with the end-to-end chain "order, production, shipment" for one product group, then expand. More on production modules in the ERP for manufacturing section of our development guide.

ERP implementation examples by industry

Where to start depends on where the company loses the most. Typical first modules:

Industry	Where to start	What you get first
Distribution and wholesale	Orders, inventory, customer receivables	Accurate stock and control of receivables
Manufacturing	Bills of materials, work orders, cost of goods	Actual cost and a production plan
Food production	Batches, expiry dates, raw materials	Traceability and fewer write-offs
E-commerce	Orders from the website and marketplaces, inventory, shipping	No more selling items you do not have
Services and projects	Projects, hours, expenses, invoices	Margin on every project
Logistics	Requests, trips, documents, invoices	Less manual paperwork

How to get your team to use the ERP

An ERP changes the work of people who have done things their own way for years, so resistance is normal. There is almost always a concrete reason behind it:

Who says what	What is behind it	What to do
Warehouse: "We have no time to enter everything"	Manual entry for every operation	Scanners or terminals; documents are created from the order automatically
Accounting: "Our accounting software works fine"	Fear of breaking the books and reporting	Bookkeeping stays where it is, the ERP sends documents there, and the accountant tests from day one
Sales: "A spreadsheet is faster"	Clumsy screens or unnecessary fields	Remove the clutter, make an order a few clicks, listen to feedback in the first weeks
Production: "We know what to do anyway"	No personal benefit	Show that there will be less rework and fewer stoppages due to missing materials
Managers: "I will build the report in Excel anyway"	Habit	The owner looks at reports only from the ERP and does not accept spreadsheets

Go-live day and the first 90 days

What to do on go-live day:

• run a stock count and enter opening balances;
• move open orders and balances and reconcile them with accounting;
• close the old tool for new documents, keeping it read-only;
• agree with the vendor on who is on call for the first days;
• set up one channel for questions and bugs so nothing gets lost.

How to measure ERP implementation success

Metric	What it shows	A good sign
Stock accuracy	Whether the system matches the shelf	Only isolated differences at a stock count
Order processing time	How long it takes from request to shipment	Shorter than at the baseline
Shipping errors	Wrong items, missing items, wrong addresses	They happen less often
Days to close the month	How long accounting and finance spend pulling numbers together	Fewer days, no manual consolidation
Double entry	How much data is typed into more than one tool	Every value is entered once
The owner's report	Where the numbers for decisions come from	One system, no spreadsheets

AI on top of an ERP

Once the ERP runs steadily, you can add AI on top: an agent sees products, stock and orders and takes over routine work people used to do.

AI works only as well as the data in the ERP is clean, so it comes after stabilisation, not in week one. More examples in AI agents in CRM and ERP, and a step-by-step plan in our AI implementation guide.

What drives the cost of ERP implementation

• Number of modules and processes. Orders and inventory are simpler than a full cycle with purchasing, production and finance.
• Production. Bills of materials, routings and cost of goods add the most work.
• Integrations. The bank and carriers connect quickly; accounting software and marketplaces take longer.
• Data. How much master data moves over and what state it is in.
• People. The number of users and roles, and how much training is needed.
• Licences. Ready-made ERPs charge licences or subscriptions per user, paid to the vendor separately. A custom system has no per-user licences.
• Support. How long the vendor stays with you after go-live.

We broke down what else shapes the budget in how much an ERP costs. In a phased rollout you know the scope and price of each phase before it starts, and we give an exact estimate for your processes after the intro call.

Why ERP implementations fail

• No owner on the company side. Nobody makes decisions, and the vendor waits weeks for answers.
• Automating chaos. Processes that did not work before were moved into the system as they were.
• Everything at once. A dozen modules with one go-live date, and any mistake stops the whole company.
• Dirty master data. Duplicate products and customers moved into the new system with all their problems.
• Forgotten integrations. After go-live it turns out website orders have to be re-typed by hand.
• Accounting left out. Documents are generated wrongly, and the books have to be fixed after the fact.
• Two systems forever. "For now, in Excel too" drags on for years.
• No training or support. The system goes live, people do not know how to use it and go back to old habits.
• No baseline. Six months later nobody can say whether things got better.

Checklist before you start

• 2-3 numbers the ERP should improve are written down and measured today
• A sponsor and a project lead on the company side are named
• Key users from every department are chosen
• Order, warehouse, purchasing and production processes are written down
• You have decided where bookkeeping stays
• There is a list of integrations: accounting, bank, carriers, website, marketplaces, CRM
• The product and customer lists are cleaned up
• The first module and a target go-live date are chosen
• A stock count before go-live is scheduled
• Time for training and support is set aside

Examples from our projects

To find out which module to start with and how long implementation will take for you, start with a conversation. The first call and the demo are free: you tell us how orders, goods and money move today, and we show a system on a similar process. More on the ERP development and BAS and 1C integration pages.

FAQ

What is ERP implementation?

It is the project of moving a company onto one system for orders, inventory, purchasing, production and finance: a process review, choosing the system, configuring or building modules, migrating data, integrating with accounting and sales channels, training people and support after go-live.

What are the phases of ERP implementation?

Goals and baseline, process review, choosing the system and vendor, design and prototype, the first module, data migration and integrations, testing and training, go-live, and stabilisation followed by the next modules.

How long does an ERP implementation take?

The first module, usually orders and inventory, goes live in 4-8 weeks. A full system for a small or mid-size business is built in phases over 3-6 months. Large companies with several plants take a year or longer.

Is it better to implement an ERP all at once or in phases?

For most companies, in phases: module by module, with a short parallel run at the start of each. Every phase delivers results, the risk of stopping the business is lower and the budget stays under control. A big bang suits only small companies with simple processes.

Do we have to replace our accounting software?

No. If bookkeeping works, it is usually better to keep it in QuickBooks, Xero, DATEV or BAS and run orders, inventory and production in an ERP connected to it through a data exchange. Accountants do not need retraining and reporting is not put at risk.

How do you migrate data to a new ERP?

Clean duplicate products and customers, move prices and bills of materials, run a stock count and enter balances at the go-live date, move open orders, receivables and payables, and reconcile them with accounting. Past years of history usually stay in the old tool for reference.

How much does ERP implementation cost?

It depends on the number of modules, whether there is production, integrations, the state of your data and the number of users. Licences for ready-made systems are paid separately. In a phased rollout the price of each phase is known before it starts, and an exact estimate can be given after a review of your processes.

How is ERP implementation different from ERP development?

Implementation is the whole project of launching a system in the company: processes, data, integrations, training and support. Development means building your own system or modules around your processes. It can be part of an implementation when ready-made ERPs fit only partly.