Staged ERP implementation plan without stopping production

Why a staged ERP implementation plan is necessary

A plant that stops production for an ERP cut-over loses money every hour. Even a single day’s delay in a textile mill running 100 looms can cost £8,000 in lost output. Yet a big-bang switch—all departments live on the same Monday—risks data gaps, training overload and a week of chaos. A staged rollout keeps the plant running while each department moves to the new system in sequence, with checks at every step.

Fugen ERP is built for this approach. Its modules mirror the plant’s departments, so sales, stores, production and finance can go live independently. The software enforces a single stock ledger and posts accounting entries automatically, which means the old system can be retired one area at a time without creating parallel books.

Preparation: the 30-day checklist before the first cut-over

Before any module goes live, these tasks must be complete:

• The master data—customers, suppliers, materials, bills of material, routes and work centres—has been cleaned, deduplicated and loaded into a test instance of Fugen ERP.
• Every user has a named login, a role that matches their job, and has completed a two-hour hands-on session on the test system.
• The IT team has confirmed that the server, network and backup routines meet the implementation plan requirements.
• A printed quick-reference card for each role is taped to the relevant desk or machine terminal.
• A super-user from the vendor is on site or on a 30-minute video call for the first three days of each cut-over.

If any item is missing, the cut-over date for that department should be postponed. Rushing increases the risk of negative stock, unposted invoices or a production schedule that cannot be executed.

Department-by-department rollout schedule

The sequence below is typical for a textile or garment plant. Adjust the order only if a department’s data is a prerequisite for another—for example, stores must be live before production can issue materials.

Illustration: cost of a one-day delay in a textile plant

Assume a plant with 100 looms, 24-hour operation, 90% efficiency, 50 metres per loom-hour, and £1.80 contribution per metre. Daily contribution is:

100 looms × 24 hours × 0.90 × 50 metres × £1.80 = £194,400

If the ERP cut-over causes a one-day stoppage, the plant loses £194,400 in contribution. Even a half-day delay costs £97,200. These numbers are why a staged rollout is safer than a big-bang switch.

Keeping old and new systems in sync during cut-over

During the week each department goes live, both systems run in parallel. The rule is simple: the new system is the master for the live department; the old system remains master for every other department. Data must be copied daily to keep the books aligned.

• Sales orders entered in the new system must be manually keyed into the old system until the finance cut-over.
• Material issues posted in the new stores module must be recorded in the old stock ledger until stores is retired.
• Production output recorded in the new system must be entered into the old daily report until the old system is switched off.

Fugen ERP provides a daily reconciliation report that shows the differences between the two systems. The plant accountant should sign off this report before the next department goes live.

Checks to run before moving to the next department

Each department must pass these checks before the next one starts:

• The department head signs a one-page acceptance form stating that all data is complete and accurate.
• The plant accountant confirms that the trial balance for the new system matches the old system within the agreed tolerance.
• The IT team verifies that the backup from the new system restores cleanly on a test server.
• The vendor super-user conducts a 30-minute video call with the department team to answer any last questions.

If any check fails, the cut-over for the next department is postponed until the issue is resolved. No exceptions.

When software is not the answer

An ERP implementation plan cannot fix broken processes. If the plant still relies on paper travellers, manual stock counts or verbal production instructions, the new software will only automate the chaos. Before the rollout begins, these habits must be addressed:

• Every material issue must be recorded against a job or a cost centre, not against a generic “consumption” account.
• Every production shift must record actual output per machine, not an estimated average.
• Every quality inspection must capture defects by type and root cause, not just a pass/fail mark.

Fugen ERP includes activity tracking that shows who logged in, what they did and how long they spent on each screen. This data helps identify which processes need tightening before the software can deliver accurate reports.

What to do next week

Start with these steps:

• Assemble a cross-department team: sales, stores, production, quality, finance and IT.
• Run a one-day workshop to map the current process for each department and note where data is missing or duplicated.
• Clean the master data: remove duplicate customers, obsolete materials and inactive suppliers.
• Set up a test instance of Fugen ERP and load the cleaned data.
• Schedule the first hands-on training session for the sales team, as they will be the first to go live.

If the plant already has an ERP that is being replaced, run a parallel test for one week: enter the same data in both systems and compare the reports. The differences will show where the new system needs adjustment before the cut-over begins.