How long does an ERP implementation take?
For a 10 to 50 person manufacturer on a cloud ERP, implementation usually takes four to twelve weeks from sign-up to running live orders, provided the data is reasonably clean and one person owns the project. Larger systems with custom development and several sites commonly take six months to a year. Most of the time goes into cleaning items and bills of materials, not into the software itself.
By Arunkumar V, CTO · 03 November 2026 · 2 min read
- ERP implementation timeline
- how long to implement ERP
- ERP go-live plan
- ERP rollout for small business
Where the weeks actually go
The table shows a typical sequence for a small shop on a cloud product. The phases overlap, and the data phase is the one that slips. A shop with a clean item master and current BOMs can be live in a month. A shop that first has to decide what its items are called and which BOM revision is real will take three months, and the software is not the reason.
| Phase | Typical time for a small shop |
|---|---|
| Agree scope, owner and go-live date | 1 week |
| Clean items, BOMs, customers, vendors, opening stock | 2 to 4 weeks |
| Configure and import | 1 to 2 weeks |
| Test with real orders | 1 to 2 weeks |
| Train each role and go live | 1 week |
| Settle and fix after go-live | 2 to 4 weeks |
What stretches the timeline
Projects slip for the same few reasons, and none of them are technical. The vendor can import a clean file in a day; it cannot decide for you whether a bracket and its painted version are one item or two.
- No single owner inside the shop with time set aside
- Trying to go live with every module on the same day
- Custom development before the standard version has been tried
- Waiting for a quiet period on the floor that never arrives
- Data cleaning handed to someone who does not know the parts
What shortens it
Go live with stock, purchasing and work orders first, and bring accounting across at a month end once the operational data is trusted. Use the vendor's CSV import rather than keying records by hand. Keep customisation to custom fields and simple workflow rules until you have run the standard process for a month. Hold a 30-minute check-in every week with the owner, the planner and the stores person, and close open questions in that meeting rather than by e-mail. Run the old spreadsheet in parallel for one month at most; longer than that and people never leave it.
How to plan an ERP implementation in eight weeks
- Step 1
Name one owner, fix a go-live date and list the three processes that go live first.
- Step 2
Export items, BOMs, customers and vendors from your spreadsheets and clean them in weeks one to three.
- Step 3
Configure numbering, units, warehouses, tax rates and roles in week four.
- Step 4
Import the clean data and run three real orders end to end in weeks five and six.
- Step 5
Train each role on its own screens in week seven, with a printed one-page guide per role.
- Step 6
Count stock, load opening balances and go live at the start of week eight.
Where ZMOS fits
ZMOS is a browser-based system with CSV import, a user guide with 54 step-by-step tasks and a six-month free period for startups and registered partners, so a 10 to 50 person sheet-metal, machining or fabrication shop can run the sequence above without a paid implementation partner. Stock, work orders and purchasing can go live first and the double-entry accounting can follow at a month end in the same workspace. It is not the right choice if you need a partner-led programme across several plants, or if your implementation depends on heavy custom development rather than custom fields and workflow rules.
People also ask
Short answers, each one complete on its own.
Related answers
- What should be on an ERP implementation checklist for a small manufacturer?
- Why do ERP implementations fail?
- How do I move from spreadsheets to an ERP?
- How does ERP data migration work for a small shop?
- All 54 answers
Inside ZMOS
Can a small shop implement an ERP in two weeks?
Only if the item master, BOMs and customer list are already clean and the shop goes live with one or two modules. Two weeks is enough for configuration and import; it is rarely enough for the data cleaning that comes before it.
Should we go live with everything at once?
No. Start with stock and work orders, which the floor needs daily, then purchasing, then accounting at a month end. A phased start lets people learn one set of screens at a time and keeps the accountant's year-end records clean.
When is the best time of year to go live?
The start of a month, after a physical stock count, and outside your busiest season. The start of a financial year is ideal for accounting but not required for stock and production, which can start any month.
How long should we run the old system in parallel?
One month at most. Parallel running doubles the data entry and people drift back to the old spreadsheet. Use the month to reconcile stock balances and open orders, then stop updating the old files.
See it on your own stock and jobs
ZMOS is free for six months for startups and registered partners, no card. Or ask an engineer anything on WhatsApp; we reply within 6 hours in working hours.