
Walk into the office of many established Indian manufacturers — in Peenya, Ambattur, Chakan, Pimpri-Chinchwad, Rajkot, Ludhiana, Faridabad or Coimbatore — and you will find software that has run the business for fifteen or twenty years. It was written in Visual Basic 6, MS Access or FoxPro, often by a local developer or a family member, and it knows the company's processes intimately. People who use it every day can enter an order or a receipt in seconds with keyboard shortcuts.
It is also, increasingly, a risk. It runs only on the office network. It needs an old version of Windows. The person who wrote it may have moved on. It cannot show the managing director what is happening at the second or third plant. And every new requirement — a new report, a new approval, a new plant — is harder to add than the last. This guide explains how to replace such a system without losing what made it valuable, based on our experience replacing a VB application for a hydraulic equipment manufacturer with 11 factories.
Off-the-shelf ERP or a custom replacement?
When an old system reaches its limits, the first suggestion is often to buy a packaged ERP. For some companies that is right. But manufacturers with long-established, specific processes — blanket orders with complex consumption rules, product-specific testing, job work across plants, customer-specific documents — often find that a packaged ERP forces them to change how they work, or needs extensive customisation that is expensive to maintain and upgrade.
A custom replacement takes the opposite approach: it starts from how the business actually works, keeps what the old system did well, and adds what it never did. It also lets you keep the working style your team is fast with, such as keyboard-driven desktop screens. The right choice depends on how standard your processes are, how much they differentiate you, and how much change your team can absorb. A good supplier should help you weigh this honestly rather than push one answer.
Signs it is time to replace
- It works only inside the building. Owners and managers can't see orders, stock or production when they are at another plant, a customer or travelling.
- Several plants, several copies. Each plant has its own copy, and data is consolidated by email and Excel.
- Key-person risk. One person, inside or outside the company, understands the code.
- Old platforms. It needs an old Windows version, old database drivers or 32-bit components that are increasingly hard to support.
- Slow and fragile. Reports take minutes, the database grows corrupt from time to time, and backups are uncertain.
- Weak access control. Everyone can see everything, or permissions are all-or-nothing.
- Workarounds everywhere. New processes live in Excel sheets and WhatsApp groups because the software can't be changed.
Treat the old system as a specification
The biggest mistake in a replacement project is to throw away what the old system knows. Over the years it has absorbed hundreds of business rules: how order numbers are formed, which customers get which documents, how blanket orders are consumed, which test is required for which product, how stock is valued. Many of these rules are documented nowhere else.
A good replacement starts by studying the old application screen by screen and report by report with the people who use it, and asking for each one: what is this for, who uses it, what would happen if it disappeared? The answers become the specification. Some features are carried over almost unchanged, some are improved, and some turn out to be no longer needed.
Cloud plus desktop: the best of both
Moving to the cloud doesn't have to mean forcing everyone into a browser. A practical architecture for many manufacturers is:
- One central cloud database and application for all plants, accessible from anywhere with proper security.
- A web application for management, sales, purchase and occasional users.
- A desktop application for high-volume users — order entry, stores, dispatch, accounts — with dense, keyboard-driven screens and familiar shortcut keys.
- Mobile or tablet screens for the shop floor, stores and quality, where useful.
Everyone works on the same live data. Experienced users keep their speed, and managers finally get a single view of the business.
What to build — and what to improve
A replacement is a chance to fix what the old system never did well. Typical improvements for Indian manufacturers include:
- Order to delivery in one flow: enquiry, quotation, sales order, production, testing, QA, dispatch and invoicing linked.
- Blanket orders and schedules: long-term agreements with call-offs, balances and rate revisions, common with OEM customers.
- Material management: requirements, availability checks before release, and shortage alerts against the orders they affect.
- Multi-plant stores: stock by plant and location, inter-plant transfers and job work.
- Quality and testing records linked to orders and serial numbers.
- Roles and permissions by module, action and plant, with an audit trail.
- A management dashboard showing orders, progress, shortages and events across all plants.
- Statutory documents and data needed for GST and dispatch, produced from the system and connected to accounting software where required.
Performance: lighter is faster
Old applications often grew slow over years of additions: queries that scan entire tables, reports that load everything into memory, screens that open dozens of connections. A rebuild with lean code, proper database indexes and efficient queries can make everyday screens and reports noticeably faster — even though the data now travels over the internet. Performance should be a requirement from the start, tested with realistic data volumes, not an afterthought.
Moving the data
Data migration needs care:
- Inventory the data. Which tables, files and databases exist, and what do they mean?
- Decide what to move. Masters (customers, items, BOMs, suppliers) and open transactions almost always; full history sometimes, or kept in an archive for reference.
- Clean as you go. Duplicate customers, inconsistent item codes and orphan records are normal; fix them during migration rather than carrying them forward.
- Rehearse. Run the migration on a copy more than once, and have users check the results.
- Reconcile. Stock, open orders and balances in the new system should match the old at cut-over.
Cutting over without disruption
For a single plant, a weekend cut-over after rehearsals is often enough. For multiple plants, a phased approach — one plant or department at a time — reduces risk. A short period of running both systems can help, but it doubles the work for users, so keep it brief and well defined. Training should happen on the new system with the company's own data, ideally just before go-live.
A typical project, step by step
Every project is different, but a replacement for a multi-plant manufacturer usually follows a pattern like this:
- Discovery. Workshops with each department, walking through the old application, current reports and the workarounds that live in Excel. The output is a module list, business rules and a phased plan.
- Design. Screen designs for the desktop and web apps, roles and permissions, the dashboard, and data migration rules — reviewed with key users, especially the power users of the old system.
- Build in phases. Core masters and order flow first, then stores and materials, then production, testing and QA, then dispatch and reporting. Each phase is demonstrated with realistic data.
- Migration rehearsals. Data moved to a test copy, checked by users, corrected and moved again.
- Pilot. One plant or department goes live first, with close support.
- Rollout. Remaining plants follow, each with training and a short support period.
- Support and improvement. Once the system is stable, the improvements that were deferred during the rollout are added.
What management sees after go-live
For owners and directors, the most visible change is usually the dashboard. Instead of collecting figures from each plant by phone and email, they open one screen — on a laptop or a phone — and see open orders, work in progress, items awaiting testing, dispatches at risk and raw material shortages for every plant. Events such as a failed test, a work order on hold or an urgent dispatch appear as they happen. Questions that used to take a day of calls can be answered in a minute.
For staff, the change is quieter but just as important: fewer phone calls asking "where is this order?", fewer registers to maintain, and less re-typing of the same data into different files.
Security and backups
Old desktop systems often rely on a shared folder or a single server in the office, backed up — sometimes — to an external drive. A cloud system should come with a clear answer to where the data is hosted, how often it is backed up, how quickly it can be restored, who can access it, and how access is removed when someone leaves. Role-based permissions and an audit trail add protection from mistakes as well as misuse.
The cost of waiting
It is tempting to keep the old system running "until it breaks". The trouble is that when an old VB or FoxPro application breaks — a Windows update, a corrupt database, a failed server, the departure of the one person who understands it — it tends to break at the worst possible moment, with no time to plan a proper replacement. Meanwhile, every year of growth adds more workarounds and makes the eventual change bigger. Planning a replacement while the old system still works gives you time to do it properly, phase by phase, on your own schedule.
Common mistakes
- Copying the old system exactly. Keep what works; fix what doesn't.
- Ignoring the power users. The people who use the old system all day know its value best. Involve them early.
- Forcing everyone into a browser. For high-volume entry, a desktop app with shortcuts can be the difference between acceptance and rejection.
- Underestimating data cleaning. Plan time for it.
- No owner inside the company. Someone must make decisions about rules, priorities and cut-over.
Questions to ask a supplier
- How will you study our existing application and capture its business rules?
- Can you provide a desktop app with keyboard shortcuts as well as a web app?
- How will our data be migrated, cleaned and reconciled?
- How will multiple plants and roles be handled?
- How will the cut-over be planned so dispatch and production aren't disrupted?
- What does each phase include, how long will it take and what is the total cost?
- Who owns the code and the data?
Working with Corposol
Corposol is a Bengaluru-based software company that builds custom manufacturing software for Indian and international manufacturers. We have replaced legacy in-house systems with cloud software and desktop apps that keep familiar shortcut keys — read our use case for a Peenya hydraulic equipment manufacturer with 11 factories. All custom code is transferred to you on final payment.
Frequently asked questions
Why replace old VB6, Access or FoxPro software if it still works?
Because it usually works only on the local network, is hard to change, depends on one or two people who understand it, runs on old Windows versions, and can't give management a view across plants. The risk grows every year: when it finally breaks, there may be nobody left who can fix it.
Can we keep the old data?
In most cases, yes. Data in Access, FoxPro or SQL Server databases can usually be extracted, cleaned and moved into the new system. What is moved — all history or only open records and masters — is agreed during planning.
Our staff are very fast with the old system's shortcut keys. Will they slow down?
Not if the new system is designed for them. A desktop app connected to the cloud database can keep keyboard-driven screens and familiar shortcut keys, so experienced users keep their speed while everyone else uses the browser.
Do we have to switch every plant at once?
No. Plants or departments can move in stages, with a short period where both systems run. The cut-over plan is agreed with you to avoid disrupting production and dispatch.
Will the new system handle GST, e-way bills and e-invoicing?
It can be built to produce the data and documents your accountants and tax filings need, and to connect with accounting software or government-authorised service providers where required. Exact requirements depend on your business and should be confirmed with your tax advisers.
Who owns the new software?
You do. All custom code built for your project is transferred to you on final payment.
